pleroma.debian.social

pleroma.debian.social

Jonathan Dowland | @jmtd@pleroma.debian.social

Principal Software Engineer on #OpenJDK #RedHat. #Debian developer (dormant). Computer Science PhD student. Amateur Computing historian (Computer Science and H/W, esp. Commodore Amiga). Guerilla archivist.

Just cut a new IkiWiki release. Hopefully I didn’t break anything. This is intended for Debian Trixie

@pndc it’s the bounce that concerns me. I could live with spooled retries. From the docs I think it might depend on the return code

@pndc i do! But as I understand it’s “pipe” command, I’m concerned about the behaviour if the command fails

@mcc I’m out of touch on current fashions, but my last project used stack and it solves a couple of the issues you’ve hit so far

@mcc @dysfun there’s quite a good chapter on parsec (megaparsec precursor) in “real world Haskell” (which is free online). I concur that a parsec variant is the best choice for this, even for micro-scale parsing . And I found that counter intuitive first time

@cstross mine’s always faintly lemon flavoured. I’m not sure I’d like mango more or less. I know I have to avoid lemon squash for months afterwards

@joostvb thanks! Out of curiosity, if you use “system some-command”, and some-command exits signalling failure, what does maildrop do?

@suihkulokki that’s the one I need to look at next. Thanks!

@noahm @suihkulokki I need to look at dovecot’s sieve in particular. I do want a pipe call-out (to a spam classifier) which exim’s sieve implementation doesn’t support (and exim’s own filter language has poor behaviour if the pipe fails: no handling in the filter script; generate a bounce to sender!). Thanks!

@mcc I *think* Char is actually (a) Unicode

Briefly looked at procmail (!) replacements today. Was disappointed.

Feeling old… I still routinely ^S/^Q to freeze terminals. I don’t really _need_ to anymore, and the bindings do occasionally cause me problems. So I should probably turn them off.

https://social.jvns.ca/@b0rk/114354742870242559

@evan citizen sleeper

Same for “atomic habits”

I keep wanting to refresh my memory of GTD and bouncing off its verbosity. I need my own cliff notes for it

Minilogue XD and Zoom R8 blinkenlights

@lightweight @pluralistic @dredmorbius WebKit itself was a fork of KHTML, in the dim and distant

Parallel ./configure (via @lwn@fedi.lwn.net, via pabs)

https://tavianator.com/2025/configure.html#parallel-configure

Proof-of-work challenges have become the current hotness for defeating AI scrapers. I think it’s great we have these and that they’re getting deployed to great effect. But I’ve also seen a lot of people claim the “AI scrapers” problem is now solved and I’m sorry to tell you this but no it’s not.

The reason it’s solved right now is because most of these scrapers don’t execute JavaScript. But with enough people deploying PoW proxies, the economics around that change enough to make it worthwhile for AI companies to do so. AI companies have more money than you. Yes it’ll cost them, but that cost is worth it to them because otherwise they don’t have a business.

(Also Anubis and other solutions default to only triggering if the User-Agent header contains Mozilla so guess what! It’ll soon need to be enabled regardless of the value of that header because it’s trivial to circumvent. Then the cost goes up for the operator too as more and more users get affected.)

The JS needed for the PoW stuff isn’t complicated. A small JS interpreter can handle that. What mostly remains is then the cost of the hash. Right now most things use SHA256, for which we have CPU extensions and AVX instructions to speed this up. Constantly increasing the PoW rounds doesn’t solve this. Eventually the experience degrades too much for real users, whereas servers literally don’t care. Nobody is sitting there waiting for the output to be rendered. All they want is to get the content to train on.

PoW proxies are a stopgap, and a very useful one. But a stopgap nonetheless. We’re buying ourselves time. But we’re going to need more than this. Including legislation that outlaws some of this shit entirely.

AI is a technology, but the root of the problem we’re facing is a societal and political one. We cannot ignore those aspects and exclude them from a solution.

»