GM

me when my neighbor closes a cabinet a little too loudly

The initial set of glyphs for glyphbyte were invented by me with no formal research and no data on how easy they would be to draw and recognize. It was just my best effort and guess. Based on some insight from my good friend @hzrd149 I am researching better glyphs that are easier to draw and also optimized for detection. So if you're excited about glyphbyte, I just wanted to let you know that version 2 is coming and both sets of glyphs will remain supported. I had the idea for glyphbyte literally 10 years ago and Claude built it for me in one day. 🤯 Thanks for the positive feedback! I'm excited to attach pieces of the internet to random objects with crayons. 🖍️ If you want to be able to find your events via glyph byte, make sure you're using a relay that supports partial prefix searches like wss://wheat.oslim.dev

"hey, what's your npub?" This is my npub represented with GLYPHBYTE. Grab the image above and upload it here:

glyphbyte

...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 '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 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

GM nostr! We're seeing a steady increase of @Fanfares adopters. I'm excited to see what @Contra will post next. Banger articles deserve a sat paywall. Sell your content, not your soul!

Encrypted comment sections live on @Fanfares. Buy the content to unlock the discourse. View quoted note →

This is what a reasonable BIP-110er looks like. 🫡 Respect View quoted note →

Sell your content, not your soul! Huge update today to Fanfares. If you have early access, go try it out. If you want early access, drop a comment or DM me with an example of what you want to sell/publish. We'll be leaving early access in a few weeks. Then anyone can sell on Fanfares without permission! We're also dropping NIPs soon so other apps can integrate The Fanfares Protocol for paywalled content. Big progress will continue until owning the fruit of your labor improves View quoted note →

The next @Fanfares release comes with a full cashu-based payment verification. Much more reliable than zaps, and extremely fast too. Instant multi-party content splits. Choose your own mint. NIP-87 mint recommendations. It's all there. Cashu was really the missing piece to make the internet work with internet-based money and enable radical monetization of any nostr event. Thank you @calle

My website divinecybernetics.com is an nsite that loads my #divinecybernetics articles. Soon, you'll be able to zap my paywalled articles on my website and they will unlock via @Fanfares API. Fanfares is the first `key service` for paywalled nostr content, but we're releasing NIPs so anyone can stand up their own key service either for self sovereignty or as a business venture. I'll be doing a lot more blogging and vlogging about Fanfares soon because the hard part is almost over -- bringing the thing into existence from nothing.

Imagine an internet built out of lego pieces. The pieces are nostr events, and any piece can have a lightning-based paywall. Anyone can paywall anything. Websites composed of individual pieces and applications and media. Everything signed and verifiable. @Fanfares is leaving early access and going full open source very soon. It's been a long road (2+ years) but what we've built has not been built before, and it operates at nearly every level of the bitcoin and nostr frontier. It's all of this, AND a social client on top. This is how we win: enable people to make money from their content without platforms.

GM! Getting a little better every day

@Silberengel @liminal 🦠 After analyzing the curated publications protocol, it looks like the @Fanfares paywall protocol is extremely complimentary! I'm super excited to get 30040/30041 support added to fanfares.io. Then people can sell books by the chapter; multi-chapter payment aggregation can be handled client-side too. I'd like you guys to review the stuff about the "X" tag in our NIP-FF-3, as you may find it a worthwhile and easy thing to add to Alexandria. You can ignore the stuff about OpenTimestamps unless it interests you, but the X tag is simple:

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

All 30041 events published from Fanfares will have an X tag; every other text-based event already does. Let me know what you think!

GM! My @Fanfares todo list never seems to get shorter 😅 but life stays exciting that way. If you haven't checked it out lately, we've made massive UX and speed improvements all around the app, and added paywalled articles to the list of content types. Give it a try, or ask me for early access if you don't already have it

GM. @Fanfares is FAST. Much faster than before. Have you tried it lately?

For the next @Fanfares release we are thinking: - paywalled video - full BLOSSOM interop - something you've never seen before 💬🗨 Let's see how fast we can cook it up 🧑‍🍳

This is a huge update to Fanfares! Now you can paywall your longform articles! (NIP-23) Very proud of our team: - migrate from Coinos to Cashu in one click (NIP-60) - Cashu in-app wallet and pick your mint (NIP-87) - automatic split payments - insanely fast media processing - performance improvements everywhere Enjoy! View quoted note → #fanfares #vb4v #longform #sovereignpublishing

I have finalized NIP-FF-3 as a potential successor to NIP-03. It's fully implementable now and @Fanfares will be implementing it shortly. NIP-03 allowed a nostr identity to attest to an event at a block height. NIP-FF-3 allows a nostr identity to attest to **content** at a block height, and minor edits to that content won't necessarily invalidate the OpenTimestamp proof. It's great for not only proving the time something was created, but also for proving originality and weeding out plagiarism at a protocol-level. You can REQ for events that have plagiarized yours via the X tag; obviously this depends on clients to opt in, but it's so easy that the primary reason not to is TREACHERY and RAPSCALLIONISM 😜 Check it out:

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

@Constant @Peter Todd @fiatjaf

GM. Here is the draft @Fanfares spec for edit-durable OpenTimestamp attestations for content, a successor to NIP-03:

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.