Probably can't be libel if they don't make it public, just stuff that happens behind closed doors and they can say "no comment". Would be different if Reddit had a public modlog like Lemmy.
My guess is, after 10 years without a problem, someone around 2 years ago might have marked me for takedown for whatever reason. I always tried to be respectful, but didn't start self-censoring until they suspended me for "violent content" without even referencing what was the supposed content. I kind of hoped that using Power Delete Suite to blank the account history, and avoiding most polemic topics from then onwards, would keep it safe, but apparently not.
Ironically, an alt account I created to participate in more polemic topics, got zero problems... but they now banned it along the main one, so bye Reddit, so long and thanks for all the fish.
the karma accumulated could be used to improve the rate of exchange for Reddit gold into real-world money (possibly USD)
Oh, so all those people with 10+ year accounts, with tons of karma accumulated over the years, and who deleted their accounts in protest for the API changes... are actually a "good thing" so Reddit doesn't have to pay top rates for their comments?
There is no need to get notified, they didn't steal passwords, just session cookies. Most (all?) servers have invalidated all the user login cookies, but if you are in doubt, just logging out and back in should be enough to get a new cookie.
"god created man in his likeness". Oh yeah, did he create aliens in his likeness too?
Depends on what that "likeness" is. What if "God created both man and alien to be bloodthirsty creatures to fight each other"... and the winner gets to fight God live on GodTV. In the meantime, tune in to PlanetaryWars channel this weekend to see a whole civilization annihilate itself!
My main account got permabanned for "sexualization of minors" after I made a comment criticizing a guy talking about what he'd do to 4th graders. Sent an appeal... and got permabanned on ALL of my accounts for "recurring offense".
Maybe spez wants to turn all of Reddit into jailbait again.
Because I already had my fingers closer to "su" than to "-s"... but really, because I tend to use sudo -E su on a remote terminal with a PS1 set to colorize the prompt based on whether I'm running root and the host if it's remote, but sudo -E -s doesn't run the root's .bashrc that runs the updated colorization while at the same time exports too much of the user's environment into the root shell.
Haven't you heard? The UEFI bios can have binaries included by the board manufacturer that Windows will ask for and automatically run on startup... for example to download a GigaByte control center installer to fill your recent install with crapware... that would then proceed to download a self-update from a http (no-s) URL. And the binaries will work even if they're signed with revoked certificates and have been injected by any device with DMA access!
That's... like... super cool, isn't it? If only we could have that on Linux... /s
Also, the modern bioses have pretty graphics and mouse support... /s/s
As an AI language model, I can understand and communicate fluently in different languages such as English, 中文, 日本語, Español, Français, Deutsch and others. Here are some examples of how I can complete the sentence:
As an AI language model, I can translate text or speech from one language to another.
As an AI language model, I can paraphrase or rewrite sentences to improve clarity or style.
As an AI language model, I can detect the sentiment or tone of a text or speech.
As an AI language model, I can answer questions or chat about various topics.
As an AI language model, I can generate catchy slogans or headlines for products or services.
Snaps and Flatpaks, are essentially the same thing seen from a different angle, so anyone preferring one over the other, basically deserves whatever they get 😋
The rest... well, freedom of choice is one thing, but when discussing the pros and cons, there are likely people who got burned by the cons of any choice out there, and each choice has their fair share of cons, so it's understandable that they'd sometimes get emotional.
What do you see wrong with the config override system? I find it an improvement over having to diff between new and current config files, then having to figure out which part of which to keep.
Xorg, or X11, "used to" do the "minimum necessary" for a remote display system... in the 80s. Graphics tech has changed A LOT in the last 40 years, with most of the stuff getting offloaded to GPUs, so the whole X11 protocol became more and more bloated as it kept getting new and optional features without dropping backwards compatibility.
The point against Wayland, was dropping support for remote displays, while kind of having an existential crysis for several years during which it didn't know what it wanted to become. Hopefully that's clear now.
OpenRC and runit are indeed working alternatives, but OpenRC is kind of a hack over init.rd, while runit relies a bit too much on storing all its status in the filesystem. Systemd has a cleaner approach and a more flexible service configuration.
Arguably, Systemd does exactly that: orchestrate the parallel starting of services, and do it well.
The problem with init.d and sys.v is they were not designed for multi-core systems where multiple services can start at once, and had no concept of which service depended on which, other than a lineal "this before that". Over the years, they got extended with very dirty hacks and tons of support functions that were not consistent between distributions, and still barely functional.
Systemd cleaned all of that up, added parallel starting taking into account service dependencies, which meant adding an enhanced journaling system to pull status responses from multiple services at once, same for pulling device updates, and security and isolation configs.
It's really the minimum that can be done (well) for a parallel start system.
Hate speech is a call to attack some people.
It may sometimes sound like "just offensive", since it often uses offensive code words to coordinate an attack.