doesn’t rely on any servers or instances .

Yet is hosted on Github and presumably requires a working DNS and HTTPS system to download.

Users connect to your node directly, p2p, and nobody can stop you.

Except your ISP and/or government.

the protocol is text only, to embed media, you need to host it on the regular ( Centralized ) internet, and then you link to it like https://example.com/image.jpg, and the host will stop hosting that image and report your IP.

So your supposedly non-centralized project requires external hosting? It’s like NFTs where the images were just worthless links. :P Also, uh, base64 encoding is a thing and clients will absolutely start supporting it.

the community creator can assign mods, mods can remove posts from that community.

… Isn’t this what you’ve been trying to avoid?

if a community is badly moderated, the user will never see it, it wont be recommended to him.

Finally, a mention of content discovery. How is your recommendation system implemented? What decides whether a community is worth being recommended?

Also being p2p, seedit is not private, so it can’t really be used for illegal activity

Wait… Isn’t your whole pitch that it was censorship resistant? Can you clarify your threat model here, who are you actually worried about censoring your platform?

[ActivityPub servers] are hard to run and manage.

And using a completely unknown new service and protocol isn’t? I’m sure there’s tons of documentation out there for hosting Mostodon or Lemmy servers.

the problem with federated social media is that each federated instance is just a regular centralized sites.

I agree with this, but not for the reasons you’ve stated.

P2P also scales infinitely, which is the reverse of centralized websites like federated instances: the more users there are, the faster it gets.

P2P scales much worse than centralized systems. Centralized systems scale at N connections per node, while P2P systems scale at N^2 connections per node.

You know what, I don’t mind this project. We need a place for far right people to go to to avoid “censorship” (getting banned from a subreddit for doing nothing but throwing slurs at people) and collaborate on their “plans” (killing minorities) on a platform that is “private” (easily traceable, unencrypted and linked to your IP address).

The most important thing about social media is the first word : it’s social.

This sounds like a technically impressive medium, but if it fails to get a healthy community (which means, not just 4chan bros) then it will die.

I’m going to post it again.

For anyone else looking for a reason to stay away from plebbit- uh, look at their X account https://x.com/getplebbit It’s 4chan crypto hashwash

the problem with federated social media is that each federated instance is just a regular centralized sites. They can censor each other,

Also, this is a feature. This is intentional.

I’m concerned about the large amount of low quality, vaporware/crypto applications built on IPFS which is the same core technology used here. It’s concerning how many clicks it takes to get technical specs for the underlying work, like libp2p for the network layer, which itself espouses only vague ideas on its main website that seems to focus a lot more on presentation than technical merit. Even the GitHub admits that the spec that most of these apps are relying upon is, well, unspecified.

Your project source downloads and runs an executable. That’s a little bit SUS; it would be much better if you compiled/built this core code as part of your build process, else, it’s not much in the way of source code, no? But, it works. It seems to delegate just fine, and few understand how to actually talk IPFS directly. But, this is the most important part!

I think the biggest tell that IPFS borders on vaporware is that there’s very little discussion about concrete specifications and the main problem faced by all DHTs: how you get your data to actually stay hosted on the network over time. These ideas are not new, and you may be better served building your app on technology that has spent vastly more time understanding the fundamental problems.

https://specs.ipfs.tech/

This is how you write a spec without actually writing a spec. And I’ve written a lot of specs.

https://geti2p.net/spec

This is how you write a spec. Excruciating detail of what actually gets sent over the wire at different levels of the design starting from the very bottom.

Anyway, just my 2c. It’s cool you’ve got functionality at this level and that’s commendable, but I feel it’s built on shoddy foundation of an immature technology. At least it should be easy to migrate to something else in the future as the distributed technology is offload to a separate binary anyway.

Note: Various edits for clarification and to ensure I focus on the code and not the human.

Peers can connect to your subplebbit using any plebbit client, such as Plebchan or Seedit. They only need the subplebbit’s address, which is not stored in any central database, as plebbit is a pure peer-to-peer protocol.

Do I need a new plumbus or will my existing one work?

I am really impressed. Thanks! I will be having a deeper look.

Side note: lemmy.world people are irrationally triggered by some stuff you mentioned: blockchain and cryptocurrencies (this is the same as being triggered by ssh 🤣), or religion, … Keep that in mind while you read 'the feedback" here.

the protocol is text only, to embed media, you need to host it on the regular ( Centralized ) internet

except we already figured out how to encode images (or any file) as text when E-Mail was created. That is how images in E-Mails, attachment or embedded, are done. I can easily imagine a userJS script that will render them in the browser, but even if not you just copy the text and decode.

if a community is badly moderated, the user will never see it, it wont be recommended to him. the user can visit bad communities directly just like you can visit a bad website directly, but it’s not recommended to you so it’s safe to use.

Ah… so you’re guaranteed to have a dark CSAM subculture on there at some point.

being p2p, seedit is not private, so it can’t really be used for illegal activity

As if that has ever stopped anybody. See all the people that got caught for sharing it on the clearnet. Or on Signal, Telegram or similar, where you have to enter your phone number, which is personally tied to you.

All in all - Great way to adress the concerns, by admitting they are in fact possible. “Hurray crypto” or whatever.

I do like the idea of a P2P system. I used to be on ZeroNet but there were just too few people and too little content to stick with it. I hope something like this takes off.

deleted by creator