typical experience for a seasoned engineer:
- use some technology for decades
- some company puts it in a nice wrapper
- suddenly massive success
- wait, normies wanted that?
hope these paid relay admins let you move to a new pubkey if you ask for that. i've bought access on nostr.wine (#[0]) for a few of my ActivityPub bridge accounts on mostr.pub so i can broadcast them to nostr.wine.
working on the crawler again since i can't sleep https://void.cat/d/LabUdN4cvtPB8nykWsjHpR.webp
board of directors?
yes, i'm bored of directors too.
not a bad idea. i'd probably put one on one of my public Linux servers but with some kind of protection on it so only i can use it.
nrcheck isn't the best name. might give it a new name while it's still young and just put a redirect on the website.
i assume some people are running private relays that aggregate and filter or broadcast traffic.
whoa, received a lot of zaps today. can't see them all since some of those went to my ActivityPub bridged account. i still receive the sats. just can't see who they're from. 😅
you start to see more and more obscure relays the further down the list you go. near the bottom, classics like wss://192.168.0.1 sometimes appear 🤣
the relatively manageable level of traffic from relay.damus.io with a subscription to all events tells me that the network isn't big, because that's a relay pretty much everyone at least posts to, and i'm not seeing a massive number of unique tagged users across the profile updates i gathered.
okay, so at least i've got a little thing running now that grabs any user profile/follow/relay updates from relay.damus.io and maintains a database of them. and i also have a piece of code that extracts any tagged user IDs and figures out which ones are missing in the database. the idea is to look them up and put them in the database too. this is to improve my tools at https://nrcheck.tigerville.no and https://nosy.tigerville.no to make them faster and more reliable.
database schemas aren't easy, even with a NoSQL DB, because there's still indexing to think about.
working on a little thing that simply indexes users, follows and relays in MongoDB for easy querying. it listens to events on a relay but doesn't store them anywhere - it only uses it for clues about what to look for.
for my indexer, maybe i should just stuff all events in a big MongoDB collection named "events" and hope for the best.
so, listening to Nostr events in node.js wasn't hard and neither was connecting to MongoDB. the trickier part comes next...
watching the raw stream of Nostr events come into my little node.js program https://void.cat/d/XfzTveA4GxFkzK496XWLNZ.webp
a tool for tracking down Nostr whales 😂
https://nosy.tigerville.no is out now in case you didn't see it already
yeah, in hex format
https://mostr.pub has a little info