ok, you make good points, but i feel like the algorithm could work to not have the system grind to a halt. i'd have to look at other examples where this has been done. but maybe i am overly-optimistic and it's not possible.
who would pay for those nodes you are querying
the people who are already running nodes, like lemmy.world, lemmy.ml, me, etc. i run some services on my home server that i let anyone use, because i have the hardware and the bandwidth to be able to afford it. there are enough people who have the necessary hardware and bandwidth to contribute to it at minimal detriment to them. it's already an open-source project where people volunteer their time to code it.
i'll read up on oxen network.
in an anonymous way
wait who said anything about anonymous? what are talking about being anonymous? there would still be user accounts.
if I don’t want to aggregate all the posts in the world by myself (as you are suggesting), then I’ll have to fine someone to do it for me
this is already what is done, except that the data is not stored in a replicated and distributed manor. you get all the posts in the world of a community of an instance. it is one server, with all the data stored on its harddrive, like a traditional website. in what i'm proposing, this is also what would happen in many cases, because the thing wouldn't requery the entire network every time you request posts, there would be a time threshold, like how posts are cached on your local mobile device for most social media apps. posts would be cached on the server.
now, yes, this architecture would in fact result in more network traffic occurring between each and every node, as they receive updates about events on other nodes. so that would be extra burden upon the hosts. but i believe it is something we can work through.
the advantages of this:
OR, after changing the ID, have the instance publish a "domain_change_notification" that all federated instances would be listening for and then they would update their data.
ah ok. well then there would need to be a deeper change and all instances would need to update. have a field for the ID of the instance itself, and a field for the domain. or something like that. would that work?
ok. so you are misunderstanding what i am proposing then.
i can explain in more detail any part of the design if you wish.
you want to strip all that out
i do not want to strip out the functionality of communities having mods that moderate the discourse and ban malicious users etc. it sounds like you misunderstood what i was proposing.
AFAIK there is no reasonable way to update/change this. IDs are forever.
can't you just run a postgresql query to update all the post ids?
This is all different when building a social network
wait you want censorship in a social network? also, the architecture i'm describing does not do away with moderation and social structure. what about it makes you think that to be the case?
Wish we had the option to add it to the bottom
@apple @android feature request here. submitting ticket.
subject to the whims of global capitalism
so how can we make that not be the case? this is what engineers and innovators are thinking about. we are thinking about what the next system will be and planning how to get there.
@LordShrek
@lemmy.world