2 ms·
Why not publish the changes too? The data of the resulting json can include whatever you wish. That data is your data. So if an app developer wants to include t
by reactordev 1y ago
Why not publish the changes too? The data of the resulting json can include whatever you wish. That data is your data. So if an app developer wants to include the history of changes, that would be the place to do it. Or link to previous at:// addresses for it. Walk it back like a linked list.
As for the identity moderation part, if you read up about DID, it tells you how to know who they are and you can block them or do whatever you need to do. The point isn’t that this is some blockchain, it’s just a federated method to share data when you own the data. Poison well attacks aside.
In the end, it’s a way to say this person, generated this data, at this location, in case you’re interested. If you care about the things you mentioned, you might not be interested at all.
- crazygringo 1y ago> Why not publish the changes too? Because you are being adversarial and trying to trick people. > if you read up about DID, it tells you how to know who they are But it doesn't tell you're they're not a spammer. I don't see anything about reputation. > in case you’re interested But that's the point. You're interested in legitimate upvotes to try to find useful content. You're not interested in spam upvotes. In a decentralized world, how does anyone tell the difference?
- verdverm 1y ago> I don't see anything about reputation That's a hard problem obviously. In ATProto, we are using labelers for verification, anyone can run and validate anyone, apps can decide which verifiers they trust. Bluesky runs their own, let's the NYTs verify their contributors, and has allowed one well known, independent user who's been verifying people. These all show a badge in the app