I am groot err… root.
Tech enthusiast and a seasoned Cloud Infrastructure Expert with extensive experience in Linux and containers. With a deep passion for cutting-edge technologies and a drive to optimize digital ecosystems.
Yea, I have submitted multiple abuse emails with details to domain registrars for scamming and phishing.
Didn’t receive any update from them on any action taken yet.
For SysAdmin you can use !Sysadmin@lemmy.ml.
For LinuxAdmin you can use !linuxadmin@lemmy.run.
I haven’t found one for IT and Helpdesk yet, but I am pretty sure they are out there.
Hmm I didn’t know about ParaFly, so something I learned today as well 😀 .
Haha, that is why I am glad I replaced all my contents with garbage before removing and waited for couple of days before removing them.
Seems like another good company is being sacrificed to corporate greed.
I nuked all my posts and comments.
Glad that I left the place, it can burn and go to hell for all I care.
On the other hand there’s enough constructive engagement happening here to fulfil my needs.
I did not.
Thank you for sharing it. Something you learn everyday, eh 😀.
Sure, will try to include output in future. Appreciate the feedback.
Yeap, but most of the time you end up trying to figure out issue on remote system, where you don’t have ripgrep always installed, but if you have that available on the system you are working on. ripgrep is always a better alternative.
Hmm, OpenBSD commands sometime have different behavior than Linux.
I know as I had run into issues with rsync earlier where some options I used on Linux didn’t work as same on FreeBSD/OpenBSD.
Seems like you are trying to build the docker image locally for your service. And you missed the dockerfile which contains all the information about building the container.
AFAIK, there is no centralize community for that.
This seems like a bug.
Also it could be that lemmy.world is overloaded and is stuck at processing to clear this.
Keep it documented and submit a bug report so that devs can look at it when they can.
Yeap, this is definitely weird.
How about you try to login in private/incognito?
Do you still see it?
If it is, I would advise you to submit a bug report to lemmy devs here.
Hmm, in that case, try to clean your browser cache.
You can go to the notifications and mark it as read by clicking the checkmark. It should disappear after that.
Nice initiative.