Do you have any experience with https://mullvad.net/ ? #vpn
Started a new hobby project: a microkernel OS in Rust! Zero kernel experience, no Rust skills yet. What's the worst that could happen? 😜 #OSDev #RustLang
Today, we’re officially introducing Kagi News: a once-a-day press review that cuts through the noise. Global stories, community-curated sources, and zero tracking. News the way it should be:
https://blog.kagi.com/kagi-news
https://blossom.primal.net/89e06ad409315a75a2535587e9ce1a445f09982ee9637113a67b943d8027c028.mp4
I like it so far. Web version is blazing fast, I haven't tested mobile apps.
Definitely funeral 😉
Quick demo of Samiz + Citrine + Jumble working with 3 phones sharing notes via BLE: https://cdn.azzamo.net/5e62d56025ca396de01187e098fa67c7db3643da1f23a2bb8f73406e9a6e3868.mp4
Great idea. I would also think about building soft for small BLE devices like those with ESP32 that can act as repeater.
BTW, I'm on it now. Except spam protection I'm also working on other security layers. Key thing will be to keep this in balance with still good relay performance. Definitely EPS only for checking events end rejecting them if malicious it's much higher than for processing valid events through all step until it touches DB.
Can't we implement on relay level spam protection to filter content at least based on keywords? I know it's not ideal but part of spam could be rejected before it touch database.
How to properly measure EPS for #nostr #relay ? Is it amount of events per second processed (processed and stored in db + processed and rejected i.e. due to detected spam or DDoS) or just event processed and stored in db?
Wouldn't be better to have spam protection on relay level?
How to unsee this?
I've tried many models but so far in terms of code quality I'm happy the most with Grok Code Fast 1.
I wrote a basic softphone for #nostr (it uses nostr relays for #webrtc signaling) called #voistr: https://voistr.codeberg.page/
More features are planned, chat and maybe video calls. Both the signaling exchange and the voistr protocol use NIP-44 encrypted events. Follow voistr here: nostr:npub1lcfnjgme4s9whl6n4fym0ft034rdmghahal7jzg7zw35w8f6dq2s2kn6vm
Sounds like an interesting project. Need to test it!