we'll see. he's an amazing dev, but he dropped the ball on user experience comes before innovation with this one...and just left users to their devices. like, any option but the first still bricks images on anything but amethyst (apk) and snort.

and according to his recent statements, we have to chase around the other clients and ask when they will implement it.

I believe this fractures our community. and i hate it because i love amethyst (still thing it's the most mature and secure client for android) and i happen to be quite fond of nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.

again, i feel he's a brilliant dev and i agree with his security forward approach. imo we just need a little notice and user experience first mentality before releasing the kracken.

i feel his cooperation in making a distinction between the beta and full apk releases was a huge win from our last convo 💜

Reply to this note

Please Login to reply.

Discussion

I vibe with this 💯 still love amethyst it's great

Asking around when clients will implement it doesn't fraction the community. It a very common question we get all the time for every NIP.

I believe labeling beta releases will help. Those of us who use github scanning apps like #obtainium filer out beta releases. When open source first people install the apk and it's not labeled beta, it should work as expected.

After re-reading everything...I honestly feel this was the breaking point when so many kept posting, not knowing they were using a beta release and pics got bricked with no warning.

As far as the wording update, I feel just a disclaimer like (new feature -vmay cause images to not be displayed on other clients)

i still love your work

make sense nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z?

Its a tiny blip in the nostr timeline. There is so much ahead.