On Amethyst the first @ reference doesn't resolve properly @npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
#[5] , maybe a slight bug in the "@" ref parsing above? I added an errant extra "t" to the end of @npub1rfd0hxdzcze6pzj29thuz34vur57wm9quje7w3edxjgusq6m47csnl7wrt 's "@" ref and now it's trying to find a profile for an invalid npub.
If it helps, my regex for these includes explicit char count:
```
(@npub1[qpzry9x8gf2tvdw0s3jn54khce6mua7l]{58}|@note1[qpzry9x8gf2tvdw0s3jn54khce6mua7l]{58})
```
Each step of the esp32-S2/MicroPython #[0] port consists of a long series of UI disasters punctuated by occasional moments of breakthrough bliss.
We ain't at bliss yet.
Def how easy it is to build new tools and use cases on such a simple, permissionless protocol.
The proliferation of clients is just one example. Remarkable how all that dev talent is free to just innovate, rather than being bogged down by complexities you find in other systems. The ensuing explosion in features and rapid maturation has been incredible.
(their dogs, too!)
I wrote a regex. And it seems to be working.
20+ yrs into my programming career and this is the first time I can say this.
#[2] in Amethyst this looks like this note is from #[1] but that's the NIP-26 delegatee for #[3].
*subtract ~20 due to me testing crap.
Whoops, and way too easy to accidentally hit boost instead of just replying when using Amethyst!
A confirm dialog would be awesome, #[4]
Be grateful for the long post auto-collapse! Crucial feature when there are no limits to post length!!!
Yep, second screenshot was straight from Iris!
If I understand this right, she and I have plenty of relays in common already, ya?
Decentralized social media is still so weird!
Amethyst can't load #[0]'s profile info for me, but has her big follower count.
Iris has her profile but missing most of her followers.
I'll need to dig in deeper, but from what I can tell at a glance, yes!
I don't think we're on the same page.
I run a VPN into my LAN so I can access any of my home machines from wherever in the world.
However, it would be cool to give my multisig cosigners access to, say, my private Nostr relay, by allowing them in but restricting their access to just the relay server's LAN IP. I don't want them to be able to see anything else inside my LAN.
Does TailScale offer any fine-grained access permissions? i.e. user X can only see IP addr Y in my LAN.
I tried getting Docker set up on a Windows machine for the first time this morning and had some not-noob-friendly roadblocks (enabling virtualization in the BIOS, then some `netstat` issue to expose the container's port).
But all worked well from then on!
