yeah he loves them. he reads everywhere we go. this is him reading at a bar in sayulita while we were dancing 😆 sooo much better than phones and his vocabulary is noticeably improving. https://i.nostr.build/kjBFGjc3jWb8SsLR.jpg
Weird, those results are only 4 years, our nodes are both 6 years old.
I was able to get to it somehow but there doesn’t seem to be a querystring for it.
Heres the earliest photo i have of the original #reckless mainnet crew:
https://cdn.jb55.com/s/6cab15e1b008dd5d.png
Maybe need to crossreference with this image 🤔
If i remember correctly rompert was one of the first nodes as well, i think i misremembered the felix one as rompert and assumed the search results were correct. Looks like im getting random now :/
Should reach out to them to see what their earliest db entries are
Imagine having that much money just for a domain, I could use that to pay all of my current contributors for a few years… instead I am just losing contributors slowly due to lack of funding and denied grants. Sigh.
I personally do but damus has multiple apps now built by many people who don’t get paid. I would like to raise money so they can keep working. I’ve had many people come, do great work, and leave. The churn kills momentum.
onboarding is somehow getting way worse. we're stopping all new new feature dev to focus our onboarding experience. we're not going to win if people give up before they even start.
yes there are many things, we had an hour long meeting about it and identified like 5+ pain points that we are going to be working on.
Biggest one is cold-start cache and having no profiles to search for. We're going to look into a profile precache of all of the users on the network. Should be pretty small and should work well until we get much larger.
Another one is the QR code experience, damus QR code scanning is janky and downright broken at times. We were looking into ways to load more profile data through the nprofile, even without and internet connection.
Profile picture and banner optimization, a lot of profile data fails to load on bad connections because things are not optimized across the board.
Onboarding checklist to guide users to set up missing things.
Lots more
A Bitcoin node will detect bugs in the matrix
since I'm not seeing any serious memory or disk issues, and assuming there are no bugs in bitcoin-core, I wonder if my bitcoin node is getting hit by cosmic rays and bits are getting flipped every now and then, leading to leveldb checksum errors.
I looked into ECC ram but I may need to build a home server, since it's not common in desktops motherboards.
Is this is why you’ve been going on about ecc memory @semisol ? I found a post about it from greg maxwell 10 years ago as well, saying all his non-laptop machines use ecc memory:
https://www.reddit.com/r/Bitcoin/comments/2jpk54/risks_of_running_bitcoin_client_on_a_computer/cle3qyb/nostr:note1ktns7scrqr00h9a400eajn8k23hcxzzp35syfr7j4tvzjkdpjjdsj4z0sf
This machine is on a UPS and doesn’t ever randomly restart. It’s never unstable. I don’t run it hot. If it can get corrupted from ungraceful stops then thats a bug.
Notes by jb55 | export