Are you talking about search engines or browser rendering engines? For search, searxng already exists. A decentralized browser rendering engine doesn’t really make sense, since it’s just software that runs locally.
Are you talking about search engines or browser rendering engines? For search, searxng already exists. A decentralized browser rendering engine doesn’t really make sense, since it’s just software that runs locally.
Automatic updates.
Yes, all of DivestOS development has stopped due to lack of a maintainer.
Nice! It would he even better if they weren’t built with slave labor.
Put them up on archive.org too if you haven’t already
You are literally describing an operating system environment
Great, but that has nothing to do with software architecture. Rolling everything into one app instead of using the OS platform is not good software architecture.
the new DeepSeek model comes with a catch if run in the cloud-hosted version—being Chinese in origin, R1 will not generate responses about certain topics like Tiananmen Square or Taiwan’s autonomy
Android provides an API to present your app in the system and launcher, and UI toolkits to present a consistent UI and UX. Apple does too, more forcefully. A “super app” is just inserting another layer.
I think that’s called an operating system
It’s gonna take many, many layers of paint in order for it to not bleed through. You’re better off stripping the existing paint and removing the soot-stained parts entirely.
Edit: after seeing the pictures maybe it’s not that bad. As other comments mentioned, TSP cleaner and Kilz paint might be enough.
I don’t see how this proposal makes any changes. Your account is already unique and usable across the fediverse.
A key used for authentication is really just a long password, anyway.
If you mean you should be able to log into server A with your account registered on server B, that doesn’t need key auth. Password auth would be fine, it’s just not implemented (at least on Lemmy or any other fediverse platform I’m aware of). Authentication isn’t federated, only content.
That talks about the credential store, not disk encryption.
Manipulative algorithms, yes.
I’m more of a nine fives guy anyway.
But the big brain move is that planned outages don’t count against five nines.
If you don’t want anyone to be able to read it, don’t send it to anyone.
I would just go to your local hardware store and walk the aisles.
You could fabricate something out of thermoplastic or metal, but I’d be concerned about it creating a crevice for mold to grow.
Why do you need port 80 specifically? If it’s for your own use, you can run http on any port. And you should be using https on 443 if at all possible anyway.
It’s open source, so you can read the code.