It's funny how govs around the world think their solutions that they've tried so far to fix the low birthing crisis would be effective.
The solution is simple, but hard:
Secure me a decent job that comfortably pays for myself, my partner, my however many children they want me to have, in a house that i'd buy within 1-3 years that would comfortably fit such a family, and continue to ensure this stability along with security/saftey.
How many countries are pushing this? Non, they just try and give you coupons =P
The Cat and the Dragon
I like it =3
#anime
Good progress today with DEN Chat regarding mobile usage, specifically about importing your (pin protected) seed/nsec into the PWA.
I was thiiiis close to use passkeys, but thankfully didn't. I just seperated the storage keys/seeds from the main domain's storage on the phone to a different one (main is web.den, the secondary one is vault.den) meaning if there's a supply chain attack on main then secondary won't be affected.
Basically this is close to the security of nostr browser extensions from what I gathered.
still not done, since did some decent refactoring with the login flow so still testing it, but assuming all goes well, mobile users will have a nice time.
Considering logic is a rare things these days, i felt inclined to add these terms in the terms of use in den chat
attatching files/images in the social page in den chat is busted, so don't use it at the moment.
DEN Chat v0.2.2 build is up. Patch notes:
Got an idea to improve Nostr Silent Payments (NSP) to make it less... catastrophic, but it would leak only to the receiver that you're the sender (so instead of it being optional, it would be deterministically known), but the benefit is that in case the receiver didn't get notified of the funds, events got deleted, etc, and there being no way to recover, there'd now be a way to do so.
The improvement is that NSP **should** only be used by other nostr users / used keys only, and so what would happen is that a address is generated based on the input of an ECDH result from the sender's private key and receiver's public key + ordering 0 and up with each discovered history in an address.
What does this mean?
1. Alice with her npub generates an NSP Bitcoin address from Bob's npub, sends money to it, notifies him, and that's it.
2. Bob didn't get the notification for some reason, and Alice already closed everything (her app, and cleared her cache too, so everything is clean and supposedly unrecoverable).
3. Alice would then grab Bob's npub and generate the same address again from the first step, and resends the notification or just tells him that she sent him a transaction.
4. Bob now gets the notification and retrieves/spends the funds.
5. Let's assume Bob still didn't get the notification, but what he can do after known that Alice sent him money, or suspects it, he can just take Alice's npub and see if he received funds to any of his bitcoin addresses that Alice could have sent to, and he sees there are funds in one of them so he can now spend it.
The recovery is deterministic now instead of random tweaks, but yea the "downside" is that if if either of them get compromised then the history is known between each other. The same kind of risk associate with DMs on nostr basically if keys leak, but hey, better than lost funds eh? / having a higher chance of recovery. I'd say the benefits outweigh the cons by a decent margin.
=3
If you're wondering "so what's up with den?"
Still fixing bugs, improving things.
One main bug I'm hunting is related to file attachments in DM (private) not doing it right (narrowed it down to a hash issue).
Aside from that, improvements related to adding years to dates here and there, moving some UI elements, etc.
right now I've added more events to be rebroadcasted on login if it fails below 3 relays, to reduce the chance of events from being deleted, and more importantly also added the same system for the members lists for a hub (blossom / hash files), since it would pretty such if you open your hub and suddenly your members list got wiped.
LiveKit now works for voice (before it was just cloudflare, but got around to self-host a livekit server and test things out)
A shitton more to share in the patch notes, and I'm hoping a new release sometime this week (hopefully tomorrow?), unless my friend gives me more things to do x3 (I mean they did, but even more x3)
This looks awesome =3
#gaming #StellarBlade
