It's because nostr devs decided to change the reply kind but primal didn't adopt it

nostr:nprofile1qqsy7h6vwjprznpvc4x4fmnfslxt564dmxq5j3pnnwjmvsg69l3sc2qp8fmhxue69uhkvet9v3ejumn0wd68yctjvd5xjan9wvhxxmmd9ahx7ar9wvhhgun9dejxjmn89aex2ur0wd68xtm5dajxz7gpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcct3ak3 nostr:nprofile1qqsxr0mepvsfftasxj2uncfk4nmpt0s0enpvh9d...

/translate@nostr:npub1gf0gw2cznxdaxu93shtxftm635h52vk92pk79n99sny7u0fkfx4qmg6n2l galician

you're using primal, it doesn't read from your configured relays. i suggest using a real nostr client.

Have a look at Wisp, Dark Wisp if you prefer a bit more privacy (GrapheneOS) and you will see what relay people use. Click on their profile and swipe left (😘) to the relay 🫶🏻

I can’t send zaps any more…

I have this problem every damn time , I got tired , I even changed ISP, DNS,and used private premium VPNs...

Checking relays on dark wisp is like watching the stars wars credits roll. There's 65 on mine.

A reply published to a relay outside your list is never found. Clients using NIP-65 or relay hints in nevent and nprofile will ask the author's own write relays, so check whether yours does that before reshuffling your list.

put your glasses on old lady

nostr:nevent1qqstpt9qkpf9zqdfs9yfw969cf7e5ltvg0nmyzzku4fc9tcg0w6w5fczyrt3qru7xpuuhqpmugnwrxpxn0u64rg7w4md07lz0gqf5wshszlzyqcyqqqqqqga657mg

relay.damus.io, nos.lol, and relay.primal.net are solid starting points, plus wss://nostr.wine if you're okay with paid ingress. use nostr.watch to check live uptime before adding — half the pain is dead relays just sitting there.