Show newer

Het besef van Ilja Leonard Pfeijffer, tot zijn schrik, hoe eenvoudig het was in de jaren 30 en nu dus nog steeds is om in slaap te worden gesust door de traagheid aller dingen en naar een #dictatuur te worden geleid. Hoe gemakkelijk het is om je schouders op te halen bij kleine veranderingen die je niet persoonlijk raken, totdat het moment komt wanneer ze je wel raken en wanneer het te laat is om je er nog zorgen over te maken. #NeoFascisme

demorgen.be/meningen/ik-woon-n

archive.ph/jiXic

Hi fedi! @darius and I are digging into our governance research, and we have a great starter list of server admins to potentially talk to about governance and administration models and challenges, but *very unofficially*, I’d love to hear suggestions, too.

We’re looking at active servers ranging from ~100-2,500 users with some flex on either end of the range, and we’re building our list with an eye on structural, geographic, demographic (along multiple axes), and linguistic diversity.

Please stop making software that’s vulnerable to SQL injection attacks. It’s 2024. Learn about parameterized queries. Please.

Please.

At Torment Nexus, instead of "setting the employee on fire", we prefer to think of it of it as "facilitating the next step of someone's combustion journey"

Ugh, someone set this TfL bus information display to German — clearly it should say “502 to Gateway Spa”

Hydration checkpoint!! When's the last time you had a sip of water?

re: constructive sabotage idea for anti-capitalists 

@pinoaffe (Note that they usually won't *tell* you that someone else told them to; they will just insist that they need the feature and be incredibly vague as to why, or come up with an explanation/usecase that doesn't make sense)

re: constructive sabotage idea for anti-capitalists 

@pinoaffe Ah, right - that's going to be dependent on the type of software, usually, but a good first pass is "hyperoptimize it for non-commercial use where no money changes hands"; like, deliberately build things without room for a billing mechanism or customer management, for example (eg. no ability to suspend an account for non-payment).

Another good one (though it requires more care to not introduce eg. unintended accessibility issues) is to design around a rigid way of using the system, especially around reporting.

Corporate users often need the software to work in very specific ways because "the manager said they want a report in such-and-such format" regardless of whether that actually makes sense, and every such reported issue that you can answer with "we have no intention of supporting this, _____ should be good enough" is a win.

It does take some experience, but after a while you'll learn to spot the complaints and feature requests that are obviously for corporate use, vs. those of individuals or collectives. "Needs a feature or change because someone else told them to, rather than because it solves a clear problem" is the major red flag.

re: constructive sabotage idea for anti-capitalists 

@pinoaffe That's the process of gradually making it shittier (for corporate use) but never to such a degree that it's bad enough for them to jump ship

re: constructive sabotage idea for anti-capitalists 

(Note that for this to be a net positive to an anti-capitalist cause, the 'clearly better' needs to be on an axis *other than* business efficiency)

Show thread

constructive sabotage idea for anti-capitalists 

Build FOSS software that's clearly better than the alternatives, but make it *exactly* the right amount of hostile-to-corporations; so that it is frustrating to use and slows down business processes, but isn't *so* bad that it justifies buying or developing an alternative

Take advantage of corporations' inability to see the long-term costs resulting from short-term savings. If they can enshittify our software, we can enshittify theirs

Also works with existing projects that are already widely adopted by corporations

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.