I made damus, npubs, and zaps ⚡️ bitcoin core and lightning dev. Unlicensed money transmitter
jb55 @jb55 - 1mo
My new favourite thing is john wick jiu jitsu https://youtu.be/dBm4pDL29RQ
All good points in this thread, but i’ll still take a key i control over some rando server managed by someone else. If you have lots of money tied to a key i probably wouldn’t use it in mobile apps that are hard to verify… i would read the source code and compile from source and just use notedeck. Anyone not reading the source code and compiling it themselves has to trust someone, even in the keyserver case. The server case is even harder for people because people have phones, not computers with servers. We are already lightyears ahead in comparison to legacy social media platforms and protocols, at least users have the ability to choose their risk tolerance levels with different clients. On legacy they can read your DMs and make posts on your behalf if they wanted to.
try nostur
I'll be there!
yes, eventually I'm going to add boid dynamics where it can take different shapes, as well as move toward things its referring to on screen.
fam is gone for two weeks so this is how i'm spending my sunday night. making dave into a swarm of 256 instanced cubes.
wen bithookup
swarm dave https://jb55.com/s/dave-new-2-2.mp4
dave is evolving... https://jb55.com/s/dave-new.mp4
notedeck 👀
good times
https://github.com/damus-io/notedeck/tree/master/crates/notedeck_notebook is another one I just put together
https://github.com/damus-io/notedeck/tree/master/crates/notedeck_dave is a notedeck app the demos how to make one
nice meeting you! now post some models.
i think the newer versions are a lot further, at least from testing bitchat at an event in portland recently
just need bots to ruin every poll now!
The problem is that the OS reports this as resident set usage of the process, mixed in with other non-reclaimable memory usage, so it’s very misleading. If your system started swapping you would see nostrdb memory usage go to 0
https://en.m.wikipedia.org/wiki/Page_cache#:~:text=Usually%2C%20all%20physical,free%22%20or%20%22available%22.
nostrdb effectively uses 0 memory since it is non-copy when querying. Nothing is copied into main memory, its just the page cache which the OS manages and is evictable, unlike explicitly allocated memory by processes.
i think you completely missed the point of my post. page cache is not “using” memory when it can be immediately evicted by apps allocating memory for real.