And yet it's still super easy to get onto and it just works which is needed for adoption.

It's already hard to get any easy user adoption from normal people. "you should join nostr it's really cool. It's not too hard you just have to learn what relays and all this stuff is. Oh you have android? People aren't going to be able to see your images. Sorry about that."

As long as clients are doing this nostr is just the next mastadon without email.

Reply to this note

Please Login to reply.

Discussion

Yikes. Mastodon is horrible hot garbage. It has more issues than Nostr. Nostr has one client doing odd things they only one other to my knowledge has adopted. This will all be sorted out soon. Have faith. Pura vida 🤙🏻💜🫂

If I don't speak my mind who will. This doesn't help adoption at all and it's the only client on Android that actually works and has modern features. As far as I'm concerned it's a huge problem, android is on an overwhelming majority of the world's smartphones that's not good.

We have several scenarios in play here, brother:

1. Amethyst is open source. Someone forks it an releases a version without NIP-94 and NIP-95. They have a cool sounding name. It gains popularity as the client on Android that allows images to show on other clients and doesn't bog down relays. It overtakes OG Amethyst because we're super fucking early here.

2. The devs at Plebstr, Current, Nostros, Plasma, etc. step it up a notch. The Android community Zaps the hell out of them to give them incentives and to hire outside devs to make their clients better. Some of these clients now become the top clients. Some fade into the background.

3. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s decides to port over his iOS app to the best and most popular operating system in the world. We rejoice in the centralization of mobile clients.

4. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z hears the outcry of many people, sees them not using his client as much, sees his Zaps and funding trending downward, he realizes that building backwards compatibility and/or user choice into his client is best. Vitor makes changes. Everyone is happy.

5. Every major client realizes that Vitor is correct here and implements NIP-94/95 the way that he did. We have mass consensus and we are all happy.

6. Or so we thought. Relay operators are NOT happy. They do not want images on their relays. Charging for relay access becomes the norm. All of the free relays do not offer image support. Clients notify people as part of the onboarding process that relays only allow a certain amount of images before you have to start paying. Users on Nostr appreciate Value for Value and pay for uploading images.

7. We realize we love Elon Musk, Dogecoin, centralization, closed source, and we go back to Twitter.

Booooooo #7

anything is possible lmao

8. Aliens 👽 🛸

Good call. Never underestimate them.

Or I port Amethyst to iOS and Web and then people can finally have access to a good client. :)

Wouldn’t it be better if helping instead of competing like ladies in a kennel mothering conflict?

😉

Or you could give your app users a choice to not use a nip implementation that is heavily disagreed upon.

This NIP will be the cornerstone to some much of the new features coming up. You can't do a lot with urls.

What features could you possibly be implementing that involve memes and pictures posted on nostr that people want an opt out for?

A whole ecosystem for creators

Don't think Nostr is just a Twitter copy cat. Some people forget that.

Then let people opt in with images, you can clearly allow people to opt out like you did nip95

People shouldn't be locked into using that content ecosystem you want to create, especially if they just want to post a meme.

I support the direction you're going in here, in fact it'll directly help something I'm building, but I still don't see why you can't make that functionality optional.

Add a settings menu and let users choose what functionality they want to enable.

Opting out of nip 94 for images should in no way break future functionality. You can clearly code this because you made nip95 posting optional.

8. Nostr Dev Celebrity Boxing Event. Winner take all.

I'm advocating for a karaoke contest in Miami next month. I don't know if nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z is attending though. 😞

The protocol is great don't get me wrong and some of those scenarios could potentially be good. If someone doesn't start caring about the average social media user's experience nostr will be nothing more Then an echo chamber.

I gotta say, I'm not against the direction Vitor is going in, but I have no idea why there's no settings in Amethyst. User control should be the norm in Nostr.

I didn't agree with the OnlyZaps feature but I still respected how it was rolled out in the TestFlight version first and then only as an opt in.

That's how you introduce experimental new features, give users a choice.

In the end that's literally all we are asking for. He made nip95 optional there is no reason he can't do the same and make nip94 optional

Yup agreed. The lack of user control in Amethyst is a letdown and it will eventually lead to forks especially when you can't even turn off features that aren't backwards compatible with other clients. Or the community will just contribute more to development of Plebstr instead.

I find it ironic the main iOS client is way more customisable than the Android one. It's usually the other way around!

plebstr is not opensource

Srsly it's closed source? Huh I guess I just assumed a Nostr client would be open source so I didn't even check. My bad.

I hear this a lot around here. I run a Fediverse instance. Im curious what the perceived downsides of the Fediverse are around here.

Im still quite new to #nostr

#plebchain