New https://github.com/fiatjaf/nak release has some unexciting new features:
- nak wallet: implements NIP-60 token receiving, sending and swapping, there is also a nutzap command for sending to others but I forgot to test that so let me know where exactly is broken (blame nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft)
- nak curl: this wraps the actual curl command you must have installed and adds a NIP-98 header to it so you can call APIs with Nostr authorization (blame nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49)
- nak mcp: you can use this to allow AIs to search people on Nostr, publish notes, mention people, read notes with built-in outbox model (blame nostr:npub1hr6v96g0phtxwys4x0tm3khawuuykz6s28uzwtj5j0zc7lunu99snw2e29 and nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s), I don't understand the MCP protocol and I don't really know if this works, I could only test it twice because Goose has stopped answering me completely
- nak outbox: in its default form this just lists NIP-65 relays for a given pubkey, but if you enable persistent mode by calling 'nak outbox init' then it will start storing relay hints from multiple contexts for every person every time you use Nostr and use those in a more robust outbox relay algorithm strategy (like https://how-nostr-works.pages.dev/#/pathological) in other contexts, like when doing 'nak fetch' -- inside nak this is not very important, but it serves as a learning tool
- now you can pipe multiline JSON into 'nak event' or 'nak req' (you probably didn't notice but before if you want to pass an event for it to modify, sign or publish you had to pass the entire JSON in a single line -- not anymore)
gj! from grug
container resource power seems shortage¯\_(ツ)_/¯
ちなみにアンドロイドですがやっぱり再現できませんでした🤔
fmm...nip07-awaiter seemingly judges whether nip07 exists by detecting just two methods, `getPublicKey` and `signEvent`. I think it's rational🤟
https://github.com/penpenpng/nip07-awaiter/blob/main/src/index.mts
That means it works even on my browser only which implemented getPublicKey and signEvent😉
fmm...nip07-awaiter seemingly judges whether nip07 exists by detecting just two methods, `getPublicKey` and `signEvent`. I think it's rational🤟
https://github.com/penpenpng/nip07-awaiter/blob/main/src/index.mts
"Fingerprinting Resistance"
Practice example
OS account dialog is some buggy. primary password dialog can't append the "caption".
so i need another dialog full controled
customable and to be able to interect setting value.
but this requires 2 times dialogs per one auth(1. cofirmation to content to sign, 2. entering password). UX is very low...i will consider more for a while.
The evolution of money theory is suggestive. Don't rush into it.
Crypt-native generation manufacturing equipment :)
yeah, absolutely webextension is bad if you use it as a *handy app*, like metamask model. Totally agree with the vision that app includes it. Let's use webextension just as "extension of the web" :)
We can *choose* color, font-size, font-weight as well😉
refactor: to Self-Sovereign Individual🌄
grug not wanting unit tests.
grug wanting integration tests.
These two is completely same grug without contradiction, because he often re-writes widely :)
Okay, I've just removed postMessage.
High security 🤝 High privacy
Note: Firefox only. The point is the Xray vision and using no-prototype-chain-pollution clean Object&Promise.
Please let me know if you find vulnerability,
I believe i'm building a part of that vision, probably!