Replies (41)
Freedom is not free. But yes, clients need to do a better job
Yeah, that's the issue. But regardless, purplepages should never be in the outbox lists.
We might add an index list to send just the kind0 and kind 10002 there.
So, It cannot be in the general section too because otherwise it will just send everything to that relay.
Even as a technical person, relays are currently more hassle than I'm willing to put into this for fun. If mine are wrong I don't even know of a decent up to date central resource to fix them.
Scattered half information like this that requires paging back and forth is never going to get a normy to get this right.
Users don't care about relays, outboxes, inboxes, sonofaboxes, whathaveyous! We just want to use this shit apps to shit post! If you make apps for nerds, you will be jerkin off each other. The strippers are long gone!
FUCK NORMIES
I never understood these relay thing. I use public relay, relay from my own (publicly available) lnbits instance, local relay... but I don't know which relay must go where and when do I need more than one or not.
🔥
We should __collect__ and __curate__ these Amethyst best practices 😉
Just seeing this convo makes me realize how hard this system must be for a day to day user. 😐
Cool but won't use until amber login support.
🤷
Right, I have no clue, but I wonder why I have to seek out people I follow, because I never see their notes.
Unfortunately for users, there are a lot of complex policies that different relays adopt which make them unsuitable for inbox/outbox usage.
If a relay requires payment to write, and you use it as your outbox without paying, then your messages will not be accepted by that relay.
If a relay requires payment to read, and you use it as your outbox (paying or not), then most users can't read your posts because they didn't sign up for that same relay.
If a relay requires AUTH to defeat spam, and you use it as your INBOX, then people who care about privacy will not reply to your messages.
I could go on, the list of gotchas is far longer than just this.
Gossip client, admittedly written for technical people not normies, has a "test relay" button to check if a relay is suitable as an outbox or inbox.
I think it is complex even for devs. Like I don't know how to check if a relay is good or not for outbox, I had to look at the notices of each relay to figure out what they do :(
I just logged in to metadata.nostr.com using amber... 🤷
Can we use only the Amethyst default suggestions and leave other relay groups empty?
Defaults are still good, but you need to choose outbox and inbox relays to host your content. Otherwise, we won't find you.
I stopped because the new version sounds like it will be completely different than anything I have now 😅
Might i ask a semi passive task from you,
@elsat and anyone else caring to help educate the ecosystem?
We gotta aggregate all these nuances together somehow. Whether as a list saved/bookmarked events, or even adding a #nostrdocs tag to a thread to find later. Hell, even tag me! 😅
Anything unclear but important to know, terminology, workflow, usability etc.
Might be a nice starting point for a nostr manual
Agree. I’ve been documenting best practices for a few months when I detect them. Example today thanks to Vitor:
https://github.com/nostrability/nostrability/issues/209
Feel free to create best practices issues in nostrability repo, for lack of a better place.
Of course. What would be the most efficient way for existing resources & what would you like to see for new ones?
Nothing that can add labels post-publication seems to be working for me lately but anything other than that I can figure out.
🙌
We're increasing the resolution.
Whether client specific, nostr specific, even zaps - any points of confusion. Minimal work, just some things for me to keep an eye out for and compile a set of resources to sort through.
The idea would be to tile up #TheNostr with a bunch of Q&A/terminology flashcards, in addition to any other more sophisticated, focused guides that could exist.
So a hashtag it is then... is that the one? It looks bare to me right now but my connection sucks at the moment. I feel like I've seen it used for tagging doctors previously though. #ndoc ?
Yeah i see that. Works for me! Nice hashtag mine 😂
This is an age-old catch-22. Give users the power, or basically make primal.
Balance will be the solution, but I don't know what that is in this case.
@Dikaios1517 would you also be interested in assisting with tagging under #ndoc any Nostr educational content as you create it or come across it? Maybe we can help build a Nostr knowledge base about Nostr on Nostr 😁
Can do!
Educational, unclear, nostr oriented questions 🙏 like #nostrbility but less formal, more scattered
I'm facing the same problem.
> We might add an index list to send just the kind0 and kind 10002 there.
Please not another event, we are scattering the basic profile config in too many places.
Maybe adding a "meta" flag to kind: 10002 is enough.
These relays should NEVER be in your Public Outbox (write) OR Public Inbox (read) relay lists. Please remove them.
relay.nsec.app
purplepag.es
sendit.nosflare.com
groups.fiatjaf.com
relay.getalby.com
inbox.nostr.wine
filter.nostr.wine/...
relay.groups.nip29.com
They are just wasting yours and your followers data plan. They are designed to go into other lists, not the regular ones you use in your client.
You can check your relays on
i think clients should set the minimum and required list of relays so user can just use protocol and don't even think about it. when (if) user will need to add or remove relays, let them study how to manage relays (maybe some notice should appear when them trying to add or remove something that should not to be added or removed).
Thanks. But you could put suggestions for outbox and inbox as well.
If we don't make the tools of freedom simple enough for anyone then not enough people will take it to matter.
It doesn't matter how free you can be if everyone around you is still trapped they can ruin your life easily.
Nostr.wine, nostr.land and jellyfish.land and your own relays from Nostr1.com are great options. It's hard to predict what would work best for each user, since each one has a different need and risk profile.
Sure, but you are still using more resources (from client and relay) than using a single event. What I don't grasp is this urgency to fracture the profile data, given its small size.
Everyone interacts with the same handful of people over and over. Just cache that data and background-sync it, periodically, so that the cache doesn't go stale.
The number of events is irrelevant, if you structure your fetches efficiently, and do some smart caching.
Thank you. Your post motivated me to try to better understand Relay Management.
For me, the paid relays are now only in the outbox, and only freely accessible relays are being used for the inbox.
For aggregator Relays I use local lists now
Vitor Pamplona
These relays should NEVER be in your Public Outbox (write) OR Public Inbox (read) relay lists. Please remove them.
relay.nsec.app
purplepag.es
sendit.nosflare.com
groups.fiatjaf.com
relay.getalby.com
inbox.nostr.wine
filter.nostr.wine/...
relay.groups.nip29.com
They are just wasting yours and your followers data plan. They are designed to go into other lists, not the regular ones you use in your client.
You can check your relays on
I thought by having sendit that i'd be tricking your outbox model into sending across the ecosystem :P
