view the rest of the comments
Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
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 !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
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 info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
it cannot really replace a simple database. it has an integrity guarantee. not in the way that data won't get modified accidentally, but that it won't get modified onesided.
the git version control system also uses a kind of a blockchain structure. git was made by the creator of linux. a major difference is that git does not use proof of work for consensus, I think it just does not use anything for that, other than the web server's access control mechanism.
commits are built on top of a large chain of histories, and the commit ID verifies that the current state and the history of it is the exact same when you checkout that commit ID on any other computer. if you go find in the repository a commit made 3 years ago, and change that commit (this is supported by git but not recommended), either the content or the metadata like time of commit, the whole history after that also need to get rewritten to remain valid, and so all those commits will now have a new commit ID