It's funny to see how non-Amethyst users react to our "complicated" relay settings. They think users are stupid and can't figure it out.
We are now a few days in and I am very proud of how our actual users reacted to it. Our UI being quite rudimentary for relay selections but that didn't scare anyone. People asked questions, changed things, and generally kept going.
There was a chance Amethyst Outbox would crash and burn. But it didn't. People are not stupid. You give them the tools, they will figure it out.
Empowering users is a hard thing to do. But it is way better than letting an app hide things from them so much that they don't even know where their content is.
As we move forward, those tools will get better and better.
Replies (33)
A lot of us react that way just for the giggles.
Can you send one you like? I thought it was a cute one... Amy-style :)
I made sure to participate in the outrage with no actual complaints to make
And with a dev that responds everyone is way easier
With current resources? Not really. I wish we could move faster, but it is what it is
No, we will fix it.
wen ios version
Frankly, I didn't even participate much. Lots of uses were replying to each other and their answers were great.
When I finish with the Android version. :)
I'm not stupid, yeah!
Real talk: I treat relays like "infrastructure." I honestly don't care which ones I'm on or not on, I just want my notes to be spread to people who might want to see them.
I suspect this is going to be the "default" approach for most new users...
Yep, but if you don't know which relays are doing that, you are just feeding the same algorithms and sales platforms of big tech. Hopefully we can make people aware and empower them to pick and easily move between relays.
I'm using Amethyst. Is it supposed to be broken?
A mistake I made when building an app was assuming users are dumb, they're not
The strange chicken and egg problem there is that- How do users know what they want to do with their computer unless they know what it can do?
Centralized platforms like Google, and Microsoft tell the user what they can do with their products. Linux distros allow the user to do anything they want but if the solution isn't prebuilt, the user has to build it.
This is literally the premise of the rules of the Matrix. You CAN do whatever you want. But if you ask the system what you can do, it will tell you a very limited featureset.
People like nice things, not dumb things.
3 of your replies on this post look like youre talking to yourself and i have no idea y
Yeah, it's one of the bugs I am trying to hunt down.
Coming back, all the original replies are there, so maybe a spinner would just make the ux more obvious if its juat that your reply loaded prior to the note its in reply to
I don't understand the Amethyst relay system. It's working so I don't touch it. The only annoying thing is some wine relay asking for money all the time.
Fico muito empolgado com a melhora, mas lhe pergunto e o suporte a comunidades?
Amy is the AMethYst mascot thing, unfortunately it's AI slop rubbish lol.
I don't know why Victor wouldn't have something amethyst-y ยฏโ \โ _โ (โ ใโ )โ _โ /โ ยฏ
I guess I'd rather get "all of the notes" server-side and then decide what I do or don't want client-side.
Then just use Twitter :) the beauty of Nostr is to not rely on any server doing that. Otherwise, there are alfar better protocols out there if the server is allowed to assemble your feed.
What I'm talking about is using the *client* to decide the algorithm, or perhaps open-source DVMs, not the server. Twitter is everything decided by black-box algo.
I.e. Coracle with advanced filtering methods, etc.
But these models still just say "give me all the notes", and then filter (by my own choice) what comes through at the client level.
you'll also only ever attract a very small percentage of the population though. if we want everyone to use nostr this approach ain't gonna work
The old way is way more complicated. People need to keep tracking where their follows are posting to update their pull lists. On this one, you just inform where your posts are, where you want to receive notifications and after that is done and thats it. There is no need to setup which relays you want to use in the app to download posts from. Much easier.
It's better than what it was before on a non-outbox client, where users need to constantly check the relays their follows are using and update their lists accordily. In this one, it is set and forget. Just make sure your posts are there. The app does the rest.
Makes sense. But if they don't understand which relays are hosting their content, there is absolutely no point on nostr. If they come to nostr just to use default servers of an app, that is not any different from a Twitter or Facebook. You only get any freedom if you control your posts, where they are. Otherwise, we didn't change anything. We can obviously hide these things away, but then we are not doing anything new here.
It's like using Bitcoin with custodial wallets. It's not that different from regular fiat.
Yes but why would these "I don't need to know about relays early on" users even come to nostr in the first place?
You can't bring new users to nostr without a sales pitch, and as far as I can see there is no effective sales pitch that doesn't involve relays and the awareness of them. They're just so fundamental to nostr. Nothing is more fundamental. It's in the name.
Relays are to nostr what wallets are to bitcoin, not what multi-sig scripts are to bitcoin. Leaving the discovery of relays until later would be like bringing people to bitcoin but leaving the discover of wallets until later. ("I'll just keep it for you myself, my friend, until you ask where it is, and then at that point we can talk about what a wallet is").
typically when people refuse to learn, I find it's because they don't want to. that's when it's best not to force it on them by making choices for them, because that just leads to you (the developer in this case) doing it all for them. is that the responsibility you want? nostr i think is about user choice, how hard is that? not very..
