Software Engineer • Bitcoin & Nostr • Economics • Security "Do not give in to evil, but proceed ever more boldly against it." —Motto of Ludwig von Mises Lightning self-custody with https://github.com/braydonf/satdress
Braydon Fuller @Braydon Fuller - 24d
nostr:nprofile1qqsyx708d0a8d2qt3ku75avjz8vshvlx0v3q97ygpnz0tllzqegxrtgpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7l329qg has a new book announced! https://image.nostr.build/3de3cf4294e8a7e4f0bae18e945ca02ef605cb5e2caf6f164b0c2bbb7ce36269.jpg https://saifedean.com/tgs
Braydon Fuller @Braydon Fuller - 26d
This is pretty cool. Running an LLM to filter events for your local relay or client is getting far more practical. nostr:nevent1qqsdzmw643h8cwle9f7namfsynhkjrjn5zht0kpgg6gx85dd4m2s8qcprpmhxue69uhhyetvv9ujucnjv9ukgmmw9e3k7mf0qgs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccrqsqqqqqpqgz59k
Braydon Fuller @Braydon Fuller - 28d
My Meshtastic journey begins! Any tips?
Great book, the POE course is also worthwhile. nostr:nevent1qqsvdax4gv4jh0t8rcsxql4a88ydpxj9nyytfh2drggt8qt0k3tmrpspzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3qwtfnlhvhvm90lgsgyd6cu82tj3v429y7qkuu54srwzxpefppc2zqxpqqqqqqzuympcl
Braydon Fuller @Braydon Fuller - 29d
Will be interesting to see if this type of setup could be used for Meshtastic and LoRa repeaters, so more repeaters are setup as a way to earn routing fees. nostr:nevent1qqsqyc2hvprc87yqfeqyt3c6xmyps2swly20v3j0sc3lcmuskep8qmspzdmhxue69uhhwmm59e6hg7r09ehkuef0qgst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqrqsqqqqqpdueagj
What about magnesium and calcium?
Braydon Fuller @Braydon Fuller - 1mo
Same, looking forward to testing out DC-1.
nostr:nprofile1qqswhhhf99z77pfg80s2c00z27rusxn2tzss7450n34krkwa2yadhtgpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhkummnw3ezuerkv36zuer9wcq3vamnwvaz7tmpw5h8yetvv9ukzcnvv5hx7un8lpntld will change this, work outside and in the sun. 🤘🌞
Going to take another look at how many of my contacts have kind 10002 relay list metadata soon here and do another push towards having my relay fetch and sync events from those listed relays. Sounds like negentropy has also made some progress. 🤘
Not all may understand. Consider this parable from Luke 5:37-38: "And no man putteth new wine into old bottles; else the new wine will burst the bottles, and be spilled, and the bottles shall perish. But new wine must be put into new bottles; and both are preserved."
That seems so underhanded. There are plenty of other ways to introduce Nostr that doesn't try to hide the most important aspect of ownership. I'm so confused by this approach.
If someone doesn't see the value in owning their profile and thus private key, they will not see the value of Nostr. Even if they join they will likely leave. If they then realize that they value that ownership, and then realize someone else created their key, they will not value that key because it has been compromised already.
Running v1.0.2 for awhile and has been good.
JavaScript trademark dispute: https://deno.com/blog/deno-v-oracle nostr:nevent1qqs2sjwtrq8kuyand2duc4zf4p3f82k544p4vun6440a86tmmuffzscpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qklkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qxpqqqqqqzauajqx
I've just started reading "Fossil Future: Why Global Human Flourishing Requires More Oil, Coal, and Natural Gas–Not Less" by Alex Epstein, and so far it's fantastic (started with chapter 9)!
So presumably with a unique IP, it would be possible to determine sender and receiver (however not likely in mass). If used with a VPN or Tor, it's much more difficult.
Is there a page that documents what metadata is made available? From my understanding, it is very little, and designed with the intention that the servers could become decentralized. I doubt their company would make that move anytime soon, however.
That's the goal, I think. 🤘
Good idea, had a similar thought. It'll also be a lot more simple when NIP-65 relay meta lists are standard for all follows. A lot of what Gossip has had to do won't be necessary then. I also think some peer-to-peer (or rather relay-to-relay) networking will go a long way towards improving implementations. If more relays sync the profiles and relay lists for their wider network, the availability of these records will be far more accessible and efficient. Implementing this in a way that has a configured list of "discovery relays" is centralizing. Being able to ask anyone of known npubs/profiles listed relays, so long as they were in close proximity (based on a social graph) could be very useful and decentralizing. Advocating for use of nprofile instead of just npub I think is also important.
It may be useful to have a comprehensive site or in-client feedback on how well various clients and profiles support this approach? Might help move progress forward.
