It’s a simple spec so it’s hard to imagine how it could go wrong in implementation. I don’t have an android device handy, and only going off secondhand evidence from my (skilled) cpp contractor trying to build 42 into strfry.
If it requires any amount of UI to enable on amethyst, then perhaps we missed something, but our very sketchy initial tests indeed failed with our NIP-42 ref machine running nostr-rs-relay.
So apparently Amethyst claims to support NIP-42 but in reality, doesn’t actually support NIP-42 🤣
Couldn’t carry the Leica for this one. Will post my best attempts at #shotOniPhone as a test of topaz media upload tomorrow (possibly)
Charlotte de Whitte. It’ll Do Club - Dallas Texas. Lfg!
Face the fire.
💡nostr based system management and monitoring
the client is straight 🔥
Follows needs to be a dedicated nostr kind.
It’s way too easy to nuke a carefully curated follow list with a single accidental event write.
Perez looks pretty screwed lol #f1
Build 22 is popping the relay detail view off the stack super quickly. https://nostr.build/av/95e38843a735f47349e30be9f41a78c5a47201f82ee13f0320863728e412be9e.mov
#[0] you shipped an infinite reconnection loop in the latest build #fixOldBugs #createNewOnes
Time to run a personal instance of strfry
The image is visible. 
Let’s speculate for fun: do you think Perez can hold his position above Max for the entire race?
I’m hoping he can - but I think the start of the race will determine how likely that’ll be.
I did this with topaz when I edited my relay list for the first time. Not fun, I sympathize 🙏🏻 #nukedMyFollows
Does Plebstr call into a centralized backend?