Much better to add features to your software that make it unusable in totalitarian situations.

For example

• if you’re building a reddit clone, make each subreddit elect their moderators every few months.
• Maybe ask How fat is Kim Jon Un during installation.
• Display the text “Taiwan is not a part of China” in the status bar, randomly

…and so on. The possibilities are endless.

If you don’t want to see it, you’re not going to.

See this https://piefed.social/search?q=censorship+musk

This won’t fool the insurance companies. They’re the ones on the hook for this.

“a documented history of migrant abuse” is such a nice way to put it.

A quick search for “libya migrant mass graves” brings up this - https://news.un.org/en/story/2025/02/1159951

That’s not ‘migrant abuse’. That’s somewhere on the spectrum between genocide and mass murder.

I remember when MS made the perfect control panel in Win 2k and XP then spent the next 20 years making it worse and worse just because.

And here we are.

Yep, I’ll document it in some way. A FEP seems overkill as it’s really just adding a bit more data onto Actors and Activities, not a big deal.

You say that like it’s a bad thing.

Lemmy users missing out is THE reason they’ll become PieFed users.

I did the DB structure changes at the same time as the ones needed for community flair as they’re quite similar. Might be able to do the rest tomorrow.

Tags, aka hashtags, are instance-wide (not just in a community) and interoperate with Mastodon, Pixelfed, Mbin. Anyone can make a new hashtag and they are completely unmoderated.

Flairs are a limited list determined by each community’s mods and are only used in that community. They will federate with other PieFed instances and with Lemmy (when they finish coding what they’re calling “tags”, a really unfortunate choice of name).

Watch this space.

Lol, rip

Title updated.

I think this is a case where changing it to “lies” won’t violate the community rule “Title must fairly describe link contents. If your title differs from the site’s, it should only be to add context or be more descriptive”…

I’m conflicted.

Making those poor bastards work 12 hour days, 6 days per week for small money is pretty fucked.

Sending them to somewhere that may be a death camp is worse tho.

Feels like the article set up a false dichotomy.

You’re going to have to prioritise.

Find changes that:

Save a decent amount of money Are low risk Don’t take too long to do Can be easily backed-out of

Also, turn off chat heads. Such obvious engagement bait.

There are probably a variety of mindsets that will do it.

For me, I think it was just really wanting to get away from being under the boot. Get away from the walled gardens. Like that feeling after using LinkedIn, except for the OS. Hearing the call of freedom, authenticity and humanity.

Increasing amounts of code running on my computer and in the online services I use will be written by generative AI.

Emphasis added by me.

Thing is, it’s not black and white most of the time - usually a developer is using Gen AI as an assistant in some capacity. There are a wide range of ways to do that with really big differences in how firmly their hand remains on the wheel of where things are going. Only in the most extreme “vibe coding” scenario would it be fair to characterize the code as “written by AI”.

There reaches a point somewhere on the spectrum of dependency on AI where quality would suffer and developer capacity-building would be stunted. Where that point is, is a more productive question than a binary Yes or No to all AI.

“Do you regularly watch videos by Jordan Peterson?” kinda needs to become one of those before-first-date screening questions.

Imagine you want to write a competitor to PostgreSQL and you start out by importing SQLite into your project and building on top of that. To you it seems like a good idea because you’ve never written a DB app before and the only DB you’ve ever seen before is SQLite. You’ll get a prototype real fast but you’ll never build a PostgreSQL equivalent because you never learned the foundational knowledge of how a DB works and because SQLite forecloses all the pathways you need to get there.

Same thing.