Thanks, I didn’t notice that before. Looking at the modlog, I’m guessing may have actually been for the use of a t*rd suffix … I think? The log doesn’t really get specific enough.

Yet, in the thread I presumed it was for, another user not only used a full-on r-word but also directed it at another user. They are still active and posting.

Hmm…

Where do you find this info?

Jesus christ. This is what’s wrong with internet discussions. There is no room for nuance and everyone just assumes the worst of everyone.

I wasn’t blaming anyone for anything. All I was saying is … murder is, y’know, bad and you should maybe try not murdering. I can’t believe this is controversial or ban-worthy.

Shadowbanned may have been the wrong term. I think it’s actually just an account lockout.

By all objective measures, so did the person replying to me. They’re still galavanting around lemmy advocating for murder.

Oh Bill…

Well, I’m here, aren’t I?

It should say “fuck reddit” where they join hands.

Forearms. It’s always forearms.

I mourn what it was, yes.

There was a recent comment I read about how it’s become this incredible resource for the most obscure tech issues and they were reluctant to delete their posts and accounts because they’d receive random messages of thanks years after a tech resource post was made.

And it’s true. Reddit has become an invaluable resource for these kinds of things. Not only that, but it’s one of the few places that exists on the web where cohesive and coherent discussions even exist. It was always the community and discussion that made reddit great and they want to turn it into yet another swipebait infested serotonin sponge. I sincerely hope lemmy can take its place, but there are going to be some major growing pains if we get big influx of “redfugees.”

It almost makes me think that when something becomes such an enormous and invaluable public resource, there should be a legal compulsion to archive it before doing anything that will compromise its accessibility.___

After hearing the call audio — and I am not defending spez here — I can actually understand how it might have been initially perceived as a “threat” given the context of the conversation. It was a mix of technical and financial negotiations (or really just spez saying “this is how it is, you can suck it”) and Christian was speaking metaphorically about Apollo’s API calls being “noisy” and (at least how I understood it) was suggesting perhaps “quiet” it down by optimizing the software.

I am not trying to victim blame here and it absolutely does not excuse spez turning around and publicly shit talking Christian, especially after spez immediately apologized on the call after admitting to misinterpreting what he heard … anyway, the point I’m trying to make is that it’s important to communicate clearly, directly, and unambiguously.

The headline is still that spez is a greedy sack of shit.

Particularly in the way that lemmy isn’t finance bro bullshit

Reddit following in their footsteps shortly after

Right, good point. Scroll down, it disappears. Scroll up, it reappears regardless of scroll position.

It’s a banana, Michael, what can it cost, $10?

It’ll be like a trainwreck in slow motion

I’m feeling rather smug and justified telling my clients to keep files on a local server that they control rather than “the cloud” someone else’s computer.

Good question. Not sure what the best procedure might be here. Could be as simple promoting them in order of initial mirror deployment dates and the others become mirrors for the newly activated instance.

Triggering the activation could be a part of an instance decommissioning procedure where the operator selects the mirror to become the successor. Maybe there could be some basic system specs and network performance reporting so they could choose the optimal instance. Users would receive a message that their account is being moved to another instance and domain.

In the event of an unexpected outage, there could be a deadman switch style timeout where the fastest mirror activates automatically after the original instance is out for long enough, but also a process for the operator of the downed instance to delay the takeover by signaling, “I’m working on it.” In the event of automatic takeover, since users wouldn’t be able to receive messages, there would have to be some sort of global lemmy notice system so users of the downed instance know where to go, like a sticky post on the front page or maybe just a separate “notices” page.

deleted by creator

That’s definitely my main concern I have with this federated infrastructure. It’s basically the same as IMAP email: if the server goes down, your account and everything it’s associated with goes down with it.

It’s a neat idea and has some benefits, but there really needs to be some sort of backup system in place. Maybe something like mirror instances, where anyone could spin up an instance with the sole purpose of mirroring another instance in case it goes down.