Avatar
fiatjaf
3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d
~

Since it is not an link it doesn't work with my magical nos2x contraption: https://twitter.com/fiatjaf/status/1611360436162633729

It also doesn't work on my Chromium/Linux to trigger the native handler.

I plan to behave the same as I do with Bitcoin.

Yes, that. It is not written anywhere and barely supported, except in Damus and nos2x, I believe.

#[4] #[1] #[3] #[2] can we have native handling of nostr: links?

We should probably have a NIP for it, but the NIP contents would be: "just prefix a NIP-19 identifier with 'nostr:'".

Replying to Avatar fiatjaf

https://nostrum.pro and https://nostr.band are excellent search engines, but they really should add support for the nostr: link scheme instead of hardcoding web clients. The web client I use is not there, the desktop native client I use is not there and the Android client I use is not there either. The universal way forward is nostr:npub1... and nostr:nprofile1..., please!

I guess they could also provide the hardcoded clients as options, but include nostr: too, please!

Replying to Avatar fiatjaf

https://nostrum.pro and https://nostr.band are excellent search engines, but they really should add support for the nostr: link scheme instead of hardcoding web clients. The web client I use is not there, the desktop native client I use is not there and the Android client I use is not there either. The universal way forward is nostr:npub1... and nostr:nprofile1..., please!

#[0] #[1]

https://nostrum.pro and https://nostr.band are excellent search engines, but they really should add support for the nostr: link scheme instead of hardcoding web clients. The web client I use is not there, the desktop native client I use is not there and the Android client I use is not there either. The universal way forward is nostr:npub1... and nostr:nprofile1..., please!

Most (but not all) clients will just automatically render any image URLs they find in the note body.

I would assume these are spam. On Twitter it is very hard to find people following more than 1000.

Finally: #[0]

If clients were a little smarter about how they treat each relay (i.e. asked different relays for different things depending on what they know about each) I think this would fit well into relays -- not as "part of the protocol", but just as an extra thing you can request. Putting it on relays has the small advantages of

a) reusing the communication channel; and

b) making it interoperable so these tally providers can be easily replaced (not that an HTTP provider couldn't be like this too).

I just don't want clients to start requesting tallies from every relay and then every relay thinking they must implement this because somehow it is "part of the protocol" or "everybody else is doing it".

I've commented there, but I think it is not good since the new domain owner can revoke your keys if this is to be trusted.

I think something like https://github.com/nostr-protocol/nips/pull/158 is a better solution. I wish people showed more interest in that.

If you want to build a client, try to do something different and maybe excel at that -- instead of just trying to make yet another Twitter or Damus clone.

#[0]

Is https://coracle.social working for you? I had high expectations from that, but apparently it is looking slightly abandoned. I wonder if someone could pick it up and improve it.

#[0]?

This somewhat-stupid note was only made because I wanted something to record a video for https://twitter.com/fiatjaf/status/1617546240878645250.

What client are you using?

First Jack, now Snowden?

#[0]

This is becoming suspicious. I think Nostr may be a plot from the globalist elites to get us all thinking we will have free speech again while they prepare the locks for our cages.

You mean after 13 years Nostr will be largely unknown to the general public and there will be thousands of Nostr centralized copycats that take your money and run away with it?