Nostr Web Client

Solid is designed by alot of people at once, and as expected it is very underpowered, barely any better than WebDav, it has no sovereign identity and data is not encrypted at use, meaning unless you run your own Pod, your host can see everything.

Peergos is great and honestly so very close to the optimal, but it also didn't start with sovereign identity, relying on a centralised PKI, although they plan to mend that, and I don't like that it runs in web browsers for no reason really, and the only way to build apps for it is to build web apps.

Finally Peergos currently has too much latency for my liking and I suspect I will never know if this is a fundamental price of excessive privacy, or an implemtation detail unless I implement some parts of it in Rust and see how fast i can get it to work.

Nuh 10mo ago

Another thing about Peergos is that it puts so much effort into being p2p friendly with IPFS baggage and complexity that is only needed for people to be able to host random parts of your data in a p2p... I personally think all of that baggage is not helpful... no one uses peergos in a p2p manner nor they ever will.

So the question is how much simpler can we get if we remove all of that Protocol Labs stuff.

Reply to this note

Please Login to reply.

Discussion

netrau 10mo ago

I like it. But before going into codding too much would be better to have a scope defined first? Something like.

1. What is what we want to achive?

2. Some example - these details you exposed here for example are pretty good.

3. How does, in general terms, the ecosystem will look like?

Idk, few lines explaining the whole idea/goal.

In general, I think I got the gist of it, but some sort of document to follow alone would be great.