cipres

I'm working on a multiplayer nostr game development library called disastr. https://codeberg.org/disastr/disastr It is based on Bevy, a game engine written in Rust. Nostr relays are used to establish webrtc connections between the players. Rollback netcode (with ggrs: https://crates.io/crates/ggrs) is used by default. Games are deployed on the web (WebAssembly). The idea is to make it easy to develop multiplayer nostr games without having to worry about identity management, networking, lag issues, and focus on writing the game instead. There's a demo here with pongstr, a multiplayer pong game. https://pongstr.codeberg.page/

voistr (nostr softphone) now supports (encrypted) file transfers between peers. Private filesharing between nostr users will be useful i think. Really enjoy working on this project 🔥

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

The Samson Option makes #israel the biggest nuclear threat on earth https://www.brighteon.com/58396053-4d0e-4080-8124-e45bfc59be4f

Interesting post about the problems with #vibecoding https://nmn.gl/blog/dangers-vibe-coding "Technical debt compounds exponentially when you don’t understand your code. Each “vibed” solution becomes a black box, and these black boxes multiply. Soon, you’re building on top of foundations you don’t comprehend."

"Accepting this initiative (Iran's proposal of the creation of a denuclearized zone in the middle east) would open the gates of international inspections and reveal what everyones suspects. That Israel has nuclear weapons and has no intention of abandoning them. In other words, Israel doesn't want to eliminate the nuclear threat in the region, it wants to remain THE ONLY nuclear threat in the region." Excellent article (in French) https://reseauinternational.net/ambiance-mossad-en-israel-ou-la-guerre-des-ombres-devient-lapocalypse-publique/ on #israhell 's self-destruction.

I think that nostr's most problematic technical flaw is that the "content" field in an event is a string, and not an object. Really bugs me. It's a serious limitation, and embedding stringified JSON like it's done for kind 0 events is inferior to having a native JSON object. I don't see any justification for using a simple string (although, sure, it makes things easy for simple events like short notes and reactions). NIP-68 (picture events) really highlights this problem with these questionable "imeta" tags. Feels like the authors were like "hey where should we put this stuff ?". If "content" was an object, the content would contain a list of objects containing the url and dimension for each picture ... Is each picture's metadata stored in a imeta tag so that it can be queried with relay filters ? (like on the picture's "alt" description). Nevermind though, i really like #nostr.

I've been working on a nostr client (with egui and nostralink) that stores events as linked data (in an RDF graph). https://codeberg.org/nostralink/paz Everything is stored as RDF triples, including followings, mutes, notes view/read status ...

nostralink is hosted on codeberg now: https://codeberg.org/nostralink/nostralink

Clif High: Secrets Revealed - Black Money Machines. Pretty crazy. https://clifhigh.substack.com/p/secrets-revealed-black-money-machines