dnzm

…I have no words.

From boiling water into water that happens to be in a switched-on kettle. Huge improvement.

When the enshittification comes (when, not if, they’ll have to drag their feet to move somewhere else again. All their followers will have to follow them again. Had they moved to a proper open solution, they could’ve stayed there indefinitely.

It’s not just about Bluesky" not being the proper and pure solution", it’s about this being a temporary measure at best, and people don’t seem to realize that.

Simple, the position doesn’t require technical insight. At all. It should, but it doesn’t.

If I understand this document correctly, it would mean that the entire connection somehow gets routed through Meta’s servers. I can fully understand the reluctance of other parties, including Signal, to do that, and I wonder how this is actually compliant with the DMA.

So they either keep Signal around and be able to talk to you, or they don’t. They don’t need to stop using WA to use Signal.

If they don’t want to do that, it’d mean that you would have to keep WA around for the one or two contacts you have there (and only there), which is somewhat comparable, actually, if you disregard the “but meta is short for metastasis, actually” bit.

Which one of the two it ends up being is between you and your contacts.

AKA Betteridge’s law of headlines.

Ehh, I’m fairly sure it’s not. It certainly wasn’t in the past. When do you believe that changed?

Never mind, you were talking about OO, not LO, my bad.

If you mean a (read-only) web interface, there’s also cgit and gitweb.

I mean, it’s your party and if Gitea works for you, that’s great. It still is a bigger piece of software than what you need (or at least what you’ve told so far), it’s up to you to determine if you’re fine with that.

i don’t want wordpress.

Me neither, but a lot of folks do (or at least think they do), and if this makes it an approachable gateway into the larger fediverse for them, I’m all for it.

They can always switch to something better, later.

It works for me in .nl, so that’s probably not it.

That’s an interesting approach, this might just make a better fit than what I’ve been doing so far!

Fellow Microserver haver, here! Mine did get a Xeon and RAM boost and has been my everything server for years now.

They don’t, officially, as far as I know it’s always been an “at your own risk, might get your account banned” endeavor.

No, problem not solved, problem half-heartedly worked around. People dislike Discord for several reasons, bridging it to whatever different platform will at best be a bandaid.

It absolutely is. Yet, as Sean said, it’s also yet another bit of software to run and maintain, and ES is known to be a bit of an effort to keep going well.

Admins having only finite amounts of time and/or resources, might make the very understandable decision to leave it out.

You gotta love the copy on the Warp site. As for why they’re now launching it on Linux:

Despite this, Linux has relatively few terminal options compared to Mac and Windows

…relatively few? Really?

This sounds like it’d be exactly how I currently use Tumbleweed on my workstations: I don’t update daily, but rather every once in a while. I appreciate the new versions of things, but being on the daily bleeding edge is more work than I care to put in.

I can also see this working quite nicely for those with nvidia hardware, where with TW you’d sometimes end up with a kernel too new for the drivers to get shoehorned in. A slightly easier-going pace would help there.

It also reminds me of Android, where you have roughly monthly updates (theoretically) and every now and then a bigger one.

Installing a software package through a distro’s package manager sounds like a perfectly fine “Linux way” to me.

Of course, that filesystem exists today as btrfs.

Which, to be fair, isn’t exactly the fasted FS around. I love me some btrfs, but not for the benchmarks.