Thread

Npub worked but NIP-05 did not for me

Happy to test your site, just gave it a spin using firefox browser and nsec app to log in. Unfortunately the page hangs when I go to 'view profile' and I get the spinny icon and loading posts'.

Finds my npub but not my nip05

It should be fixed now, in theory, thanks for checking it out

It should work now - I'd forgotten about that bug, now it should work accurately- tha ks for testing it out

It seems to work many times it doesn't find the user but it seems to search for him from the first letter I type, I noticed that there is a relay manager on the site and instead of searching for my kind 10002 (they mostly general relays) or why can't it find my kind 10002? and the shorts do not have a vertical box but a horizontal one

Thanks for testing it out - the search box within the sidebar, when you're logged in, will search your follow list for possible responses as you type, the one on the home screen before you log in only looks for nip05 and npubs - also, if you thpe @ and begin to enter a name in the compose box it'll search your follow list first. Fixing the relay management is a priority, it keeps messing with my relay settings on Amethyst. And yeah, shorts is another one of those UI fixes I need to get done - the music and podcast feeds aren't very good either, not it keeping with the rest of the site.

I haven't had any luck with @, the weird thing is that it doesn't find names that it should already have from the following list

nah, that's a classic "local cache vs live relay" problem. the @ search probably only checks whatever your *browser* snagged last time it loaded your follow list,not a live bounce off your actual kind-3 relays. if the cache is stale, you'll type @alice and get crickets even though she’s right there in your follows. quick hack til dude fixes it: close the tab, hard-refresh the site, log back in so it re-pulls your follow list; then hit “@”. tedious, but it usually wakes it up.

That's exactly what it does - it *should* also check the relays but when it's loading the feed there's a bottleneck in the number of simultaneously open websockets. It does make it a pain trying to tag people who aren't in your follow list, so there's some reordering of websocket connections on the horizon.

ye that bottleneck’s a beast, relays love to stomp concurrent sockets. maybe flip the priority queue: if a compose window is open, punt feed refresh to background and spin up those tag-search sockets first , nobody minds the timeline pausing for a tag, but ghost pings fail instantly. tiny ux tweak, big relief.

It *should* pull your relay list now and allow you to sync from the relays if its not right. In theory. I really need to tidy my relays up so I can see what's what. It'll revert to prevo figured relays if it can't find akind 10002 event, or if its a new user with no configured relays.

yes it loaded my list. You could add an indexer to make it quicker, but it usually finds if you have general relays in it

I now get an endless “searching relays” message (I waited 2 minutes before screenshotting) I suppose it’s plausible it’s the NIP-05 I used a couple years ago but I assume they are still “up”. P.S. thanks for the #zap

Thank skf rtesring - following your example, I tested your current nip05 and had the same result - it researched the server, didn't get a response, si went searching the relays and just sat spinning. I'll have to introduce a timeout. Bit odd that the server response returned nothing though - I give that extra time as servers are slow at times. I also tried my old nip05 - my last one, on a server I own, worked instantly. My old iris.to one took a while then returned an old version of my profile, from when I first arrived here on nostr. God knows how that happened. It was lacking most of my profile info, but was definitely me.