I know some European "automatic scribe" projects of the government sector. Their IT buys a physical GPU server hosted locally. Pretty sure it wouldn't be accepted otherwise (or maybe I'm just naive, but it sure is a topic they care about). The software stack is mostly open source, I think. It sure as hell doesn't talk to a big American cloud provider. (Well, the transcription service doesn't. Who knows what they do with the automated transcript. Probably the same thing they did with the manual transcript.)
Well said. There is a social context, there is a process and a struggle that can be more important than the result. It is sad to reduce art to the final product, or to approach it with an industrial mindset: maximizing commercial value while minimizing effort.
My doctor probably thinks we software developers do a very narrow job. And she is kind of right, we always turn up with those back problems from sitting too much, or RSI or whatever. While doctors have all those medical specializations and different roles and employers.
If it can go online, I'd prefer to use an android work (or user) profile with only auth apps in it, and nothing else.
As a separate device, it should be offline always IMO, and perhaps the size of a passkey. Or one of those banking devices with a display that show an authenticated text saying what you are confirming.
Say you have an ad-blocker and you don't allow it to touch your forms. Five years later, the ads have moved all into form fields.
Never mind the technical challenge to allow doing anything with the DOM but disallow reading the forms. Like, prevent the forms leaking its text when you do funny things like testing character width via line breaking or font changes.
Disagree, Linux is too big to fail. Too many people depend on it. It may get chaotic, but worst-case distributions will start collecting patches, as they already do for many unmaintained projects. Eventually one or two of them will emerge as the new upstream.
reply