Bad robot 🤖

Are we there yet?! 🚀🌖 50 years is a long wait for something like this, time preference notwithstanding... Especially if we didn't actually go the first time around 😎 Godspeed! 🤞

I love how flexible and composable things are in Nostr. Running @npub1hqlx...gspw relay locally on my phone now (thank you @greenart7c3 !). Added it to the list of relays for my npub. Pulled all my events into it locally. Can also now probably do a bunch stuff while completely offline. Much delight

Claude Code has also been very eager to keep adding model co-authirship trailers to commit messages, and periodically forgetting instructions to the contrary. Solved it with a Git commit hook eventually - with a reject message gently reminding the agent not to do that View quoted note →

Eventually you gotta level up though. Hello @GrapheneOS, @Zapstore and all the ungated open-source and Nostr innovation and creativity!

Nostr is fascinating and has been a very rewarding rabbit hole to be falling into. I couldn’t help it but start itching to try to measure the current levels of user activity and the trajectory. 

It looks like we have been hovering at around ~5k daily active users and ~30k monthly active users for the past year - based on the data I have right now and the current methodology.

This is currently based on aggregating most of the major events in the network indicating user activity - posts and replies (kind-1), reactions (kind-7), zap receipts (kind-9735), etc. Some of the more obvious and egregious spikes due to bot swarms, etc. have been removed. The data is from two major relays so far - relay.damus.io and relay.snort.social (both support negentropy, so historical data acquisition with strfry is straightforward). Pure lurker activity (follow-list updates, profile updates, etc.) is not currently measured (requires continuous acquisition of replaceable events) and can lift these numbers meaningfully, but not by an order of magnitude most likely. 

Would love to hear if this aligns with what folks have been seeing through their own methods and observations! 

One of the next aspects I’m curious to explore is what happens if I start moving out on the long tail of relays by progressively acquiring and incorporating data from smaller relays for this analysis - would that simply lift the baseline DAU/MAUs while keeping it roughly flat, or would we see growth?

Much delight - getting pretty happy with where I’ve been able to progress to with my envbox builds over time. Two separate units now: one running next to the solo Bitcoin miners and the other in the living area. Near-realtime environmental metrics produced: temperature, relative humidity, illumination, barometric pressure, CO2, particulate matter. The unit next to the miners has an additional noise level sensor - proper factory-calibrated dBA. All metrics are exposed by the units via a REST API. Data is continuously acquired from the envboxes and the miners by Telegraf into InfluxDB and plotted in Grafana - all running on an Umbrel

Running Hydra Pool :) On an Umbrel, on mainnet. Much delight. Smooth sailing - great instructions on hydrapool.org. This is running :latest via docker compose. Also built locally from Rust source earlier - breezed right through it 👌

GitHub

GitHub - 256foundation/hydrapool: Open Source Bitcoin Mining Pool

Open Source Bitcoin Mining Pool. Contribute to 256foundation/hydrapool development by creating an account on GitHub.

Awesome job guys, amazing! Thank you @256Foundation @npub1x0yw...9t7k @econoalchemist et al