Sven Slootweg @joepie91@pixie.town

A voluntary peer review system, but for pull requests. Instead of throwing money around, having meta discussions on how to run FOSS better, keep it simple. A group of people, including some real experts for the truly weird cases. Let’s call it the s-express (security express, and yes, when you remember the song, all the better). When you as maintainer receive a pull request that looks dodgy, you can forward it to s-express, who will take a look and report back with a first assessment in 24 hours

Proposal:
- Legally require all consumer products to specify an expected lifespan in all their marketing materials.
- Extend the "legal guarantee" in EU to cover whatever the claimed expected lifespan is, under the same terms as are used now (but no shorter than the existing minimums).

I bet that this would cause a significant industry shift towards durability. Because making something much more durable is often only slightly more expensive, but unless corner-cutting manufacturers are required to be transparent about their corner-cutting, price is often the only thing that products are judged by.

I wish more people who are worried about FOSS supply side attacks would realize that universal basic income and free healthcare would result in an almost infinite stream of excellent software from people who care more about quality than profit.

Firefighters value property when lives are in danger about as highly as cops value lives when property is in danger.

"If you make your own engine you'll never ship a game"

I'm here to tell you this is BS. Kitsune Tails uses a custom engine built on a custom framework all made from the ground up by yours truly. Neither of these were even remotely the bottleneck for development duration. Turns out that the thing that takes the most time when you're developing a game is all the stuff that is hyper specific to that game and can't be generalized anyway

Not to mention all the, you know, actual content that sits on top of the engine. I can write a json parser and serializer from the ground up in a day or two, but all the cutscenes I had to script for KT took many weeks

Then there's the fact that if I'd used an out of the box physics solution for Kitsune Tails I'm fairly certain I'd never have been able to nail the game feel it has, which is the most core thing to the whole experience

You don't *have* to make an engine but quit pretending doing it is the hard part of making a game. It fucking ain't

Six-year-old Ami's idea of putting numbers in #order was unusual. She wrote
0 6 9 3 8 2 5 4 7 1.
and explained it like this:
"It's an order from soft & curved to sharp and straight. Zero is a whole soft oval. 6 & 9 try to make curls, & 3 makes double curls. 8 connects the doubles! Then 2 starts to uncurl & makes a sharp point. 5 has that, plus more straight parts. With 4, the curve is gone, & then it gets simpler for 7 & then down to just 1." #wss366 #microfiction #numbers

She's not daft, my mate. UI designers just behave as though they live in a vacuum. They think that when someone looks at their menu, it's the first menu that user has ever seen, and they haven't seen a hundred menus a day with a massive button saying "Yeah make everything worse lol" and a tiny text link that says "Just let me get on with it for a minute."

This is the new normal, UI designers. Your users expect hot garbage, and they expect it so hard that they'll treat your Very Important Question the same way they'd treat any other spyware cookie crap that every website insists is a Very Important Question, and they'll just give whatever answer will let them continue while being mildly annoyed.

Helping out a mate set up her #gameDad recently. She got to a page asking a question and prodded the buttons without reading. I went "Wait hang on what did that say," we never found out but it was Probably something about updating a list of ports? Who knows! Anyway it started up fine, but... like, twenty years ago I would've gone, like, "Mate what are you doing," but these days...

When every website you visit thrusts a thing in your face as you're scrolling and you know it's spam so you just hit the heck-off button without looking, never mind reading

When every game you play starts with a bunch of logo videos that you have to mash buttons to skip

When a new game throws some bollocks up about an EULA that nobody expects anyone to ever read

When every three days your computer goes "Hey can I just -" and you read it once and understand that it's asking you to install spyware and then every other time you hit the Remind Me In 3 Days button without thinking or even pausing

When every day you get an email that says "Important information about your account" and it's never important information

When 80% of your physical mail goes straight into the recycling bin without even being opened because, well, it's just recycling

...yeah. It's absolutely no surprise that our default first interaction with a machine is to mash buttons randomly until it stops banging on about whatever and gets on with doing what we bought it to do.

Back in 1999 when you'd go to join a new forum there'd be a rules page, and at the bottom would be a big bright eye-catching "AGREE AND CONTINUE" button, and a little way above it, in the rules themselves, would be something like "To prove that you've read the rules, click on the period at the end of this sentence."

Clicking on "AGREE AND CONTINUE" would issue a two hour IP ban so you could Actually Read The Rules, and also think about what you'd done.

1999 was a hell of a year