This is my npub represented with GLYPHBYTE. Grab the image above and upload it here: https://www.glyphbyte.dev/app/
...and you'll get my nostr profile.
Glyphbyte is a simple idea: hand-written data that attaches a piece of the internet to a physical surface.
One day I thought: why can't we have a QR code that you can memorize and draw by hand? That's glyphbyte.
Write the first few bytes of an event id or pubkey as glyphs, and snap a photo to match the prefix against a relay.
OceanSlim (npub1zmc…7f60) 's excellent Grain relay (https://github.com/0ceanSlim/grain) accepts partial prefix id and author queries.
If you have the first handful of bytes, you don't need the whole event id or pubkey; you either get exactly what you were looking for, or you pick from a list of partial matches.
Either way, you only have to write a few symbols to encode anything on the internet.
fiatjaf (npub180c…h6w6) this is why partial id and author matching matters, and I have a fork of nak that allows partials on REQs. Partial matching was originally supported by NIP-01, and it was optimized away for no good reason. Now we have a good reason to have it, because nostr allows us to effectively represent anything on the internet with a couple hand-drawn symbols. That's pretty powerful IMHO. GM btw