I did it.....i fucking did it. I know non of you are going to care, not even the tiniest bit but:
I managed to turn an arbitrary moment of a starcraft replay, and turn it into a save-file so you can continue playing the game from that exact moment. And it works in remastered!
Im not sure if Blizzard is going to be mad, but you guys don't understand....this feature....Half of South Korea will be using Nostr soon, don't worry
Constant
npub1t6jx...ksrw
Writing a book about Nostr
Ceterum censeo NIP-3b omnibus esse utendum
As for what ive build that already works (replays, maps etc all shared via Nostr). Check it out here π:
https://npub1epzfpke2r4t45cyjc0vgrsxl7sv66km7jgsw7wa9k0gxxry763ys3qaldv.nsite.lol/
View quoted note β
That moment you build something that actually works and did not even know was possible.....leads you into this grand crazy idea that will eat all of your time and will be too complicated to actually finish.
Yet, here we are... Totally Nostrified Brood War, soon (maybe)
@Alex Gleason 's ''insight'' that a Nostr-ID == Bitcoin address, came with the wrong conclusion. The point is not you can send BTC to a Nostr profile, the point is that Nostr already indexes naturally anything that is relevant to Bitcoin.
Yes, this means you can go and create a kind:0 (profile) for a BTC-address, or send BTC to a Nostr profile, sure. But there is a lot of potential (meta) data involved with your Bitcoin Wallet. Address book/contacts, transaction labels, wallet descriptors and scripts. Those things are already tied to a (master)keypair, and as such a very easy query away from fetching if they were stored via Nostr.
The only response i got to this idea was this:
View quoted note β
In a way it is a weird and confusing position to me. What system are you supposed to use for "must-be-available data"? What do we use now? What are they planning to use? What makes a server or system adequate for "must-be-available data", the fact it has a sticker that reads "reliable" on its housing? Does one solution exclude another?
Data availability and reliability on Nostr are straight forward, because it does not fool you with false promises: You figure it out.
Redundancy is resilience, decentralization is censorship resistance, paying for a service will probably net you more reliability than something you use for free.
More relays, better relays, migration to different relays over time....thats it, thats all there is to the ''data availability'' story anyway.
Nostr.
Is This The Most Powerful Post on Nostr?!


Came up with this 5 min ago, therefor i am certain i am right.
An NFC card with an ncryptsec is probably the most straightforward minimal viable back-up one can have (especially if you can create it from and load it into your signer automatically).
Cope in the comments
I am about to kill a darling, in this case the use of Musig2 inside TEPP for the association event between parents and children.
In trying to plug all sorts of holes i took a step back and realized that perhaps a different perspective is in order.
TEPP introduces a "regime" onto a keypair, where others provide the permissions and restrictions that define that regime. Ok, but it is not water-tight and never will be. But perhaps that is not the end if the world, as long as things remain actionable and transparent the moment things do go wrong.
The insight i had was that, at any moment, your kid can just walk to the front door of your house, open it, and walk away. People/children generally don't flee their home, people generally try to escape from prisons.
TEPP is not a prison, it is a home. Its the walls and structure your parents provide to facilitate you according to your parents insight. The restrictions are, hopefully, in your best interest, to guide you on your way to get on your own two feet. In this case to at some point walk the digital plane permissionlessly
Yakihonne is based.
View quoted note β
nostr 

When i came up with the rough sketches in my mind for what ultimately became TEPP two years ago, i hoped we were able to front-run some of the madness i saw looming at the horizon when it comes to "child online safety" and the legislation proposals that would come with it.
Did not expect things to go this fast, and it is clear a policy agenda has taken shape internationally, seeks rapid implementation and by the looks of it seems to get it.
Ok...so we can't front-run what is already at our doorstep, at least we are starting to formulate a response. I would like to thank @Jeroen β
and @Sebastix for sharing the vision and manifesting it with @Kubo.watch . While i am at it also a shout-out to , let a 1000 Nostr flowers bloom.
The core protocol/TEPP needs some work still, but there is way more work to be done on the client side in order to deliver the right experience anyway. Feedback from users is desperately needed in order to move both quickly and in the right direction. If you are a parent, or know any, please consider engaging actively so we can add a calm, sensible, practical voice to the discussion by delivering actual answers.

Tubestr β Creative Freedom for Kids
A safe, parent-guided video platform where kids can film, edit, and share videos. Built on Nostr for true privacy and ownership.

Home Page
Trusted circle = Your KIDDOβs safe screen
Whether youβre a parent yourself or not, sure you already know the dopamine trap: endless scrolling β just one more like, one more video, one m...
Has anyone ever looked at serious Nostr integration for a Bitcoin wallet, when it comes to storing descriptors, scripts, etc.
I happen to catch a large chunk of this talk while backstage because we had a panel right after and it was good. Whenever the recording gets published you should watch it
View quoted note β
Can confirm @BITKARROT is indeed a dude.
It is known
Bit rushed on time, i forgot to make a couple of points that i will make now, geared to the developers, especially those that want to put "Nostr" into the background:
First: if you give users in your app an "account" because that is easier; they will end up making another "account" in the next app they download, and at that point, we hardly differientiated from where we came from, its probably worse.
Second:
If your argument is 'if users are ready they can blablabla'; how are they supposed to get 'there', get 'ready' when you went out of your way to hide everything from them in the first place.
How about you find a way to help them understand rather than hide it for the sake of "UX", which leads me to:
Third:
The best "UX" is probably the app that just 1 thing and that 1 thing only; and that set up only really makes sense if users are competent in using their profile in various apps.
Well, thats mostly it, im off drinking beer now
View quoted note β