i got annoyed that posting would never work on the seedit web client, so i set up a new instance that reverse proxies the p2p interface as a public instance.
it's more or less an experiment whether this could work at scale if at all. it's meant to be a temporary solution to the >pending problem that i hope can work for a while. browsing and posting seems to be much faster and hasn't failed once from my tests (if the sub is online ofc)
you can check it out here:
* seedit: https://plebbit.works
* plebones: https://plebbit.works/plebones/
plebchan isn't available unfortunately
maybe you will notice that you can create subplebbits there, but every user that accesses plebbit.works is an admin for all of them (meaning they can delete it, change it, mod it, ...), so don't do it.
if you have feedback post on this thread. if the web server dies from too many people using it i'll notify you here too.
Maybe I will make a new thread, but plebbit.works now redirects to plebbit.mooo.com (a free domain) because the plebbit.works domain (ironically) doesn't work sometimes. I guess it's a weird issue with the domain registrar but I don't want to pay for a new domain or transfer it, so I opted for a new, free domain.
It's now also available via Tor: http://zfahbff3nwautscwwqyxvquruig25wwxudssxaqprczoxofvpuf2htyd.onion/seedit/
Accessing it via the onion link is more reliable if you're on Tor anyway.
This is great. We need more experimentation with plebbit. It's the only way we're gonna find out what's the best design in terms of optimal UX for the average normie user.
Maybe there will be a monetization model in the future where people would host frontends like this, and in return get a % of tips made by the user. It would a big competition between hosters to attract users. Developers will start developing caching systems on top of Plebbit that will predict what the user is interested in, and fetch it before they ask for it. Normies will have a pretty smooth instantaneous experience. When you try reddit.com or other social apps, you're bombarded with ads that makes the UX much slower and worse. They have to do that, because their corporate interests aren't aligned with the UX, but in Plebbit case it's extremely aligned. There will be hundreds of clients that caters to every type of users, and they will be interoperable with each other.
We need first to further develop the RPC API of Plebbit. Right now if you connect to an RPC, you're assumed to be admin and you have full privileges. But we will have a permission system where somebody can only create and manage their own subs. Or maybe no subs at all, but they can use the RPC to browse and publish.
I like what you have done, we don't have a simplex group but if you would like you can create one and mirror our TG group there. You should also drop your ETH address, we don't have tipping implemented yet, but we want to foster an ecosystem where projects that serves the decentralization goals of Plebbit are rewarded.
reposting in the comments because the text doesn't show up on seedit:
i got annoyed that posting would never work on the seedit web client, so i set up a new instance that reverse proxies the p2p interface as a public instance. it's more or less an experiment whether this could work at scale if at all. it's meant to be a temporary solution to the >pending problem that i hope can work for a while. browsing and posting seems to be much faster and hasn't failed once from my tests (if the sub is online ofc)
you can check it out here:
seedit: https://plebbit.works
plebones: https://plebbit.works/plebones/
plebchan isn't available unfortunately
maybe you will notice that you can create subplebbits there, but every user that accesses plebbit.works is an admin for all of them (meaning they can delete it, change it, mod it, ...), so don't do it.
if you have feedback post on this thread. if the web server dies from too many people using it i'll notify you here too.
Plebscan