https://void.cat/d/EC9J62B4E3ZFzg1DjztNZh.webp
One last big refacto and I think I can ship my new PWA app for an open beta test
Elon Musk cures my twitter addiction
https://void.cat/d/EC9J62B4E3ZFzg1DjztNZh.webp
Rewriting Zerologin mobile app in JS (PWA)
What name should it take?
I had Zerokeeper in mind. What do you think?
I also liked "Bunker" word, but there is already nsecBunker
https://void.cat/d/EC9J62B4E3ZFzg1DjztNZh.webp
Rewriting Zerologin mobile app in JS (PWA)
What name should it take?
I had Zerokeeper in mind. What do you think?
Secure store is probably the biggest problem with PWA.
Then, performances
My project is not related to nostr directly. It’s the mobile app that keep your private key (bip39) safe.
The only thing I’m worried about is how to securely store private key in PWA. Native apps have access to the device secure store. I’m not sure a PWA can do that.
Any advice? I’m also interested for my own Zerologin mobile app.
💣💥 STOP CARPET BOMBING YOUR MOBILE DATA
Coracle 0.2.20 is released — and it's kind of a big deal. https://app.coracle.social is now the least bandwidth-intensive pure Nostr client, with a ~90% reduction in network usage!
TLDR; this feature is opt-in for now, to enable it go to Settings, and enter "wss://multiplextr.coracle.social" as your "Multiplextr URL".
How'd I do it? I created a relay proxy called "multiplextr", inspired by https://github.com/Dolu89/nostr-proxy, but instead of setting relays up-front, I wrapped the Nostr protocol to allow clients to specify which relay to talk to on every request.
You can check out the source code and self-host the library using this link: https://github.com/coracle-social/multiplextr. If you're a dev and want to add client support for multiplextr, https://github.com/coracle-social/paravel might be of use.
Full changelog for 0.2.20:
- [x] Re-write pool to use paravel
- [x] Add support for multiplextr
- [x] Fix retrieving old chat/DM messages
- [x] Disable self-zap
2 words: Awesome
Ok it’s only one.
I’m happy to see my project inspiring new ones, great job! I like your proposition more than my current proxy
What would be data source? Relays are supposed to search in their DB. If your relay only does NIP-50, you shouldn't have any data (or you save events from other relays)
I forgot one thing in the initial message.
Maybe you didn't had common relay with me in snort and nostrgram?
Astral is back on track! #[0] did it again! https://astral.ninja is blazing fast now!
Actually I failed to find #[1] in both snort and nostrgram, so I tried Astral and not only did it work instantly there, all the rest is snappy, too! 🤞
Shit, I answered and event has not be saved...
I was saying something like this:
Why me? 😁
Default relays configuration in client is bad according to me.
Clients should read NIP 65 instead of proposing a list of relays for existing users.
It could use Nostr proxy (https://github.com/Dolu89/nostr-proxy) to check events from a large number of relays
To go further, you can later make a mobile app that can send push notification instead of notification in telegram and other.
Or a web page sending the new web push notifications from Apple
You want a Nostr project idea for Bolt.fun tournament?
Create a server that observes events destined to a pubkey (notifications, DM, answers, etc) and send a notification to telegram/discord/any other configured services saying "You got a new DM from XXX" or "XXX answered you: *message content*" etc.
It can be a SAAS or a self host service (but please, make it easy to host)
I'm not sure, I didn't check how it was working. I don't have so much time right now.
But calm down guys! I'm coming soon with a login spec + PoC
I’m working on it. The mobile app is difficult to build for me. I got some issues
It was supported at the beginning of Ligess, but when I switched to Una, it has been deleted.
It can be fast to add LNBits in Una if someone want it. There is still some examples in some old commits on Ligess
I never lost my follow list, it's strange. What was your actions for losing it?
No you can't know the pubkey from a REQ, that's why NIP 42 was perfect... but not implemented anywhere