Arch is wisdom. Every LTS-type distro is bound to catch issues due to lags and discordance in release cadence and worse of all, distro-specific patches that complicate things and by themselves have the potential to introduce unique CVE's like one I was reading recently about Ubuntu involving OverlayFS.
Necessary for me to fix the "bugs" present in Android (Safetynet fix, F-droid & Aurora auto updates etc.) and some from the OEM (flawed camera libs from Xiaomi that unintentionally hamper the use of Gcam).
As it you can block an entire community from your feed. I don't trust the instance to do any of this on my behalf. This is where things get slippery and instead of just banning hate groups, they'll eventually start banning political communities.
If you really take a look at this. Something like Twitter has done a great job of this such as mass filtering out undesired content by muting keywords.
I really think this is the way to go instead of allowing unappointed admins who are only answerable to themselves to be the judge of what is "good" speech.
Maybe I will end up giving up on lemmy.world and eventually self-hosting my own instance.
Depends on the exceptions but that's anti speech anyway, so not a fan at all unless has to be done.
Am for people individually blocking out content that doesn't align with their values. Personal curation as opposed to mass censorship. Mass censorship opens up a whole can of worms that I personally find too distasteful for my liking. I don't agree with the idea of a walled garden social media.
All of them. Am pro free speech and strongly against censorship.
No. Federated tools suck and lemmy.world is kind of the last attempt am giving. If it doesn't work, I can just go back to pleb sites.
Have accounts on other lemmies that I don't use but I want to use lemmy.world the way I would use reddit. One account that takes care of my identity.
I'm not creating 20 different accounts on 20 different instances.
It's a stupid point from my perspective. Can't just jump from every Lemmy instance whenever they do stupid shit.
Besides federated tools are already hard to use as they are. Might not be worth the trouble in the long run if censorship is rampant on every big instance.
Everywhere. HN, Twitter, Reddit, Element. If lemmy.world mods make another justification post for de-federating a community they disagree with, it's bye bye Lemmy.
Who gets to decide what is permissible content? That's my issue. Not some faceless unaccountable to anyone mods.
Is lemmy.world a place for anyone who wants to have a conversation (within legal/social limits) or not? is the real question here.
BS. I see stuff I don't disagree with all the time on the net. I don't go calling for admins to take them down or refer to the posters as ticks. If you have to grandstand about morals, be real and about something.
Nah. It's a (biased) personal interpretation of what "good" "safe" "family-friendly" content means for lemmy users. Idk much about Hexbear's content but isn't it possible to label their posts as NSFW incase of visibly violent content or something similar.
The users who disagree with Hexbear's overall comments know where the block button is. It's not that complicated a solution. People should use more of it instead of looking for reasons to get mad.
Oracle responds to Red Hat
Basically have watchtower monitor and update containers whenever new images are released. I've recently noticed that with searxng (using redis as db), hosted through nginx proxy manager, will have a steady downtime of about 15mins post update then come back online.
This is extremely frequent for searxng's case as I have watchtower run every day and my preferred way of running most of my containers is with the latest tag. The way out of this downtime in my experience is a restart of NPM which brings back the searxng service.
I'm looking for a way to automate a restart of the NPM container after a successful update of searxng's container.
I have checked the docs for watchtower, and the lifecycle hooks (a way to run sh scripts pre/post update) are able to run only from the applied container and not from the host system.