@vhstape
@lemmy.sdf.orgThere are instances where the user is implied, but there is always a user. As far as Git goes, the user is almost always git
.
I can provide my two cents regarding Point One only. Throughout my day, I am likely to read news on multiple devices. I use FreshRSS to keep my subscriptions, read status, and favorites in sync; and I treat it like a backend. That is, I prefer native clients compatible with one of the supported APIs (FreshRSS supports several). On Apple devices, NetNewsWire. On Linux, NewsFlash.
LLMS are not (currently) involved. The article states that video content, trained to imitate the likeness of a celebrity, is generated to recite human-written information. Or so they say
Ollama provides a Python API which may be useful. You could have it generate the story in chunks, having it generate a list of key points which get passed to subsequent prompts. Maybe...
This is an interesting and well-written take. It might also be a bit of a stretch, but I still enjoyed reading.
I believe that RCS is a specification maintained by the GSM Association. That's not to say Google is not a member (they are) and has a strong influence, but Google doesn't own the standard either
I read a comment on Reddit a while back that pointed out how much of the open source community has no issue hosting projects on GitHub while also lampooning Snap for having a closed-source backend server. However, since Snap (and GitHub) are open source themselves, nothing is stopping curious and concerned users from auditing the codebase or hosting their own servers. I removed Snap from my Ubuntu installation and use Flatpak instead, but I do not hate Snap. And for what it's worth, I always go for the native DEB when possible...