Avatar
tegila.js
e9ae796ea6af44ad46fa7b8c4bae4612ece321a01bbd9d866a68232835b2078e
Js, c dev

Yes it did.

In some places, in the country I live, you can’t even reach to the beach sand because it’s owned by someone powerful enough to expel you at gun powder without being subject to any law.

God bless law and order.

Yeah but they don’t, same as with email. Soon Google take control of everything and we’re left with bad code practices.

Also it’s not a network if you can’t search/discover thru it.

Replying to Avatar Alex Gleason

Check: https://docs.soapbox.pub/ditto/signing

Ditto is a legacy REST API server similar to Mastodon. In this design, NIP-46 is the most viable way to sign events.

Soapbox (the frontend) has been updated to include a full NIP-46 signer implementation. When you use it, it uses NIP-07 over NIP-46!

This design is actually insane. But it also makes the most sense. The frontend (Soapbox) is not a "Nostr client" at all. It is actually a Mastodon client. The Ditto server is a hybrid Nostr client and relay, and it is actually the Ditto server which publishes your event to other relays.

Relay owns the content not the content creators

Because clients still didn’t condensate same ids or reference threads.

Can we use the npub to pay and avoid all this lightning UX nightmare.

I’ve already setup 3 AWS instances only to setup my #nostr profile.

JS is fine. The Typescript guys who are messing around.

I’ve done many nostr webpages using js only and very tiny. Without webpack or uglifyjs.

Only