

I’m planning the same.
I’m planning the same.
Let’s not defederate from every corporate player. Some of them can probably respect reasonable rules of civility.
But fuck Meta. We already know how this plays out.
We know there’s a huge wave of hatred and misinformation incoming. We’ve seen it on their other platforms.
Yeah. I’ll switch to an instance that is defederated from Threads, if mine doesn’t.
I left Meta’s other properties to avoid state sponsored hate speech. I won’t use a platform that gives hate speech a platform.
I don’t need to wait to know if Meta will do that. I already know.
Awesome. Thanks!
It’s the year of the Linux desktop! /s
But seriously, I think I’m going to buy a SteamDeck.
Would it be enough to be able to run .deb packages on fedora?
Unpacking a .deb on Fedora, or unpacking an .rpm on Ubuntu isn’t a big deal. The files inside are often actually identical.
But would not be useful because the files inside usually rely on shared libraries, which may or may not already be installed. Those shared libraries are installed in different places on each Linux distro. Figuring out which ones to ask for (and making sure the program can find them) is the real work that the .Deb or .RPM installers do.
A fun way to try this out is with Portable Apps. Anything called a “portable app” either doesn’t use additional libraries, or carries the libraries it needs with it.
If you find a portable app for Ubunutu, there’s a good chance the Fedora version is an identical file, and works fine on Ubuntu. There’s lots of reasons it might not work, but it can be fun to try.
For the most part, the only reason any Linux program is unavailable on a different version of Linux is that no one has bothered to build the necessary installer for that combination of program and OS.
.RPM was supposed to solve this by being universal, since any other OS can implement it to match .Deb was supposed to solve this by being universal, since any other OS can implement it to match (about 60% actually do). I think Flatpacks and Snaps might solve this by being universal, at some point…
Source: I’ve built installer packages for various operating systems.
That’s the most evil thing I’ve heard in awhile, and I would absolutely make use of it anyway.
I’m confused. Google Services normally reach my news feed when they’re being abruptly discontinued. The headline doesn’t read like anything is being discontinued. I’m unsure what to make of this.
I guess I might check it out, if it’s still around in a few more years.
Edit: I wouldn’t be posting this cranky comment if I was still posting on Google Wave. Google Wave was pretty great.
I’m excited to give it a try.
I would just stop buying games. I’ll only play old games and open source games, if Steam gets enshitificaties.
Nice. Your excellent suggestion probably belongs in a meta-package somewhere so that users get it for free when appropriate.
You might find good resources at https://carpentries.org/community-lessons
I feel seen.
Markdown is gaining traction. There’s lots of tools that will edit and display Markdown consistently, and without a dedicated tool, it’s just a very readable text file.
And, most importantly for today, it’s easy to generate a PDF file from, haha.
The word cloud already honestly reflects the raw reviews pretty well.
That said, as badly as Amazon gets review spam bombed already, it’s hard to believe this isn’t going to be equally abused.
The compromise I’ve landed on is that I host my own DNS mx records, and point them to a paid enterprise mail provider.
This gets me the advantages of a paid provider while keeping my actual email address fully mine, to take wherever I want.
I did still have to learn a bunch of DNS rules in order to send all the correct “I’m not an evil spammer” headers and DNS records. But following a one page tutorial worked for me.
Edit: A disadvantage of my approach is that I’m still at the mercy of my email provider if I want to export my message history, and for the privacy of my message history.
I have had some pretty obnoxious recurring reboots on my Pi4 when I don’t add a heat sink and fan.
This is terrific. Thank you for starting this discussion.
I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.
I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.
But we know from XMPP that proprietary extensions are a huge problem.