Plebbit is a selfhosted, opensource, nonprofit social media protocol, this project was created due to wanting to give control of communication and data back to the people.
Plebbit only hosts text. Images from google and other sites can be linked/embedded in posts. This fixes the issue of hosting any nefarious content.
it has no central server, database, HTTP endpoint or DNS - it is pure peer to peer. Unlike federated instances, which are regular websites that can get deplatformed at any time,
ENS domain are used to name communities.
Plebbit currently offers different UIs. Old reddit and new reddit, 4chan, and have a Blog. Plebbit intend to have an app, internet archive, wiki and twitter and Lemmy. Choice is important. The backend/communities are shared across clients.
The code is fully open source on
You could do the same with DNS, nothing is stopping you from registering a similar domain name and doing the exact same thing. ENS doesn’t change anything with the attack, it merely exchanges registrars for a block chain.
Except dns requires proper registration, and has a place to report abuse, and those reports are actually acted upon. Moderation here is not preventative, it’s reactive.
Stop trying to justify this approach, a blockchain is cool but you’re really just monopolizing domain registration
Oh, I think the approach is problematic, I just don’t think ENS is a major concern here. I don’t think you need DNS/ENS for this kind of service, nor do you need any form of blockchain.
My point is a blockchain DNS system isn’t significantly worse than the current system, where we already see a ton of similar abuse. The proper solution, IMO, is to avoid the need for DNS at all.
Accurate, what would you do instead of dns though?
Nothing?
DNS exists to give an authoritative answer for who owns something. I would have a completely different design where nobody owns communities.
Basically, I’d treat communities as topics that live on a DHT as keys, posts would be keys semantically related to the community (e.g. “communities.<community>.posts.<post>”), and so on. Anyone can post to that topic or to any posts or comments related to that topic by creating subkeys, all of which use UUIDs to guarantee uniqueness. All entries in the hash table are signed by the author’s key, and people can create identical entries (i.e. the same key), which can be distinguished by the signature. The signature is important, because we can’t trust timestamps to distinguish between collisions (e.g. someone mimicking someone else’s post id vs someone editing their own post).
Moderation consists of a web of trust system, where users are given weights based on how much you trust them. When deciding whether to display a post, you’ll check the moderation of that post by people you trust, and show/hide it accordingly. The same goes for votes, you could disregard votes from users you consider spammers/trolls. Building that moderation graph is largely automatic, if you vote or moderate similarly to someone else, you start to trust them more, and their weight in your graph increases.
In other words, nobody owns communities, so there’s no reason to have DNS, and the main reason to have DNS is for moderation, which becomes moot when moderation is itself distributed.
A domain name system is for naming domains, not moderation. And just use a database instead of reinventing the wheel.
That alternative “show if trusted” approach would be nice in an ideal world where everyone already has a perfect filter bubble with only their perfect friends. But unfortunately the world isn’t like that.
You gotta learn to walk before you can run
Right, plebbit seems to use ENS to connect a name to a place. If the name doesn’t point to a place but instead a distributed collection of posts, you don’t need a domain name system.
A DHT is a distributed key value database. I’m modeling everything in terms of structured keys using existing data structures.
Moderation is the hardest nut here to crack, and that’s pretty much the entire point of this experiment: can I build a distributed trust system? I’ve read a few papers on approaches that could work, and this transitive trust system should do okay. The idea is that I trust user A by X%, A trusts B by Y%, so I should trust B by something less than both X% and Y%. To get a decent result, I need enough data to make it work well, but not so much that computation is slow.
I think it’s feasible. If it works, we don’t need centralized moderation, which solves a ton of problems in current social media networks.
Note: we don’t have centralized moderation here either. We’re talking in two completely different instances. Just like plebbit would have
It’s still centralized in the sense that there are specific individuals who have moderation power. If you think of each instance as a separate thing altogether, it’s the same as Reddit.
No, it does not “seem”, it explicitly states.
A hash table is a way of storing data, I suppose you could call it a very primitive database. But that’s not the common usage of the word database. Hash tables are used in database indexes, hence why I called it “reinventing the wheel”.
The naming system is still a central part of any network, even if decentralized in design. So it will need some sort or central moderation.
One issue with ens though, is that the control over it is more centralized than dns. But without regulation, it’s worse than the existing solution.
I haven’t used the service or reviewed the code, I’ve only read the whitepaper and read the website. Early stage projects like this have a habit of stating this things that aren’t yet true, hence the uncertainty.
It sounds like you’re limiting your definition of “database” to relationship databases, there are a lot of other types of databases out there. The most common use case for Redis, for example, is as a key value store, and a hash table would be a perfect way to implement that. I’ve used
redbin this project, which is a disk based key value database.Sure, but DNS systems are authoritative, meaning there’s only one right answer to a given query. This requires synchronization across the network, which creates a ton of complexity.
If we can avoid that synchronization, the design gets a lot simpler, which makes it more robust. In my design, I’m specifically avoiding mandatory deletes and updates, so the only operations my “database” needs to support are creates and reads. Communities are just topics you can post to, and moderation is just client-side filtering. The tricky part is getting the client side filtering good enough to not give spammers and trolls too much visibility.
Some nice parts about this: