Rebooted an LND node and it cant connect to peers. good times
i found out this morning my refactor a few months ago created a regression. shit happens
i have no knowledge of sailing apart from involves, boats, water and wind
what did you learn today
alot of resources provided by others. as for active projects, look to
Theres over 200 active bitcoin education projects there throughout the world looking for funding. Quality varies, much like donorschoose.org for classrooms
ive been doing eggs in cast iron for some time and always cook em with butter. slides easy
I spoke with nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj about his reasoning to remove GiftWrapped messages from eden.nostr.land. It's not that he doesn't want users to have private conversations and it's not that he's censoring content. It's that he doesn't want to unknowingly store images on his relay.
I've said since the beginning that NIP-95 is a great solution for decentralizing our images, however I've also said that it's bad form to make relay operators store binary data when they didn't originally intend to do so. Relay operators should have a choice in that matter as it will drastically increase their operating costs. With GiftWrapped messages, relay operators could technically store binary data, since they have no clue what type of content they're storing. The message could be a really long message or small image.
GiftWrapping is more than DMs.
I get it now.
This is why we have these discussions to hash things out and to learn. This is how the protocol grows and we end up reaching consensus on how to move forward for all to benefit.
I'll be adding eden back to my relay list... for now 😉
im just glad eden.nostr.land is working again as i thought we all got rugged but i guess it was maintenance
My mempool still filling
Id like an easy way for me to see at the end of a month. ...
- how much time spent in app
- per relay, data rx/tx, event count read/write
- per file serving domain, data rx, and files read
and have integrated ways to send sats to each of those type of entities, whether i have a paid subscription to relay or not.
peoples consumption and value attained differs and having objective data helps in applying sats to the unseen
Ive just finished clearing some old data on 3 raspberry pi nodes. Two of them will stay in service as is for another 9-12 months while the third is going to be reprovisioned for #Start9 to have an environment to test package install of #Nodeyez.
You can incentivize this by contributing on the Geyser Fund project page here
theres been good videos on this... and my net recommendations are....
cheap dice is fine, you dont need casino dice.
you should probably check for dice bias, which plagues cheap dice, but is less of an issue if more weight (eg metal) and rolls well
regardless, when rolling, roll all your 6 siders at once and let entropy set the order you write them down in.
see my how to here
https://github.com/vicariousdrama/howto/blob/main/bitcoin/generating-device-seeds-using-dice.md
DN & GM
If you havent broken any laws that harm nobody, you are the one being harmed.
I want a feature in clients to let me choose whether i attempt to rebroadcast to a relay or not.
An all or nothing solution wont work for some paid and private relays. But I would love to be able to
- mark relays for broadcast, and situation (all, follows, liked, members of selected list)
- broadcast ALL notes to my private LAN based relay when on network
- broadcast only notes of those i follow or like to relays ive marked for broadcast
- still broadcast to all on a note by note basis
TLDR - i want configurable rules for auto broadcast that should be client specific, not necessarily published as rules for all clients or made public