PrincipleOfCharity

Now I think I see what you are saying. People have suggested that Lemmy needs a separate protocol to connect with other Lemmy instances to more efficiently synchronize. Gossipsub could do that. It would also be nice if each Lemmy instance only needed to keep a minimal amount of data at any one time to service the clients that connect to it while the rest exists in the swarm.

I still don’t think that you would want a phone to function as your server and your client, though. All that coordinating takes bandwidth and processing power. Phones are ill-equipped for that. Also, usually to p2p effectively you need to be able to make direct connections through firewalls. Opening your phone directly to the Internet would be a bad idea, plus I doubt any phone companies would let you do that. Without a direct connection, you would need to proxy your connection through some server somewhere and deal with bandwidth costs. Might as well just connect to a server as a client.

Maybe the final solution is software like Lemmy running with decentralized identities via the Nostr protocol that is federated out using Gossipsub.

Then the p2p network is really the “server” and the phone is still just a client. I’m also not sure that a p2p network could be queried very well because something would have to be able to produce aggregated and sorted results. It isn’t like pulling one file from a swarm. It would be like a blockchain and the phone would have to download the whole dataset from the p2p network before running queries on it.

What you are talking about sounds kind of like the Nostr protocol. It is a distributed social network trying to solve the same problem that ActivityPub is but in a slightly different way. All the events are cached on multiple relays and the client applications query those relays looking for information that gets aggregated and sorted on the client however it wants.

ActivityPub is all about pushing content around to subscribing servers. It sort of expects the subscribers to always be online which would not work for a phone. Servers could resend missed events, but essentially you would miss every event that occurs while the phone is asleep or doesn’t have the app running.

Also, every event that occurs needs to be processed and stored whether or not you are actively looking at it so it would be a huge battery drain while it was running.

It is definitely a service best run on an always-on server with a client application in a phone just asking the server for the latest stuff on-demand.

You can do that, but there are a couple of things to keep in mind.

Different apps may only be compatible with certain database products and versions. I could be a real pain if you have to spin up a new version of a database and migrate just for one service that updated their dependencies or have to keep an old database version around for legacy software.

If you stop using a service then it’s data is still in the database. This will get bloated after a while. If the database is only for one service then wiping it out when you are done isn’t a big deal. However, if you use a shared database then you likely have to go in and remove schemas, tables, and users manually; praying you don’t mess something up for another service.

When each service has its own database moving it to another instance is as easy as copying all the files. If the database is shared then you need to make sure the database connection is exposed to all the systems that are trying to connect to it. If it’s all local then that’s pretty safe, but if you have services on different cloud providers then you have to be more careful to not expose your database to the world.

Single use databases don’t typically consume a lot of resources unless the service using it is massive. It typically is easier to allow each service to have its own database.

I’m confused. Isn’t the commission that is paid just a cut of the profits from sales? The 85% not paying commission would be because their app is free. Apple’s argument is that they are providing a huge platform and infrastructure for app developers; many of which are utilizing it for zero cost (except the annual $99 developer fee).

If someone then uses that infrastructure to make money then Apple takes a cut of either 15% or 30% to help sustain the whole thing. Those numbers are argued to be too high although they are basically in-line with the mark-up of most goods and services.

The real complaint is that Apple doesn’t allow alternate app stores that would compete, and theoretically push down the commission to whatever the free market determines is reasonable (and presumably below 15%). Apple, of course, argues that they do it for safety purposes. One way to offer lower commissions is to have less strict screening processes to save money. This could end up being a race to the bottom of quality which may not really benefit users.

I was like, “Portainer costs money? When did that happen. I thought it was open source.” Granted it has been awhile since I used it.

You want to check out the Community Edition. Here’s their Github.

Physics and math. J/k. I’ve seen similar numbers thrown about. Here is a link to a Quora question What happens to the human body when a submarine implodes from 2 years ago that may be of interest.

When a submarine hull collapses, it moves inward at about 1,500 miles per hour - that’s 2,200 feet per second. A modern nuclear submarine’s hull radius is about 20 feet. So the time required for complete collapse is 20 / 2,200 seconds = about 1 millisecond.

A human brain responds instinctually to stimulus at about 25 milliseconds. Human rational response (sense→reason→act) is at best 150 milliseconds.

The air inside a sub has a fairly high concentration of hydrocarbon vapors. When the hull collapses it behaves like a very large piston on a very large Diesel engine. The air auto-ignites and an explosion follows the initial rapid implosion. Large blobs of fat (that would be humans) incinerate and are turned to ash and dust quicker than you can blink your eye.

I believe the point of OP’s “thought” Is that death-by-implosion is basically instant (30 milliseconds) so it could be considered more humane than other methods.

Not sure if this is the same problem, but it has been noticed that passing messages between federated instances has been hampered by the way the “worker threads” are currently been done. The big instances are essentially getting overloaded with outbound federation work. Solutions for that are in the works. issue/3230