nostr:npub17usj0jh86ged3pt34r5j6ejzfar9s2q5dl3l84tq8ymhfj2wz08sxmkf8w Why do developers blame users for not understanding obscure technical details that are poorly documented and communicated?
nostr:note17gkx5v9sgnvwaj7sersrxgnhhyeayd7803thk6rxdjrwewzwytkspvjnt0
I am just saying that your relay is not allowing anyone to connect to. You choose to self host. It's your problem when the way you set up doesn't work. Either fix the relay or delete it from the list.
This is not hard
So you’re saying that the instructions provided by nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct are wrong and I’m supposed to have known that when I configured it in 2023.
I have no idea how you set your stuff up to know if it is Umbrel's or someone else's fault.
To me, as a user that is trying to read your posts, the problem is on you.
You complain a lot about devs not taking criticism well, but you are not any different when your stuff fails. You just blame everybody else.
I followed the instructions, as did many other people. Was “outbox” even a feature back then? You built something into your client that other clients don’t have and most users don’t know about and you think everyone is just supposed to absorb this information by osmosis?
Again. I don't care how you made your server. I am just a user trying to see your notes from the servers you said were available.
If you can't keep your on infrastructure up but you are still advertising it to everybody else, that is on you. You can talk to your providers for that serer. But it is still on you.
LOL, OK. I think I’ll just keep my setup the way it is and let client developers figure out how to make software that works together on the same protocol.
If you want to keep bugging your followers unecessarily... sure.. I would just fix my shit. But you do you.
Also, I don't think this was about the protocol. Your server wasn't even reachable.
But that is the exact answer you complain about devs all the time. You are just like everybody you complain about.
Hey Vitor, I’ll do my part to learn more about this but I’d appreciate you taking a deep breath and realize not everyone is thinking about these things the way you are. I actually had no idea this was even an issue until you mentioned it.
I hope you have a great day.
Filter.nostr.wine is not an inbox relay. The rest seems fine.
I would add another DM inbox relay to avoid relying on just one.
If you are using Amethyst, you will need to setup your preferred Indexer relays. Click the Default button if you don't have an opinion about it and just want something that works.
On Amethyst, you put filter on a proxy or broadcasting relay list, since it is not designed for others to use. Filter is just for you and your client. It shouldn't be on any list that others use to talk to you, like outbox and inbox.
Yes, but I haven’t yet seen a way to have your relay lists continue to work with Damus or other single relay list clients. I’m still stuck in the same boat.
Maybe there should be an app that will automatically optimize your relays for you so they’ll work with the maximum number of clients despite all their bizarre incompatibilities.
You might want to talk to the nostr.land folks because I don't know what their different addresses do, but it feels weird to have hist, aggr and nostr.land in public outbox and inbox.
On the outbox: If they are coming from the same pool of nothes, each of your follows is connecting to the 3 relays and getting duplicate data all the time.
On the inbox: If all of them send data to the same pool, then only one is needed to receive posts citing you form your follows.
nostr.land is run by nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj.
