Nostr Web Client

The ID never goes away, we won't purge it, however if you do remove it as your identifier, you would no longer be listed in the directory and in the future you wouldn't be able to gain write access to our relay if your ID is different.

pet 2y ago

Please, consider using relay authentication via nostr protocol (uses the keypair), not via NIP05.

Thanks!

Replying to

Sirius

Renamed to "ignore"

pet 2y ago

Much better than "block"

👍

Replying to

Sirius

I wish we had polls on nostr.

pet 2y ago

https://github.com/nostr-protocol/nips/pull/148

pet 2y ago

That's exactly the reason why it proposed to allow setting NIP-05 aliases by a DNS record (TXT):

https://github.com/nostr-protocol/nips/issues/146

No webserver, no HTTPS certificate, no maintenance.

It was discarded right now as it complicates the protocol and it's no implemented anywhere.

Let's hope it can get traction and support.

pet 2y ago

#[2]

Replying to

Sirius

Hmm, I'd still like it to be a low barrier of entry way to try out Nostr. Maybe some notification that prompts to use extension, after you've used it for a while?

Unless you're on mobile, where extensions won't usually work. For Android I think PWAs can be actually packaged as "native" apps. Idk about apple, probably not.

pet 2y ago

Another option to easy the entry way is to automatically generate a new keypair and later offer the option to the user to sign Key Delegation tokens if they want to post on behalf of another different privkey.

Replying to

lapulpeta

Not yet. But it's open source so you can always inspect the code and build it yourself for extra security.

pet 2y ago 💬 1

Ok. Thanks for the answer! 👍

Replying to

jack

Worth it

pet 2y ago

🙏

Replying to

lapulpeta

Did you check out Nostrid by any chance? 🤔

https://github.com/lapulpeta/Nostrid

pet 2y ago 💬 1

Is it available in the Play Store?

pet 2y ago

Let's hope some day it's allowed to validate a domain via a DNS record:

https://github.com/nostr-protocol/nips/issues/146

Replying to

daniele

Perhaps we can thing about editing with a revision system.

Then this incidentally create nostr-git :)

pet 2y ago 💬 1

This should be useful for the proposed Decentralized NIPs managament too.

Replying to

Sirius

Current message kinds are for social networking, but if you wanted online stores for example, you'd have to define a new set of message kinds.

Unless you have a k-v storage / graph database. Then you can do nostr.put('npub123/store/items/socks/description', 'Pair of alpaca socks').

pet 2y ago 💬 1

A new message kind for products on sale could be a nice idea, that's true.

One for offers and another one for requests.

These message kinds should then be used by different implementations of online shops (webs & apps). An eventual #nostr-uber and friends could use these same kinds