Don't want to visit the blue bird?
Here you go:
Yes, tracking will still happen if no proxy is used, but the picture will be change-protected in nostr clients supporting NIP-94.
I think it's a step in the right direction.
And less controversial that NIP-95 right now.
We have an update on our mining initiative. This one is about ASICs
https://www.mining.build/update-on-our-bitcoin-mining-asic-program/
Oh, yes!!
Decentralise #bitcoin mining and put it back in people's hands, please!
Thanks for your work!
š«
What about using NIP-94 to check that the profile picture is not changing while still using a HTTP URL to get the file?
Kind-0 attribute could be added to publish the profile picture this way, innit?
I still don't understand why Nostr Nests doesn't use nostr identities... š¤
If I may ask:
Why taking it as a supplement?
Why not in another way?
The best thing Satoshi did was inventing #bitcoin.
The second best was disappearing.
It seems Snort also implemented NIP-94 before Amethyst, so that would make Amethyst the third nostr client implementing.
#[4]
A common standard is already here:
Pasting an image URL.
#[3] has 'just' added a new way of embedding an image via a nostr: link.
But the old way is still working, isn't it Vitor?
Sometimes implementation is important, yes.
But communication is always more important.
š«
Theoretically, yes.
But it doesn't always work like that.
Sometimes a single implementation pushes a NIP acceptance (i.e. Zaps or Repost in Damus), sometimes implementation waits till a NIP merge, even months later!! (I.e. NIP-42 Auth).
I understand recommending the Android client that suits more the way you think nostr micro-social should work, of course.
But building a Damus Android client because you don't agree with Amethyst direction looks like wanting to control yourself where micro-social nostr is going, imho.
Just my opinion, ofc.
As an outsider to Nostr development, this is something Iām puzzled by. According to the GitHub page, ā[NIPs] should be implemented in at least two clients and one relay ā when applicableā before theyāre accepted. Yet it seems as though Vitor is the first to implement NIP-94?
https://github.com/nostr-protocol/nips#criteria-for-acceptance-of-nips
Actually, https://filestr.vercel.app/ implemented NIP-94 before Amethyst.
cc #[6]
Are you planning on using NIP-94 to organise/find music files?
Pushing the status quo is important, but not everything that does it is positive.