If they do that, nearly no one will find it, though. Are there larger non-federating servers?
Computers and the internet gave you freedom. Trusted Computing would take your freedom.
Learn why: https://vimeo.com/5168045
If they do that, nearly no one will find it, though. Are there larger non-federating servers?
I think the problem with this approach - read: the reason I don’t do this - is that you’re blocking communities from ever appearing again, and if your interests change, you still won’t see them. I think this is more likely to result in creating an echo chamber.
What I do is subscribe to communities that I found interesting, and then scroll all once in a while to see if there’s something else I like
I’m mostly reading my subscribed feed, and sometimes switch to all and if I find an interesting community, I subscribe to it too. The only communities I have blocked are either porn related or operating in a foreign language, which I see even though havening set my language preferences.
Afaik that’s docker’s fault. They always mark the latest uploaded image as latest. But also I thought it’s well known that :latest shouldn’t be used for any kind of software, unless you are a developer
I think provider might be a better world. It’s less of a technical term, and everyone knows what’s the difference between mobile service providers, internet/cable TV providers, and such.
I very rarely use reddit on PC, even though I use a PC for almost everything I can.
The reddit client that I was using kept track of which comments after new ones, but even that did not tell me that there are new comments there that I may want to read.
That’s right, but mostly it has been the same on Reddit for my while I was using that.
That’s not an excuse to keep it that way, of course, I would love it if we could subscribe to replies of a comment, either recursively or only to direct responses.
deleted by creator
It does with a plugin, but there are other tools that I think are not available for IntelliJ
code forges are great for management tasks. host an internal forgejo, and create repos for your servers and services. use issues for keeping track of initial setup, config changes and upgrades. have a longer term issue for whenyou just want to record a little change but too lazy to open a full issue for it. you can also store config in the git repo, and write docs as wiki pages for things that are more stable or important aspects of your systems