Nostr Web Client

There is one post that has this entire list as a single relay hint, which is wrong.

does this seem like a bug? when I do a normal close on amethyst, and then open again, tons of these rate limits on the resolver. (graphene, tor features off).

this is cool! will keep testing.

```

2025-08-02 11:09:18.459 13624-16100 Relay rela...bunker.com app_process64 W OnFailure null null Unable to resolve host "relay.nsecbunker.com": No address associated with hostname null

2025-08-02 11:09:18.460 13624-19995 Relay relay.pleb.to app_process64 W OnFailure null null Unable to resolve host "relay.pleb.to": No address associated with hostname null

2025-08-02 11:09:18.461 13624-20533 Relay wot.sovbit.host app_process64 D OnOpen (ping: 422ms)

2025-08-02 11:09:18.461 13624-18075 SHA256Pool app_process64 W Pool running low in available digests

2025-08-02 11:09:18.462 13624-16059 Relay aegis.relayted.de app_process64 D OnOpen (ping: 371ms)

2025-08-02 11:09:18.463 847-22642 resolv netd E Query from 10187 denied due to limit: 256

2025-08-02 11:09:18.463 847-22642 resolv netd E GetAddrInfoHandler::run: from UID 10187, max concurrent queries reached

2025-08-02 11:09:18.464 847-22646 resolv netd E Query from 10187 denied due to limit: 256

2025-08-02 11:09:18.464 847-22646 resolv netd E GetAddrInfoHandler::run: from UID 10187, max concurrent queries reached

2025-08-02 11:09:18.464 847-22652 resolv netd E Query from 10187 denied due to limit: 256

2025-08-02 11:09:18.464 847-22652 resolv netd E GetAddrInfoHandler::run: from UID 10187, max concurrent queries reached

```

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 5mo ago

Some of this is normal, because the close is hard it cancels all the queue of things to process. The pool one seems new to me 🤔

cloud fodder 5mo ago

did some decent testing today. my overall feeling is, it's not loading my feed anymore as much as it did when I first opened it. when i double check against one of my home relays, i see posts and replies from my follows that i dont see in amethyst.

though, sometimes it does seem to load more context, eg. when viewing a specific thread.

i guess, yeah its just too much connecting, eg. the resolver and etc just not gonna work (900 relays needs to be boiled down to more like 10-20)..

i assume you already know all this I just wanted to try to help by reading the logs and trying things out and giving feedback.

🙏

Vitor Pamplona 5mo ago

Most posts are not going to the right places. So it is likely that if a client doesn't send his reply to the parent message's outbox/inbox correctly and just send to the logged user's relays, then it doesn't show up in any outbox. We will keep testing.