My girl #[0] is SO CUTE!!

@#[1]

Enabling IP forwarding is an easy step to miss on the machine that runs the exit node. All the steps should be in the linked gist!

Yes, you got it!

Don't tell Netflix, but I configured a Raspi to route my mom's Roku traffic through my home IP via a Tailscale exit node.

Took a couple hours over the weekend to figure it all out but it seems to be working! And I did my best to document the steps (though good luck getting your hands on a spare Raspi!).

https://gist.github.com/kdmukai/ab7b2b1de898c6c3e64ffbe1e0316bbe

Awesome!! The name is amazing! #nip26 slowly happening.

#[7] how about some insanely fast purple car renderings? And/or Vin Diesel as a nostrich?

omg #2nostr2furious needs to be a thing!!!

Ha, I'm so spoiled by all the Nostr client devs being so responsive here that I didn't even think to log a github Issue!

I thought that didn't matter anymore in a v24.0 "full RBF" world?

See #nip26 in action here:

@#[5]

Your UIs are too pretty. Stop it!

Whoa, pretty wicked #[0] bug #[1]

Paste in an "@" note ID reference and then add a misc char immediately on the end of the ID. Browser autoloads that errant note ID into the address bar for some reason and makes it a bit hard to escape back to where you were.

Is this just in your own dev fork? Not seeing it work in Damus 1.1.0 (2) in TestFlight.

see: #[4]

Follow @npub1kumadawgefxjt2c293whsan5sfmdg5tylm0uk39enc6uxxfy5m4scrz2v7 for all your #nip26 needs!

And play around in https://nostrtool.com to easily make your own delegated posts.

Nowadays feels like I'm looking at $1mil in Raspis here.

tldr from tonight's Nostr client testing:

Snort > Iris when creating a post that references a note ID.

Referenced posts look amazing in Iris, but since Iris doesn't generate "e" ref tags, other clients just treat the note ID as plaintext and don't wire it up.

Damn, latest Amethyst version crashing like crazy on me.

Back in my day we called that dereferencing a pointer! I think. I dunno. C++ was a LONG time ago!

"At"-ception?