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.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49
Please don't do this. Please don't break backwards-compatibility in these crazy ways.
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.
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
There could have been talk about web-SRI inside the NIP94 spec
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
Let's not reinvent the wheel when it could already be offloaded to the browser.
Move fast and break things, or have a lengthy standardization Request-for-Comment process.
I still don't get why Web SRI was not part of notes. Any href references outside of nostr benefits from an integrity check.
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
If only we had Web SRI:
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
I'm surprised that Web SRI is not part of nostr.
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
Just happy to be able to see this post while Damus relay is down. Sufficiently decentralized.
How easy? Does digitalocean or fly.io or railway.app make it a one-click affair?
Seems like you should turn off LNURL or Lightning Address instead of onlyzaps mode?
I think for those folks who opt into #onlyzaps, Nostr clients could combine zaps and likes into one button. Afterall, it's a zap with 0 sat.
If you like something on nostr, you should repost it, so word gets around and the content has a chance to gain visibility. Since Nostr is not Twitter, it works on decentralized relays.
Is not always about making money. It's about assigning value to this worthless likes.
Maybe the community could create a bot service that will automatically like all your posts once you set it up via DM.
Real friends don't let friends not use Zaps.
Is running Torrents over WebRTC part of any Nostr nip standard?
Likes can't be free, otherwise nostr would run rampant with likes count manipulation by automated tools.
Either NIP-13 PoW or some way for users to solve some image recognition puzzle to earn some like tokens, then use them.
Which clients support NIP-13?
Take a look at Nostr retention https://stats.nostr.band/#retention_curves
I've added a couple more graphs to Nostr stats page, and the goal is to try to understand how well Nostr ecosystem retains users.
The graphs show the % of pubkeys that are still writing events after X (up to 30) days after signup (first event). Separate lines are for each monthly cohort of users to see the dynamics.
I don't have much experience analyzing retention, but here is my take on these numbers.
Good news: the curves don't head to 0 - they stabilize after 10-20 days, some some fraction of users does stick.
Bad news: even among high-quality users that got significant engagement from community only 10-15% stick around.
And Match was weird, I guess due to Nostrica.
Do you find this useful?
What else should we measure to go from 'this is nostr retention' to 'here are potential causes of good retention'?
We could do better
I think magnet links should be built on https://webtorrent.io instead of a non-browser-accessible protocol.