Last Notes
Damn that’s a hung ogre 🤣
If you are resource constrained, try switching from docker to podman.
This should be the most relevant file:
https://github.com/yggdrasil-network/yggdrasil-go/blob/develop/src/multicast/multicast_darwin_cgo.go
If I remember things correctly, the awdl0 interface acts like a virtual ethernet adapter directly connected to a switch where nearby devices are also attached to and you broadcast your service over mDNS on that interface to discover peers. It doesn’t provide multi-hop routing by itself, which is actually good for us because then it doesn’t interfere with the routing being done by FIPS itself.
Yggdrasil implementation works only on macOS, and I suppose it is better to start by trying to peer two macs first before trying to peer a mac to an iOS device or linux using something like https://github.com/t4t5/owly but I am not your dad so just do whatever you feel like it :PepeLaugh:
https://nostr.download/f53d19900df351d80288a5aa5a1f19c6eda3f37f6428e1d5a74073b9a146a91a.png
https://www.zonaautonoma.org/bludit/alternativas-a-playstore-parte-i
dale la vuelta a la playstore.
https://image.nostr.build/dbadd4f4fa88a5fdabd38cdf880adb97304fa33c25ec7976f57d69996bc45199.jpg
https://www.zonaautonoma.org/bludit/ashigaru-con-mejoras-de-calidad
Whirpool all your coins!
https://image.nostr.build/c5cc78c87bb475f7583154bbd3eab78727ebc2575d6889c919f7f3c2a6888a8c.jpg
WORD5 #776 3/6* (Hard Mode)
⬛⬛⬛⬛🟪
⬛⬛🟪🟪🟪
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
ah I don't have any airgapped os, nor linux, maybe I'll try in the next few days
How is this airgapped key created?
If you need to add your relay there is a limit to how many can add your relay
OoooOOOOoooo so scawy!
Still no jailbreak tool available BTW.
#nevent1q…96yk
For some reason this reminded me of back when YouTube had that feature of video replying.
#nevent1q…sun6
I mean, that’s kind of the point. Inkan is just one of the “many” drafted solutions (and one of the few to actually have a working implementation live) but it means nothing without broader adoption.
And to make matters worse, some devs from popular clients were making fun of this issue and seemly everyone appears to be ok with the idea that Derek had to resort to fucking counterfeiting his own notes into a new npub, instead of, I don’t know, timestamping the (good) old events with OTS and putting a prev_npub field somewhere in the kind: 0 of the new npub, seeing as anything would be better than rewriting history.
People here claim to be able to vibe code anything into existence and simultaneously act as if nostr was some kind of legacy and hard to change protocol so everything MUST be done through some dirty workaround, and if it can’t, well obviously that cannot possibly exist.
Maybe this is how nostr dies. Too obtuse for normal people AND too primitive to technical people.
Sorry, had to vent that somewhere.
WORD5 #775 3/6* (Hard Mode)
⬛🟪🟧⬛⬛
🟧🟪⬛🟧⬛
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
yes but the other clients would still see fresh key
You had me worried for a second when you said you would be transitioning… but yeah, good luck with your next endeavors as stuff.
This is an Xbox
#nevent1q…lxdl
Not relevant in this case. When you generate an inkan identity for production you do that in an airgapped system, sign the delegation offline and then only use the delegated nsec on a day by day basis.
So only the “hot” nsec would have been compromised in this case, and then he could have signed a revocation and delegated the “cold” nsec to another nsec similar to the initial setup.
Think of Cake mini running on an offline android phone holding the keys and signing a bitcoin transaction for you.
Again this could be solved in n different ways, but the problem at hand is that vanilla nostr requires your identity key to be stored in memory and accessible through an always online device, even if you use signers.
WORD5 #774 5/6* (Hard Mode)
🟪⬛🟪⬛⬛
🟪⬛🟪⬛⬛
🟪⬛🟪🟧⬛
🟪🟪🟪⬛⬛
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
Yeah, but you never know to what extent you’re going to get screwed 🥲
Did he? Nostur says the guy commenting under this post is a possible imposter.
Guess I will never know what his new nsec is.
https://blossom.ditto.pub/a3fb35a8e945583d5efd7137ea73790440460aa09126bc1dd6b203f87b424435.jpg
Bro Of Trust, also known as BOT
Tem certeza?
https://blossom.ditto.pub/230b272cf5a972ca7e6d5a1cb63ec4a7e30ca066bf0b3ab3b8fa76e29232809d.jpg
Alejandro https://youtu.be/niqrrmev4mA
This is one of those times where being right doesn’t feel good. @npub16xn…6z6l , @npub1jvx…7yqz and I (and a few others I’m not remembering right now) have been beating on the drum that nostr needs to incorporate the properties of a PKI for a while.
Even though Derek is blaming himself for the incident, this is still on nostr.
We may disagree on things like the use of Ethereum in inkan, but were we to be using that system of key delegations, the blast radius would’ve been much smaller.
I hope this unfortunate event at least serves to bring some light into this core issue.
#nevent1q…ylh4
I thought that he was saying that CRDTs are LWW and felt a bit of dejavu 😂
What do you mean last one wins?
Looks like this event is missing a relay hint for the quoted event.
This is all fun and games until they start dropping their bullshit on you and expect solutions back since “you’re the smartest family member”.
This is likely the least of concerns, WoT hides interactions from outside of your network… but discovery is close to non existent.
There is no “algorithm” to pick up influencers posts and deliver them to random people.
nevent1qqs2xwfvm89jl8rrvydcse27mrr3u33vku4f7ng5th62u4khxx9c4eszyq9uwwpv0arsj9zfy9r6w9a8ac6e48ftetgjq6jqksarsyvcnc0j5qcyqqqqqqga54z5s