He will say what he thinks needs to be said, and the forced-birthers understand this. They haven’t defeated abortion yet and aren’t going to split their efforts, but they will continue to put pressure on ivf in the meantime. Remember, they weren’t always anti-abortion, and didn’t switch to it overnight! Their current position that life begins at conception necessarily conflicts with current ivf practises, and they’ll say they don’t disapprove of ivf in principle, and they might even have a friend who’s getting ivf, but talk is cheap and they’ll absolutely oppose any legislation that tries to guarantee access to it. Which is precisely what is happening.

Today's entry in the wordpress saga: seizing plugins from devs. The author of this one appears to be affiliated with wpengine, which possibly signals more events like this in the future.

We have been made aware that the Advanced Custom Fields plugin on the WordPress directory has been taken over by WordPress dot org.

A plugin under active development has never been unilaterally and forcibly taken away from its creator without consent in the 21 year history of WordPress.

More details here: https://furry.engineer/@cendyne/113296240801713427

It’s shit like this that discourages from ever running any sort of service that interacts with the general public. I’m already exhausted by the sheer grinding tedium of the amount of visible tone policing on the internet, and it somehow never occurred to me that it was just the tip of some vast beige fatberg clogging up all the pipes.

Anyway, thank you for hiding the awful realities from the rest of us o7

You should try what these folk are selling.

https://h2o4u.ca/

I have faith in the ability of the UK public sector (or rather, the relentlessly incompetent outsources they hire) to catastrophically fuck up delivery of any software project.

For example, capita has already lined up at the trough: https://www.capita.co.uk/news/capita-advances-approach-next-generation-ai-microsoft

If you’re unfamiliar with capita, that’s probably a good thing. I’m not aware that they’ve ever been successful in anything, other than their continued ability to fleece the government. They’re basically too big to fail in the uk, because HMG’s procurement processes mean that they basically can’t stop giving them money.

The notion of “professional moderator” should perhaps ring some alarm bells. Sure, some people will be good at that sort of things, but:

• being a moderator can be stressful or even traumatic, depending on the sorts of stuff your site is subjected to. Mods must take breaks from time to time, and modding several sites at once to pay rent seems like a route to a mental health disaster.
• mods opinions should broadly reflect the ethos of the site and at least some portion of its user base. Selecting mods from that user base is one way to do this… finding non-users who don’t need time to get up to speed with the local situation seems challenging, unless you’re running a very generic bland corporate platform.
• ACAB. People who seek out mod powers should be given a good deal of side eye. Assholes lurrrve positions of power and authority, asshole mods wreck communities, and finding non-assholes in good mental health who have the time and are prepared do the often unpleasant task of moderating your community seems challenging.

treehouse.systems had a nice thread recently about their modding arrangement, but I can’t find a handy link to it right now.

I like the idea of small communities, but a major issue (possibly the biggest issue) as demonstrated by many mastodon servers over the years is longevity. What happens when your admin gets bored/burns out/dies/goes fash/is replaced with an asshole/is unable or unwilling to moderate effectively?

I don’t particularly like the big mastodon hosts (eg. mastodon.social) but they’re probably still going to be here tomorrow, unlike eg. octodon.social who are winding down because adminning was too much (after 8 years, which was a pretty good run!) and they didn’t have any plans or processes in place to handle this eventuality.

Between that sort of thing and stuff like matrix cryptography being full of holes and large matrix room management being a nightmare and email really being gmail, I’m slowly coming round to the idea that federation is too hard to do well and that if we could just manage a decentralised identity service and decent client software then it wouldn’t matter if servers didn’t talk to each other because we’d still have 90% of what people wanted from federation in the first place. Just a simple matter of engineering, I’m sure.

You realise that all electronic currencies will necessarily involve transaction logs stored in someone else’s computer? Even Zcash and monero, which have clever anonymous transactions, allow selective disclosure of the details of those transactions if you ever find yourself at the wrong end of a criminal investigation or tax audit. Moreover, their anonymity guarantees are not perfect (the IRS has certainly paid big bucks to chainalysis for de-anonymisation, for what that’s worth).

Unless someone magically invents a software artefact that can’t be duplicated (don’t hold your breath, I’m serious about the magic) there’s no escape from this fundamental requirement.

Ploopy kinda fills that niche, as the bits are replaceable and the non-generic parts don’t require stuff like your own injection moulding equipment. Not quite there yet, nor do they have a the full range of stuff you might want (and what they do have isn’t cheap), but it’s a nice start.

What do you mean RAG is basically LLM flavored elasticsearch

I always saw it more as LMGTFYaaS.

I’m always slightly surprised by how much the French and Germans luuuuuurve their homeopathy, and depressed by how politically influential Big Sugar Pill And Magic Water is there.

I spend an inordinate amount of time at my C# day job adding documentation comments about exclusive access and lifetimes and ownership… things which are clearly important but which dotnet provides little or no useful support for, even though it has a perfectly good garbage collector. The dotnet devs were well aware that garbage collection has its limits, especially when interacting with resources managed outside of the runtime, and so they added language features like IDisposable and finalisers and GCHandle and SafeHandle and so on to fix some of the things GC won’t be doing for you.

I’d happily use a garbage collected language with borrow checking.