Oddbean

▲ ▼

 I spoke too soon. Still slow when using hex ids e.g.

https://njump.me/e26b8498fc84c1f709c81b1689b636ffec203d9b7a0d19e3236fe06c5a3242d0

It’s redirecting to http from https which is weird.

▲ ▼

 Maybe the first time? For me this url loads instantly now.
I don't see any https -> http redirect; actually the inverse redirect takes place.

▲ ▼

 Could be. I created an nevent manually with a relay hint to get it to load.

▲ ▼

 Your mentioned a hex id, not an nevent. What take a long time to load?
All events or just the ones you created manually?

▲ ▼

 I meant it wasn’t loading for me with the hex id, so I manually created an nevent for my hex id to get it to work.

▲ ▼

 Usually I let Njump create the nevent from my hex ID, but that doesn’t seem to be working well

▲ ▼

 If the note was sent to a relay that njump does not know about, it cannot find it and therefore converts it to a nevent. The note was sent to relay.damus.io?

▲ ▼

 I found it on relay.nostr.band and that’s the relay hint I added to get it to work

▲ ▼

 I confirm that relay.notr.band is not used to look up raw hex ids.

▲ ▼

 Do you know why? That relay has everything. 😂

▲ ▼

 Actually, I don't know. Probably to incentivize the use of hints. I need to check better.

▲ ▼

 I use Njump to create the nevents with hints for me 😂

▲ ▼

 Why? Which is the use case?

▲ ▼

 My app Quotestr doesn’t support using hex IDs. I use zap receipt hex IDs on Njump to look at zap receipt events to see if they seem legit. Then I copy the event with route hints that Njump creates and use it on Quotestr.

▲ ▼

 I see.
Maybe you can create a simple command line tool to quey a large set of relays and create the nevent.

▲ ▼

 i can create the nevent with route hint in my script. i've just been lazy. 😂