Ideas I'm having while hiking now (and listening to the Nost...

npub1zthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnq6wxm56
hex
9cb1c966f660adfb668acb87a05d2faf3d7765e668a0f47fce5d8f7b2180846bnevent
nevent1qqsfevwfvmmxpt0mv69vhpaqt5h670thvhnx3g850l89mrmmyxqgg6cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsp9msr6ytgfgf9mkrmapuu9qvsg9d78ua3ajntfmt580t5llvgpeseqhwz3Kind-1 (TextNote)
Ideas I'm having while hiking now (and listening to the Nostr Compass podcast)
-
How similar are Bitchat and FIPs? ( nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm ) They both solve similar-ish problems in the (Bluetooth) mesh. Last I recall, nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk had added source routing in the Bluetooth mesh
-
Instead of building support for Cashu Spilman payment channels directly into apps such as Nostr relays and Blossom servers and Nostr client, I should just start with making Docker images which act as proxies to those systems. One container on the client side which adds the payment before forwarding it, and another container on the server side which accepts the payment before forwarding it to the "real" server
-
I should use HD (hierarchical, deterministic, [BIP32?]) key generation in the encrypted file storage thing that I mentioned an hour or two ago, so that I can give you the keys to access and decrypt a subfolder of my data. You can derive the private keys for any file or folder nested within that, but you can't go back up to the root
Raw JSON
{
"kind": 1,
"id": "9cb1c966f660adfb668acb87a05d2faf3d7765e668a0f47fce5d8f7b2180846b",
"pubkey": "12ee03d11684a125dd87be879c28190415be3f3b1eca6b4ed743bd74ffd880e6",
"created_at": 1773501951,
"tags": [
[
"alt",
"A short note: Ideas I'm having while hiking now (and listening t..."
],
[
"p",
"bbb5dda0e15567979f0543407bdc2033d6f0bbb30f72512a981cfdb2f09e2747",
"wss://nos.lol/"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63",
"wss://eden.nostr.land/"
],
[
"p",
"bbb5dda0e15567979f0543407bdc2033d6f0bbb30f72512a981cfdb2f09e2747",
"wss://nos.lol/"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63",
"wss://eden.nostr.land/"
]
],
"content": "Ideas I'm having while hiking now (and listening to the Nostr Compass podcast)\n\n- How similar are Bitchat and FIPs? ( nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhscs6htm ) They both solve similar-ish problems in the (Bluetooth) mesh. Last I recall, nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk had added source routing in the Bluetooth mesh\n\n- Instead of building support for Cashu Spilman payment channels directly into apps such as Nostr relays and Blossom servers and Nostr client, I should just start with making Docker images which act as proxies to those systems. One container on the client side which adds the payment before forwarding it, and another container on the server side which accepts the payment before forwarding it to the \"real\" server\n\n- I should use HD (hierarchical, deterministic, [BIP32?]) key generation in the encrypted file storage thing that I mentioned an hour or two ago, so that I can give you the keys to access and decrypt a *sub*folder of my data. You can derive the private keys for any file or folder nested within that, but you can't go back up to the root",
"sig": "fbd3bbb750d5b6790c56df7f331dd002ab4279880083521163c7b8e58be67035870695529000a2cf5de19593fdc7b478f0af547377f97911f23f011b7baf3a3c"
}