Seeing so many blank posts now from amethyst users. I wonder if they know that no one can see their photos anymore (except other amethyst users). This is a huge L for nostr. View quoted note β
Login to reply
Replies (94)
Yep just noticed this after updating to the latest version from github.
Wait, what happened?
Hmm thats confusing...
The scroll on amethyst had so much lag to it. Idk what's going on there. Had to switch back to iris
I agree. I hate this new feature
Will be talking about this on Frog Talk πΈ today
Sucks. I think it's not just non-amethyst users. I often don't see posts too. But also we have our own meta now (until there's a fix.)
#[1]
NIP-94
What happened? Does it do the same thing if I drop a Nostr.build link?
What is Amethyst doing to make it so we canβt see their photos?
I am working on an alternative that encodes all of that information into a small string that can be included in post metadata itself, and would be backwards compatible.
NIP-94
Why?
Who is this nip 94 and what master does he serve?
they don't, like wrong way driversπ€·ββοΈ
I won't be updating my app until this is resolved.
NIPs all over π
My man π€
Thatβs a whole other language to me. π Going to learn about this.
I noticed it on the newest APK for Android, so I reverted to a previous version from 3 weeks ago.
Can you see this note?
#[1]
Serves Elon to get everyone back on Twitter
I swapped back to using my own image hosting becasue of this. Really annoying.
Those are just the APK users. π
Been posting on Amethyst all day, and I can see my images fine on Iris and Snort. Appears to be a Damus only issue. At least for me and I am on Amethyst Beta.
This is the alternative to apples TestFlight right
Thanks!! So much to learn here. π
Ahh Thats a fucking cool update. Best of luck with the resolution hope it is quick and i will be patient.
Nah itβs the APK users using the newly implemented NIP-94, youβre not using that brother
Even rougher, but yes.
π«Άπ» 
Thanks!π
TambΓ©m estou em Amethyst beta. E nΓ£o vejo problemas.
Hahaah yeah Iβm on Damus & I can see all your pics π«
π« no prob my fren ππ«
I actually love when one of you implements a cool NIP and everyone else has to follow or figure out an alternative, feels like the right kind of innovation π«‘
So, a whole new standard instead of a NIP-agreed design?
View quoted note β
What a piece of hell is this?
NIP-94 was never intended to be used for inline images in social clients, right? It was meant for those other apps that would create markes for files and other crazy filesharing applications.
@Vitor Pamplona @Kieran
Please don't do this. Please don't break backwards-compatibility in these crazy ways.
NIP-94 was never intended to be used for inline images in social clients, right? It was meant for those other apps that would create markes for files and other crazy filesharing applications.
@Vitor Pamplona @Kieran
Please don't do this. Please don't break backwards-compatibility in these crazy ways.
Wrong, that's horrible and stupid and is breaking the protocol.
Can we atleast make it backward compatible. It's broken right now.
DAMN, so.. Iβm guessing the right thing is to support the agreed upon NIP design ? Not introduce an alternative.. idk enough about this Iβm willing to change my mind
today? when? ππ
Yeah it makes me sad π
But seems like a backwards compatible solution could fix the current broken thing, but is it sorta like a bandage ?
this could be a nood for all we know π
your stuff is too nerdy, sorry ... missing the coolness ... no offense π«
It's not broken. That's the way we add any other content to posts in Nostr. I am just adding a NIP94 event.
π«£
Ahhh okayyy π«‘
Exactly. I didnβt not expect it to be used this way either. If we want image metadata we can include it in a small TLV encoded string in the tags that references the URL (by index)
This is superior in many ways I understand but experience is broken.
Only because some clients have yet to implement NIP-94. That's ok. We saw the same things with zaps, long form contents, polls, which other apps also don't see.
In all other cases damus can ignore them, but breaking images is an insanely bad experience for all other nostr users. Why do this?
Iβm not up to date on this but it seems to cause many issues. The NIP was poorly worded seemingly, though havenβt checked itβ¦
Is it possible to maintain backward compatibility without breaking the user experience while also implementing new cutting-edge features
I mean take a example of this post. On Amethyst it seems like Will posted this picture.
I can't upload photos on amethyst. haven't tried elsewhere
I can see this post on damus and havenβt seen any blank ones but if you posted a picture it just has a circle moving around.
Because we are pushing forward. NIP-94 is a better way to link to a static file and we would love to see all clients implementing it at least to view URLs.
And it's ok to cause issues for APK users. They are the ones pushing Amethyst forward anyway.
PS: You don't need to write NIP-94 events if you don't want to. But reading them will be a must sooner or later.
If I Quote a Poll or a Long Form Content, Damus users will not see it as well.
Weird, I posted that pic. #[2], can you not see it?
I didn't want those Apple snobs to see my exquisite photos anyway
zing π€π»π
Try nostr.build
the note just says NON FEED RELATED EVENT on gossip π₯Ί
#[3]
Hey Bill, how are those towers holding up linking?
Si vous n'utilisez amethyst vous ne verrez pas mes upload d'image π₯²
#[0]
Oof.
Did you see my tea mug from this morning?
Those are not fundamental things. I can hide that easily. Images are pretty core to nostr at this point and urls are the gold standard. If you want the extra goodies provided in that nip you can achieve the same things in a backwards compatible way.
Yeah, I just pinned Iris to my phones homepage and use that instead of Amethyst.
π―π―π―
For real wtf π
Just tried Plasma and Plebstr, neither can see the images I posted using Amethyst.
He'll say it's working just as expected.
I thought it was a glitch but itβs just a misunderstanding of the NIP-94... Either a bad substitution...
Iβm happy as long as NIP-01 works π
Had no idea that was the reason!
Ok yes!! So this is what's going on.. so I fix tgis by using a different client. If Victor makes amethyst like this I will use a different client.. problem solved
#[0]
I agree. For the sake of simplicity interoperability it doesn't make sense to have multiple competing ways of embedding media in a basic social feed. That's just going to make it harder for client developers.
Yeah, you must be on the apk. I'm still on 0.32
I just won't update until they fight it out π€·ββοΈ
Boom!π₯
Je confirme, je ne les vois pas
Sometimes amethyst is weird with uploading images and VPNs.
The definition of a hypertext reference or resource could be revisited.
Afterall, it's strange that Subresource Integrity is not part of nostr notes, considering that in the world of NFTs, JSON referring to external images are hashed.
Subresource Integrity - Security | MDN
Subresource Integrity (SRI) is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered...
okay, then you have either not upgraded to the most recent apk version or you are using the play store version. there was an issue introduced by the most recent amethyst apk update introducing nip-94 that broke picture visibility
#[4]
I think it was file size. imugr prolly has size limits
thx for the reply
#grownostr
#jimstr
I did try nostr.build and haven't looked back. thx.
#smij #zapd #grownostr