Did you check out my Hihjlighter guide? It describes the older version, but still may be helpful: https://lnshort.it/highlighter
Had my first cup in about a month today. This definitively helped me realize I’m not hooked and I’ll be fine having an occasional cup of coffee, not 2-3 a day like before. Liberating
Max got Neurolinked 😂 nostr:note1pnrvlj9zqvwnp6da7sj29se9q5wu8t7nc2u5eyu7u3utfz9ng9askshzrk
Parquet Courts - He's Seeing Paths
Damn! My first coffee after a caffeine-free saga of a month, paired with the tunes from #[0] is way too electrifying! It's like a dance party in my head 🎶🎧🕺🔥
They should start making louder iPhones lol
Every Thursday and Friday evening 
#zapathon 
It’s the human readable paths that need to be implemented across the platform first. As far as I understand it is not something super complicated, but takes time given there are a lot of other things to be done under the hood. Things work different on Nostr than they do with traditional centralized platforms and we are really early. Some patience is required 😌
At the moment I use https://lnshort.it to produce short links as naddrs in long-form posts are massive. And I add the image to the note manually. That’s the best solution I could come up with so far. Please let me know if you find a more elegant way.
You can see an example here: nostr:note1alz0lexz6nxetrac34g0pqujh98vrp8ryj6hmggvecd8pzxvan9qg6pwm0
Happy to bring value 💜
Previews aren’t yet widely available. The feature is on the way. Some articles do have a human readable path, but the process is not yet automated. Soon™
Regarding Nostr notes (and other stuff 😉) Habla automatically turns any Nostr-related link into an embed. Other option is writing “nostr:” followed by an event ID - be it a note, an npub, or a naddr.
That said we are still in the early stage and there’s so much on the roadmap, so don’t judge us too strictly 😅 it’s all coming, just needs some time.
Also I recommend utilizing the preview features — one in the top left, right above the composing field (looks like an eye) and one on the right side of the composer dashboard, which lets you toggle between the markdown, Split View and a preview. These features are underestimated 😄
I’ll be releasing a detailed article on Habla features too. Just waiting for a few things to be fixed/implemented.
By the way, just checked out your site.
What a vibe 🤙 🎶🎧
Will try to visit you often
If you’re self hosting a website, you can follow one of the traditional guides on email forwarding.
For Nostr and LN stuff check out these guides:
NIP-05 setup: https://nvk.org/n00b-nip5
LN forwarding setup: https://guides.getalby.com/overall-guide/alby-lightning-account/where-to-use-your-lightning-address/how-to-use-your-own-domain-in-your-alby-lightning-address
A few foundational ones are enough for most. Just like very few know the periodic table by heart, but most people know the essential elements.
I think I cracked the code on private groups.
Long-form post here: https://habla.news/a/naddr1qqwkzttswfhhqmmnv9kz6en0wgkhqunfweshgefdvaex7atswvpzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqvzqqqr4guuvl8xr
Instead of relying on relays to implement access control as in this PR (https://github.com/nostr-protocol/nips/pull/566), we could combine the Gift Wrap proposal (https://github.com/nostr-protocol/nips/pull/468) with #[0] 's nsec bunker to create private groups with easy administration and moderation!
Gift wrap fixes DM metadata leakage by using a temporary private key to send a DM to a recipient. The recipient decrypts the wrapper to find a regular nostr event inside. This could be another kind 4 as in the proposal, or anything else. Which means you can send kind 1's, 7's, or anything else in a wrapped event.
Now suppose you had a pubkey that you wanted to represent a group instead of a person. Put its nsec in a (modified) nsec bunker, and now you can allow other people than yourself to request signatures. A shared private key!
Anyone who has access to this nsec bunker could de-crypt any gift wrapped note sent to it. Relay-free read access control!
There are lots of ways you could manage this access list, but I think a compelling one would be to create a NIP 51 list (public or private!) of group members and set up the nsec bunker to authenticate using that list. Boom, dynamic member lists.
You could also create a NIP 51 list for admins, and pre-configure which event kinds each list is allowed to post using the group's nsec. So maybe members could only publish wrapped kind-1's, but admins could publish wrapped kind-0's (you can now zap a group!), kind 9's for moderation, updated member and moderator lists, normal kind 1's for public information about the group, etc.
Gift wrap would support:
- leak-free DMs
- Fully private groups
- Public-read groups (nsec bunker would allow for admin, but everyone would publish regular instead of wrapped events).
- Organizations and other shared accounts, with role-based authorization (list/kind mappings)!
Of course, no clients currently support this kind of thing, but support would not be hard to add, and it creates an entirely new set of affordances with two very simple applications of the core protocol.
There are a few drawbacks I can think of, of course. Gift wrap makes it harder to search notes by tag. You could:
- Leave all tags off (other than for DM recipient as in the proposal)- Selectively keep tags that aren't revealing of identity
- Encrypt tag values. When a client wants to query a tag, it must encrypt the value using the same pubkey and include that in the filter. This, I think, is ok for the use case above.
There are also a number of proposals in the works to fix NIP 04 DMs which are apparently broken from a cryptographic standpoint, so implementing this should probably wait until that stuff is sorted out. But it should be possible however that ends up materializing.
So am I nuts? Or is this a galaxy brain solution?
#[1]
Damn, #[1], I better hurry! 😅
Hopefully those who don’t want to learn from past will learn from Netflix. Happy they are providing at least some food for thought
Hell yeah.
