I'm gonna DM you from Amethyst and you'll never see it 😂

Reply to this note

Please Login to reply.

Discussion

Exactly 🤣

just sent you a dm. from amethyst. I assume you got it

I did. Its not in primal though because they use different NIPs. Part of the problem.

Primal's DMs are NIP-04, they are terrible, and the primal team should update ASAP if they care AT ALL about user privacy

Its actually on my to do list to a PR to get NIP-17 DMs in Primal because you're right

What is holding every client back from fining the DM standard? It’s unacceptable.

Honestly, laziness.

NIP44 (used in NIP17) is a different encryption scheme. It's a little harder to implement (and I say A LITTLE, because honestly any competent developer should be able to build it).

I’d love to just use KeyChat but you never even know if your recipient will see your message because it isn’t backward-compatible.

Never used keychat personally, but amethyst works well with DMs, as does 0xchat

KeyChat runs on iOS so it’s easier for me than using Amethyst which isn’t on my primary device. I have 0xChat installed but not signed in at the moment.

ah you're an ios user, I see. seriously I think nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z should focus on rewriting the app to use compose multiplatform, so we can have amethyst everywhere

Quartz is almost there, but man.. iOS needs so much :(

don't worry about it, good work takes time :)

Maybe you could try using Aegis as your signer on iOS.

I don’t even know what that is, but if it uses NIP-46 I got bad news for ya.

It’s a nostr signer for iOS. Unfortunately, on iOS you can only log in through NIP-46, but Aegis uses a built-in local relay as the bunker relay.

On the surface, it sounds amazing and I would love to use it, unfortunately I recently learned that the NIP-44 spec for encrypted payloads which all NIP-46 signers use has a data size limit of 65535 bytes, and this happens to be too small to transfer my follow list, which is over 200 kb. I discovered this while trying to enable that feature in #PlebsVsZombies a few weeks ago. I might be an edge case, but that’s a hard cap I can’t get around and it seems much too low to support steady user growth. If I’m following around 2800 users (down from about 3300 due to culling my zombies) and my follow list is still more than 3x the size limit to use a NIP-46 signer, that caps the maximin number of follows to around 900.

Why does your follow list need NIP-44 encryption? Isn’t it a plain text list?

idk but mute lists have an encrypted seciton

Yeah, I’m sure that’s part of it.

I see, this is a limitation of NIP-44. Even without using a signer, the problem still exists

Exactly. This wasn’t well thought out IMHO.

the number of ways in which the hurriedly ushered in "better encryption" protocol was screwed up was many. i didn't know it had a max payload limit

I implemented it into Bloom in like 10 minutes it's not that hard

I suspect there's also a lurking suspicion that NIP17 is not the solution so may as well take a pass on it and wait for the next thing. and on nostr there's always a next thing.

NIP-44 is versionable, soo....

Sure, but it’s a constant moving target, you can understand the fatigue. And six months ago there was talk of nip-ee superseding all other chat methods , jeff hoping to put out a sort of convert kit for dummy clients. But thats all quieted down.

Didn't realize you were part of the primal team, still, I don't take back anything I said, haha

Lol I'm not, just tired of shit DMs