For context, this is a smart card based HWW I am developing.
I’m currently checking out CryptoGuide’s fork of nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl that supports smartcard readers.
Use ZigBee devices from now on and don’t suffer
Big things are coming 👀
nostr:note1pakffhusqgxyhmmkttjruvm9n5vhfx3pzdp8fa7mrf77w3xmvp4suaxe5a
Try vibe coding a smart card and see how many vulnerabilities you can rack up 🤣
Will also make a new LLM, called LL.
It’s not even a different brand that they are ripping off
I am going to make a phone and call it Phon™️
🤣 maybe if they had more useful contributions to things like Nostr, such as reviewing NIPs and building a significant amount of the base protocol… :)
for me, secure elements
Also, the NOTICE: Failed to receive messages have nothing to do with it, they are for writes, not reads.
I'll be pushing an update to the indexer soon to improve a whole bunch of things.
I have not on Damus.
I'll check what's going on... There's an infrastructure migration underway so it may be related to that.
The actual experience is more like repeating the same computations twice, being extremely careful about the order of operations, double checking *everything*, and so on...
I cannot wait to vibe code my HWW.
I feel like code as documentation needs to be a more popular concept.
If it is readable code then it is much more understandable + easier to use correctly than manual documentation.
Had many cases where the documentation was wrong, but the code was correct.
The value of your labor usually goes down with time
I made my own SoC to run Amethyst with a refresh rate of 3 FPS
trust absolutely no one
Adam is suggesting that the OP_RETURN messages were created by additional 3rd party transactions and were not part of the original transaction:
Yeah it’s bullshit.
The article is AI generated.
All of these OP_RETURNs are included transactions sent TO the wallet, not FROM, so it could be anyone.
We could, but then it restricts the file path / extension. Could the path be defined by /.well-known/nostr.json?
GET /.well-known/nostr.json
```
{
"names": {
"bob": “...“
},
"relays": {
"...": [ "wss://relay.example.com"]
},
icon: “https://path/to/icon%E2%80%9D
}
```
Actually, what if the icons were per-name? And the favicons could be cached by URL instead.
This means:
- Any icon changes show up quickly (after NIP-05 validation, aka restart of app)
- Custom icons can be awarded to different users (like team members, contributors, etc. for Damus)
- Icons can still be cached
otherwise, LGTM.
{"icons":{"semisol":"https://…"}}
you can set up simplynostr@nostr.fan :)
I have talked to Tropic Square and I had a really poor impression. They are pretty inexperienced in the SE world from my talks with them, and custom firmware was barely a priority for them (which I asked about)
My current work about open SE platforms is with one of the big 3 SE companies, which has been pretty supportive. (I’ll let you guess which, there’s only one company that would barely consider it.)
writing from Nostur over here because Damus iOS is eating my data…
I could probably make a solution for this eventually but I have more important stuff rn
“why is this ugly” 🤣🤣🤣
gm Nostr