CIRCLE WITH A DOT

@mcc Has Rust crossed the line yet? Rust has been such a valuable tool that I'm going to be really upset if we have to either give it up or fragment the community.

@marco @FreakyFwoof @pixelate Ah yeah, that does sound more likely.

@dalias To be clear, I'm not convinced by the proponents of LLM-based coding agents. I find the idea of having a statistical text generator pump out volumes of code from ambiguous natural language distasteful. And I sure wouldn't want that approach to be used for something like musl, where you clearly work on it deliberately, carefully, with no line of code wasted.

@dalias Doctorow seems to feel that this is what he would be doing; he finds the LLM useful. And some programmers I follow and respect feel that way about their LLM-based coding agents (using the big rented models, not a local one like Doctorow), that they'd be denying themselves something useful and putting themselves at a disadvantage for moral reasons.

@FreakyFwoof @pixelate Linux GUI accessibility, I think.

@FreakyFwoof @ToniBarth @TheQuinbox Now, maybe that points to the need for a better shared platform for devices like the Move, a platform that has the accessibility ecosystem already built in. Some of us wanted Android to become that. But that didn't really happen; Google only really cares about their own devices plus the emulator, so you end up with Android forks for other devices, and no official maintained port for the Pi as far as I know.

@FreakyFwoof @ToniBarth @TheQuinbox Good point about the advantages of externalizing the screen reader output, despite the obvious drawback for self-contained portability. It would have been beyond Ableton to reproduce the breadth of TTS and Braille options on Windows, iOS, or Android, let alone the choice of all three. They presumably realized that and decided to punt on that. Competing priorities, limited resources, tradeoffs everywhere.

This came across my timeline today: "How to Scale a System from 0 to 10 million+ Users" https://blog.algomaster.io/p/scaling-a-system-from-0-to-10-million-users

Aside from the question of whether any one service *should* be scaled all the way to 10 million+ users, I wonder what people think of the specific stages and especially the estimated number of users for each stage. My feeling is that the author way underestimates the number of users that a single machine, even a cheap VM, can and should serve.

@fastfinge You can set up SRV records for your XMPP server, like this (in BIND format):

_jabber._tcp 300 IN SRV 0 0 5269 im.interfree.ca.
_xmpp-client._tcp 300 IN SRV 0 0 5222 im.interfree.ca.
_xmpp-server._tcp 300 IN SRV 0 0 5269 im.interfree.ca.

You'll probably also need to configure your XMPP server to handle the base domain.