Someone should fork Wavman and make it compatible with Zapstr, and add zap splits. Also with Stemstr. Then music over Nostr would become interoperable, as it should be.
nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hschfr5x I've published a kind:1 note 0f68226041d699a84af8ca0afbd16f0e3913251c1d0032841e9de875c156be16 with several 'zap' tags and now Snort crashes on it with:
Error: Could not determine service url\n at new LNURL (https://snort.social/main.55c8d09c6305345728a5.js:1:388649)\n at getTargetName (https://snort.social/main.55c8d09c6305345728a5.js:1:943759)\n at NoteFooter
...
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy8hwumn8ghj7mn0wd68ytnddaksz9rhwden5te0wfjkccte9ehx7um5wghxyec4uepvf looks like Amethyst (like Snort) supports the older version of the zap spec where 'zap' tag contains lnurl, the current nip57 version has pubkeys there. Is this on your radar?
We blocked a lot of spam from our db at some point, that's why we have less pubkeys and notes counted. Same for total zaps - we ignore self-zaps and some big obviously-fake zaps. We also treat 'users' more strictly (a pubkey with a profile, published post, and at least 1 followed person). These should account for most of the differences.
I didn't engage until it became obvious he needs some push back. Personal dislikes or opinions are fine, unless represented as a fight for the good of nostr, while promoting his own half baked copycat.
nostr:nevent1qqsgkc3tduhyraf9pg2ftjrv4mraatq8ue73f2a5mpa8lf8henth0mqppemhxue69uhkummn9ekx7mp0qgs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qrqsqqqqqpp48s9m
I didn't engage until it became obvious he needs some push back. Personal dislikes or opinions are fine, unless represented as a fight for the good of nostr, while promoting his own half baked copycat.
nostr:nevent1qqsgkc3tduhyraf9pg2ftjrv4mraatq8ue73f2a5mpa8lf8henth0mqppemhxue69uhkummn9ekx7mp0qgs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qrqsqqqqqpp48s9m
Great job!
nostr:nevent1qqstp6wxhq2qqmftwxmpzvsnnvtqpc2rqgm6hwy6gvc933jd5ssfsrcpr4mhxue69uhkummnw3ez6vp39e3x7mr59ehkyum9wfmx2u30qgsvwp3ue4lf4hqdm49h034l40luswvmg83ymcaxdzn2kchduty240grqsqqqqqp6qykxk
A very helpful and thought provoking resource!
nostr:nevent1qqsqswkt7ssrdxagj43t52m4r9v7462rmxs4l8yfvcts3qwzxl4hazqppemhxue69uhkummn9ekx7mp0qgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygrqsqqqqqp0yfah5
@k00b trying to link my Nostr acc to my account in SN settings, after I confirm the auth event in Alby SN shows "Auth failed. Try again or choose a different method." - what might be wrong?
I was initially confused by the idea of microapps, because all examples I heard were about social media use case - "edit profile", "edit contact list", "edit relays" etc.
But think about this: we can have nostr events for _any_ data type. Which means _any_ app could be a Nostr app.
Why would you want to make all apps work over Nostr? Because Nostr is the infrastructure for an app ecosystem, much better than the dominant ones like Android/iOS.
- You have an open "cloud database" with a standard API
- You have authenticity and tamper-proof of all events (documents, files, records)
- You have well defined data types (event kinds)
- You have a decentralized monetization (LN)
- You have web of trust as a potential solution to app safety issues
- You have shared open network effect for the benefit of any new app
None of the existing app platforms offers anything like this.
Nostr as Twitter alternative is fun. Nostr as iOS alternative is crazy fun!
Tell a random app dev that Nostr is a Twitter replacement, and they'll probably yawn. Tell them it's a new app platform, and they'll start paying attention.
We win the devs - Nostr wins. Right?
Yeah right you spent ten minutes thinking it through and coming out exposing our nostr domination plans. Right after you copied one of our "unmonetizable" products. Good luck.
I already heard about that grudge from Derek. Now that you have spoken it - feeling better? Maybe you should have started with it?
We want nostr to succeed as much as you do. Don't like our approach? Well I don't like yours. As I said, good luck.
If the tab has been opened after the launch of the browser then it stays in memory until explicitly closed (or browser is terminated). We plan to enhance this by keeping only N recently used tabs in memory and releasing the rest, to avoid consuming too much system resources.
Oddbean new post about login | logout
Notes by brugeman | export