this post was submitted on 09 Mar 2024
1297 points (94.2% liked)
Lemmy Shitpost
26728 readers
3860 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Git doesn’t need consensus mechanisms because it’s “permissioned”, like Hyperledger. All actors are known and given permission by some entity to contribute.
You can’t contribute to the Linux kernel unless your changes have been approved by someone trusted with permission. You cannot contribute to whatever Walmart is doing, because you haven’t acquired permission to do so.
And?
Hyperledger Fabric still uses a consensus mechanism, and I promise you Walmart uses one. You can't trust China with food safety.
Permission is given out to various suppliers with various levels of trust.
"Permissioned" in the context of Hyperledger Fabric just means all participants are known entities with identities managed by a Membership Service Provider (MSP), which is likely Walmart in this case and have access control governed by policies ensuring that only authorized actors can interact with the network and its resources. It doesn't mean that a consensus mechanism isn't used or needed.
Shit, without using GPG and SSH to sign commits and outside identity verification mechanisms, you run the risk of git identity fraud.
In what way can blockchain ensure food safety? Just because participants use proof of work or whatever doesn’t mean the input data is more truthful. The oracle problem is a thing.
By providing transparency, auditability, and traceability throughout the food supply chain.
Or in other words it prevents fraud via a tamper-proof system for data collection and monitoring. If the input data is falsified and people to get sick, it's just a matter of plugging in the QR code for the contaminated product and within seconds you know the identity of the participant who authored the product and where it came from. The identities of all participants are already known before hand by the Membership Service Provider.
Think of it like as if someone signed a malicious commit with their GPG key containing their name and address but with additional tamper-proofing pushed to an immutable repo, it's not going to be very hard to trace back and slap a fine on whoever is responsible; effectively greatly reducing the Oracle problem.