No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
So, if I get it, it's like torrent, except instead of you manually verifying the hash code, each computer your file passes pay automatically checks and says "yup, the file I received and transmitted is the file I was supposed to receive and transmit" ?
pretty much, think of the files like what you would see in your .git folder for a code project. they are all linked together in a history graph. so you are validating the data, its position in history along with its entire history, you also know who changed the data and what systems were responsible for writing those changes. really solid tooling for provenance and chain-of-evidence scenarios.
I see, but if I'm not mistaken, git is anterior to the blockchain. What I'm asking here is what new things the blockchain brings to the table, that preexisting protocols like Git or P2P couldn't do. Or is the blockchain just another application of the same principles (the Merkle chain, as a previous commenter was saying)? If so, what sets it appart ?
I'll refer to one of my earlier responses someone asked about this in context of a process like docusigns'
so if you are looking at this its a question to trust scopes, at least in public systems. here you are trusting:
the proposal for a decentralized ledger with neutral execution is that the only “trust” needed is that in the contracts function, however this is not entirely true, in reality you are shifting trust to:
your ability/resources to asses the contracts function and your counterparties.
some people feel this is a better way of doing things, ive found it interesting to work in the space technically but I dont necessarily agree with the wildwest nature of the public systems and am more an advocate of regulated channels if these are going to be done at all. There is also the idea that a large enough network makes it possible for the network to handle larger loads than any individual processor could handle, this has borne out in some cases though its not perfect since we know P2P network instability tends to ripple through a network.
Finally if an application has been built with web3 practices enshrined its entirely possible to ensure service continuity even in the event of the provider failing financially and being unable to serve the users. Important to note this is RARELY done properly and I have only seen a couple cases where it worked so far. However personally this is one of the most impressive features, I am biased however as I was involved in the recovery of a commons that has turned into a defacto standard. Didn't make anything from it other than consulting feed, just really cool to help a non-profit
If we are talking the internal org, like docusign itself, an org like might adopt a ledger based system for the in-built capabilities of some chains, you find quickly that enterprise grade cryptographic tracking of large scales of assets or process gets VERY expensive. Ledgers can be very helpful in these cases though are more a consideration when validating a new system rather than it being an impetus to upgrade in and of itself.
I often refer to it as a specialized app-server stack to clients.