SWIM's avatar
SWIM 6 days ago
Unfortunately, I have no clue how this could be solvable. _Perhaps_ part of the root cause is the decentralized structure and different routing to actually access any given profile/note ... So the easy way out would be not only a faster information protocol but also nodes with more locally stored data - aka centralization, which simultaneously steer small node operators away from the network (cost). Maybe better client side caching could solve it more sustainable - e. g. when reading a thread the profiles of the thread participants might already be loaded. With the cost of increased network traffic. Having all clients behave as small nodes would be cool but probably not feasible. If that is, how its already how it works, I'll better shut up :D I am not a technical person really.

Replies (1)

I'm pretty sure the centralised routing of content is a major part of it but i have to wonder if the physical servers being used are up to the job. Some of it will be down to clients, and the various ways they pull, deduplicate and prioritise loading. It's even harder for web clients. But these are the things that definitely need fixing. Not kind 1111 replies. That's just so not important at this point.
↑