Avatar
hodlbod
97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322
Christian Bitcoiner and developer of coracle.social. Learn more at info.coracle.social. If you can't tell the difference between me and a scammer, use a nostr client with web of trust support.

Same, you use your time very differently when it doesn't belong to you

Is anyone else seeing a lot of likes from one-off pubkeys?

Looks awesome, I don't know much about it

Can you point me to the notes you're looking for? It could be a kind coracle isn't asking for.

I think it's good, but doesn't fix relay surveillance entirely (if you're AUTH'd and request stuff from an alias key then the relay can correlate the two keys). It also means other DM clients won't interoperate with 0xchat if they don't support alias keys.

That project is way above my pay grade, but I'd love to see it

NIP 44 and subsequent work on encrypted messages represent a major improvement over NIP 04, but are not anywhere near on par with simplex, signal, or MLS. If you want real privacy (foward/future secrecy), use those instead.

Lol yeah, signal this ain't. The new encrypted messaging stuff is what I would describe as "barely adequate" vs "not adequate" which was the case with nip 04.

We're currently having a conversation about the api for signers supporting NIP 44. Currently it looks like we're going to provide a `getConversationKey` method, which clients can use to generate and store keys used to decrypt DM history.

The justification is performance β€” it's expensive to re-calculate the keys on every call to encrypt or decrypt. It's also expensive to make lots of network calls as in the case of NIP 46. Both of these are easily solved though β€” the signer can cache keys just as easily as the client, and the network latency issue could be solved by adding `encrypt_bulk` type calls.

The downside of having a getConversationKey method is that clients can generate and store keys that are valid forever. Evil clients could do this without the user knowing, and send the keys to a server somewhere. From that point on, that person would be able to snoop on and forge messages between two participants. For me, this complete defeats the purpose of signer extensions.

Am I wrong?

https://github.com/nostr-protocol/nips/pull/940

I love how he's podcasting from the middle of a forest fire

Having a hard time focusing on work as of this morning. Two more days!

I am completely checked out for Christmas I think

Recursive alternating colors, rather than sequential. Think quote notes inside of quote notes.

I'm not quite sure what you're describing here, the summary is that I use the inbox model to send shared keys to members. Those invites have relay hints to help them find the group. Everything is wrapped using the nip 59 draft. You can read the spec here: https://github.com/nostr-protocol/nips/pull/875

Thanks for liking coracle! The new release removes several old features which I hope to revisit later.

Maybe there are reasons to do it nostr-natively (the IP obfuscation is not one). I agree we should use existing solutions, tor is just too slow for people to bother with usually, so it's probably more a question of making this stuff accessible with a good UX. I think a harder problem than IP obfuscation is filter analysis anyway. If your client sends 100 filters in a minute, there's a lot the relay can learn about your pubkey.

Trying to talk myself into listening to the health ranger report again since there's frequently high-quality content hidden in it. I downloaded the full archive of episodes since 2015 and I'm going to listen to some from 2019/20 to see how his predictions turned out. His titles are just so spammy though, here's a random sample of episode titles:

$ cat hrr.json|jq '.[].item_title'|shuf|head

"Brighteon Broadcast News, May 1, 2023 - FOURTH bank collapses in USA while Russia unleashes devastating new attack on Ukraine"

"Justin Beiber's PARALYZED face 'Ramsay Hunt Syndrome' is actually a VACCINE INJURY"

"Same people pushing VACCINES also push CHILD MURDER / Infanticide"

"You will either be a fool BEFORE the crash, or AFTER the crash"

"Situation Update, Jan 18th, 2022 - Corporations take out life insurance policies on EMPLOYEES then push vaccine MANDATES to kill them and cash in"

"Health Ranger nails down recommended source for GOLD and SILVER"

"Helicopters OBSOLETE? New drones will carry PEOPLE"

"There is no way to DETOX from the mRNA vaccine"

"GREEN NEW DEAL: Build railroads across all the oceans!"

"Antifa terrorists and the Insurrection Act"

nostr:nevent1qqs0dy2dvp70w7p2yrwlhf75umwfhk8qarddtcfn0kst5gcpy6q820qpzdmhxue69uhk7enxvd5xz6tw9ec82c30qy28wumn8ghj7un9d3shjctzd3jjummjvuhsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qyt8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6tcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq3wamnwvaz7tmwdaehgu3wvdsksmr9dchx7un89uq3jamnwvaz7tmvd9nksarwd9hxwun9d3shjtnrdakj7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcjmkkm0

Reply all you want, I'll just generate more pubkeys to like my post

There are a lot of things I appreciate about nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgspz9mhxue69uhnzdps9enrw73wd9hj7qgnwaehxw309ac82unsd3jhqct89ejhxtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsa887h4 . I'm currently listening to Alex Jones' interview with Tucker, and the fact that he of all people speaks highly of Jack as Twitter CEO speaks volumes.

Well, I think Amber will probably support the same protocol, but remote key storage seems best to me because it covers all platforms with a single key management app.

We talked about this a bit on TGFN, content creation is the addition of signal and noise. Content curation is a signal amplifier

Open source your search implementation as a DVM that other people can run

You can already do that on that dialog. Although I do have some hardcoded defaults that could go away

I enabled reposts in Coracle, and holy moley more than 50% of my feed is reposts. Lame, you guys.