Okay. I'll have a light review of the code tonight. It's flutter+rust so that be a review of the mild headache kind, but I'm getting used to that stack a bit more now.
(edit: holy shit dat commit message insanity - I'll probably be the first ever to actually look at the code other than Claude)
[..]
* feat: disable message send when media is uploading
* fixup! feat: send media from chat input provider
* fixup! feat: add media tags in message sender service
* fixup! fixup! feat: send media from chat input provider
* fixup! fixup! fixup! feat: send media from chat input provider
it's not like git rebase -i is rocket science.
scrolling down further I see mega-squash-merges, refactor+feat+bugfix, unsquashed rustfmt fixes... all the things that will give you shivers.
So as a joke I had Claude review in parallel with me, to see if it came up with something I'd missed. I had to actually push it because it was off regarding how the blossom integration works, lol.
**IMPORTANT:** My previous comment about NIP-44 encryption was
**INCORRECT**. After reviewing the actual source code in the
`whitenoise` and `mdk` repositories, here is the factually accurate
encryption implementation:
[..]
Thank you for prompting me to verify against the actual source code.
Damn bot is like a lazy jr dev that I'd fire if fucked up like this. lol.
How did you guys even manage to send messages. If I c&p siggy's npub above to create a new chat, it says "this user isn't on white noise" and I'm stuck at a screen with a link to download the app
Not entirely sure what you mean, but if you mean discovery, it depends on your relay. The most popular relays can be slow sometimes, and I figured that this is why when I open Amethyst it takes up to 3-4 minutes sometimes to load everything up.
One of the things I think is needed w/ nostr is "offline-first", like email. I'd want to have a local cache of everything I've already seen; especially my own notes, and keep track of what got published where, republish when needed. This may feel antithetical to some nostr (pwa) dev patterns but local state should always trump relay state, even if you run your own relay.
The thing that's missing for me is... remote signing. Until then, it can only be throwaway, separate identity; i.e. I wouldn't use this for my SN-listed npub until there is bunker/amber integration.
I tried to follow this thread to discover if your recommendation are a good alternative – but I’m too normie to understand dev convo. I’ll keep talking nobody in mesh bitchat
You can also use PGP to encrypt your xmpp messages if you prefer, but my point is xmpp is very easy and lightnweight to self-host. You can run it in a rpi1, 2 devices...
Yeah it was hyperbole. I actually have an xmpp server on my own metal. And a private nostr relay. And a whole bunch of things. I just wanna test new software. Having fun with whitenoise review rn; it's basically 3 bespoke repos and a headache haha.
How real is the possibility to fork simplex? We don't need huge servers for normies use it like whatsapp, we just need a lot of people self-hosting and set up storage rules how they see fit imo.
If keeping digital hygiene, like using a spare phone only for that app it would be fine using even MAX messenger. Just keep separate private and public matters.
and no, just read that some of them got closed on state request.
git rebase -iis rocket science.rustfmtfixes... all the things that will give you shivers.fixupbut didn’t actually rebase to make use of it 🤔Did you receive the message from some guy?whitenoisereview rn; it's basically 3 bespoke repos and a headache haha.