arthurfranca

Whoa AI is rapidly polluting the nostr event kind space 📝 7a44ae06…

Great cartridge arts

yolo, back to coding. fixing nostr step by step. localized trending topics is next. but first, 3 spoons of this:

Try this wss://relay.44billion.net for an anti-spam xp. Add it as write/read relay

2 days left to the end of the internet in Brazil as we know it. Government want us to show an ID or biometric data even to use Linux.

kkkk

@619af6a6…6d3bdf23 o Jumble não tem isso. E agora??

Ok I can see me using the poo silhouette with a fake account using someone else's pic. Me gusta!

It would be interesting to read a contrary opinion, although unlikely. A curious fact: I was just browsing the cashu repo and read a comment suggesting that in the future they may have to represent amounts in nanosats instead of millisats (which is already a unit 1000x smaller than what is officially considered the smallest unit of bitcoin) as if the price of bitcoin was going to rise to the moon. Dishonesty or pipe dream?

"Hardened Events use event kind 30078 because previous interoperability back and forth isn't needed to pick the effective event kind" - quote from a draft NIP. The most grotesque side-effect of replaceable/addressables events shows up when you test a new bugged app and it wipes your follow list as soon as you add a new follow! Imagine if Facebook (in the good times) was on Nostr and you suddenly lose all your hand-picked FB follows due to a bug on another nostr app 😱 In an effort to fix this once and for all, I created a spec called "Hardened Events" that accidentally reverses the current school of thought from NIP repo maintainers of making atleast two clients interop before they (maybe - add politics to the soup) merge your NIP with these new event kinds you picked so that other people won't try using the same event kinds for other things. Now it's like: you pick a string as event kind prefixed with your app name or anything else. If someone wants to interop, they look at what events your client is producing and adopt'em. I kinda appreciate the outcome, it feels more organic. Though it's an (unintended) attack on Nostr. All new (effective) event kinds would use `kind 30078` as anchor. And to the despair of some, all newly created event kinds would be editable. Absolutely outrageous or ingenious? Not sure yet.

Similar as in "got into OpenSats limbo then auto-rejected"? xd My project was a big one meant for making nostr "normie"-friendly: 1) new (and secure) way to sign in/up that your grandma would understand 2) multi-window and multi-user app launcher platform that makes any nostr webapp installable with pinned version, auto-login and more 3) three starter apps: app store, messenger (unreleased spec superior to nip-17 while 99x easier to reason about than marmot), twitter-like client hiding nostr complexity 4) relay with some smart data aggregation which today is the 44 relay 5) new kind of relay for backup/sync/availability (data sovereignty) Most of it is online at an alpha/beta state, not just an idea, though the development halted for now.

Thanks for the almost-zap hahah but, above all, thank you for the recognition. Didn't know you were from the committee, I wonder why you left. The current nostr board most likely simply let my application rotten till auto-rejection. I can only speculate, though it was really sus to be rejected with an auto-generated email right after I sent them one (kindly) asking them for feedback as it was taking so long.