Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Searching for "the five requisites for blockchain use" isn't finding anything relevant, what requisites do you mean?
This wouldn't be storing more data, it would be storing existing data. It would just be putting it somewhere that can be globally read and verified.
How do you store data in a decentralised way without have many redundant copies? The decentralisation of Blockchain is from many machines maintaining their own copy of the entire history. The entire xo dept I herebtly stores more data. Your suggestion is to literally store more data, claiming it won't store more data only suggests you don't know how blockchain works.
And that's not even including any overhead of implementing a Blockchain in the first place. Or the fact you'll be storing data on literally every user even if they never interact with your instance, pr even if their instance is entirely blocked from yours. And there's no way around that, if you do manage to selectively store some subset of users then when you do need to include that data you're trusting the subset of maintainers who do have that user's data which, initially, is only the user's home instance so we're back to square one.
Yes, my point is that that sort of thing is exactly what blockchains are for. They handle all of that already. So there's no need for Fediverse servers to reinvent all of that, they can just use existing blockchains for it.