IlliteratiDomine

Lemmy, itself, more or less has no rules, but individual instances do and links may violate some of them. More importantly though, publicly linking directories like that can be a good way for them to catch the attention of someone that would want to shut them down.

Edit: I accidentally a word

Little clusters of nucs has become a really common way to run small Kubernetes clusters at home. I recently rebuilt mine (still using a bulky, power hungry box like you're tossing) and have been very happy with it. Everything is really stable, containers that misbehave are automatically destroyed and replaced, and updates are breeze because everything lives in code/git.

Sure, but their algorithm in their app will be steering their users to content across the fediverse chosen specifically to ~~engage~~ enrage those users. Even if the broader fediverse isn't being fed directly by their algorithm, the worst of the Threads user base will be showing up in our communities and comment sections.

Ubuntu at work, Arch at home. Having a linux machine at work has been an incredible upgrade.

Speak for yourself. Seems like a high bar to me.

We’re not going to change it back, because this is a sexually explicit game, and also fuck them.

Now, this is a message I can get behind.

"Know your customer". Financial institutions, in the US at least, have to verify their customers' identities before providing services.

Technically, no, but you may want to. All of these services are federated and interact with one another. Mastodon users can interact with pixelfed posts and lemmy communities and anything else in the Fediverse. In reality, though, these services, and their clients, are built for specific types of content. If you're spending much time at all on those other Federated communities, the "round peg, square hole" nature of using a Reddit-like app to use a Twitter-like service (as an example) may start to chafe.

Nostr's "Zaps" concept really feels like the answer to me. A lot of the other aspects of Nostr are probably too "weird", at least right now, for mainstream adoption, but Zaps are simple enough to explain and enable direct monetization for creators.

Had me in the first... third.

Well, got it done. I was going to write something up about this process, but it ended up being really straightforward. I'm running it in k3s and the worst part was waiting for the initial sync.

Now, something about the SMTP traffic my router sends (trying to send notifications from a Mikrotik) makes the smtp implementation mad, but all my other clients were fine.

The KDE project has been focusing on sustainability, as a system efficiency metric, for some time now.

If you'd like to read more.