Power management is going to be a huge emerging issue with the deployment of transformer model inference to the edge.

I foresee some backpedaling from this idea that “one model can do everything”. LLMs have their place, but sometimes a good old LSTM or CNN is a better choice.

Yeah, this is actually a pretty great application for AI. It’s local, privacy-preserving and genuinely useful for an underserved demographic.

One of the most wholesome and actually useful applications for LLMs/CLIP that I’ve seen.

Ideally you want something that gracefully degrades.

So, my media library is hosted by Plex/Jellyfin and a bunch of complex firewall and reverse proxy stuff… And it’s replicated using Syncthing. But at the end of the day it’s on an external HDD that they can plug into a regular old laptop and browse on pretty much any OS.

Same story for old family photos (Photoprism, indexing a directory tree on a Synology NAS) and regular files (mostly just direct SMB mounts on the same NAS).

Backups are a bit more complex, but I also have fairly detailed disaster recovery plans that explain how to decrypt/restore backups and access admin functions, if I’m not available (in the grim scenario, dead - but also maybe just overseas or otherwise indisposed) when something bad happens.

Aside from that, I always make sure that all of all the selfhosting stuff in my family home is entirely separate from the network infra. No DNS, DHCP or anything else ever runs on my hosting infra.

It would be better to have this as a FUSE filesystem though - you mount it on an empty directory, point the tool at your unorganised data and let it run its indexing and LLM categorisation/labelling, and your files are resurfaced under the mountpoint without any potentially damaging changes to the original data.

The other option would be just generating a bunch of symlinks, but I personally feel a FUSE implementation would be cleaner.

It’s pretty clear that actually renaming the original files based on the output of an LLM is a bad idea though.

(6.9-4.2)/(2024-2018) = 0.45 “version increments” per year.

4.2/(2018-1991) = 0.15 “version increments” per year.

So, the pace of version increases in the past 6 years has been around triple the average from the previous 27 years, since Linux’ first release.

I guess I can see why 6.9 would seem pretty dramatic for long-time Linux users.

I wonder whether development has actually accelerated, or if this is just a change in the approach to the release/versioning process.

The DJI Fly app is probably considerably worse for security/privacy than most Google apps. DJI has a storied history of sketchy practices in their apps: see here.

Google also won’t allow DJI to distribute their apps through the Play Store, because of DJI’s weird insistence on being able to push arbitrary binaries to customers’ phones entirely free of any third party vetting.

GrapheneOS’ sandbox hardening might help somewhat, but I’d recommend avoiding DJI products if you can. If you must use DJI Fly, prefer to use it in a different profile where it can’t touch any of your personal apps. Tough when they are singularly the best drone manufacturer for videography though.

OwnTracks is good for location sharing/logging and is open source. Ideally requires you to run your own MQTT server though.

If not using your own server, you can use payload encryption to protect your location data from being snooped by other users. (But ideally you should just run your own server, it’s pretty easy.)

If you include ChromeOS that’s very likely.

You can restrict what gets installed by running your own repos and locking the machines to only use those (either give employees accounts with no sudo access, or have monitoring that alerts when repo configs are changed).

So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.

For anti-malware, I don’t think there are very many agents available to the public that work well on Linux, but they do exist inside big companies that use Linux for their employee environments. For forensics and incident response there is GRR, which has Linux support.

Canonical may have some offering in this space, but I’m not familiar with their products.

At least in some circumstances, the risks of sharing your DNA include having children…

Tbf 500ms latency on - IIRC - a loopback network connection in a test environment is a lot. It’s not hugely surprising that a curious engineer dug into that.

I don’t think it’s necessarily a bad thing that an AI got it wrong.

I think the bigger issue is why the AI model got it wrong. It got the diagnosis wrong because it is a language model and is fundamentally not fit for use as a diagnostic tool. Not even a screening/aid tool for physicians.

There are AI tools designed for medical diagnoses, and those are indeed a major value-add for patients and physicians.

Precisely. Many of the narrowly scoped solutions work really well, too (for what they’re advertised for).

As of today though, they’re nowhere near reliable enough to replace doctors, and any breakthrough on that front is very unlikely to be a language model IMO.

Exactly. So the organisations creating and serving these models need to be clearer about the fact that they’re not general purpose intelligence, and are in fact contextual language generators.

I’ve seen demos of the models used as actual diagnostic aids, and they’re not LLMs (plus require a doctor to verify the result).

There are some very impressive AI/ML technologies that are already in use as part of existing medical software systems (think: a model that highlights suspicious areas on an MRI, or even suggests differential diagnoses). Further, other models have been built and demonstrated to perform extremely well on sample datasets.

Funnily enough, those systems aren’t using language models 🙄

(There is Google’s Med-PaLM, but I suspect it wasn’t very useful in practice, which is why we haven’t heard anything since the original announcement.)

It is quite terrifying that people think these unoriginal and inaccurate regurgitators of internet knowledge, with no concept of or heuristic for correctness… are somehow an authority on anything.

I know of at least one other case in my social network where GPT-4 identified a gas bubble in someone’s large bowel as “likely to be an aggressive malignancy.” Leading to said person fully expecting they’d be dead by July, when in fact they were perfectly healthy.

These things are not ready for primetime, and certainly not capable of doing the stuff that most people think they are.

The misinformation is causing real harm.

Ohh, my bad! I thought the person you were replying to was asking about Gitea. Yeah, Forgejo seems truly free and also looks like it has a strong governance structure that is likely to keep things that way.

This sadly isn’t true anymore - they now have Gitea Enterprise, which contains additional features not available in the open source version.

From here:

• SAML
• Branch protection for organizations
• Dependency scanning (yes, there are other tools for this, but it’s still a feature the open source version doesn’t get).
• Additional security controls for users (IP allowlisting, mandatory MFA)
• Audit logging