Nate

Well, I might have just had a 'productive' all night gaming session followed by sleeping into 4PM. Got called to do a set of 9PM-9AM shifts, because of some rather high winds, at the local power company I recently started working at. Wish me luck.

Made a revised version of my older social media protocol comparison post https://nate.mecca1.net/posts/2026-03-08_microblogging-pr… And a meme to go along with it: I'll also share as a NIP-23 Nostr post in a few moments. #blog #blogstr #nostr #activitypub #bluesky #meme

🚀 📝 4b63fee0… 📝 6cae3bf7… #GrapheneOS

@Soapbox @Alex Gleason @MK Fain @Derek Ross Hey, random thought, if it was a useful idea figured you all would be the people to make use of it. Has there been any consideration of using Nostr for age verification? A user verifies their age in a semi private way (say, a small credit card transaction) -> provider creates an event or badge of some kind and applies it to their profile -> the user of the profile can be assumed to be of age without needing to provide proof to relays or other services. It wouldn't exactly be anonymous, but it'd probably be about as pseudonymous as you could get for an age verification (the npub with an age attested isn't publicly tied to any details that were used to verify it). I know age verification isn't really in line with cypherpunk ideals, but a lot of jurisdictions are moving to require it. At some point soon everything from a Nostr relay to a GitLab server could require age verification, and as much as ignoring it now might an option, it might be good to get ahead of things and get the infrastructure for that sort of stuff in place. A verified npub or gpg key might be the least evil of all the options, and could probably be useful to verify an account for just about any small project or service (Nostr & beyond) without requiring the people verifying to pay for some external age verification service, and without requiring the people being verified to hand over their personal details to ever service.