Merry christmas #nostr. I built a simple collaborative #voxel world-building game with #bevy and #nostr, it's called noxel. Basically each player in the world can create voxels, each voxel can have a different texture, like the bitcoin voxel ...

Codeberg.org

noxel

Collaborative voxel world building game, built with bevy and nostr.

A map of the planet's history of violence over 4000 years ...

I'm working on a multiplayer nostr game development library called disastr.

Codeberg.org

disastr

Nostr multiplayer game development toolkit

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:

crates.io: Rust Package Registry

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.

pongstr

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:

voistr: a softphone for Nostr

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: @voistr

The Samson Option makes #israel the biggest nuclear threat on earth

The Samson Option makes Israel the biggest nuclear threat on earth

Brighteon.com is a leading online free platform that empowers free speech, allowing individuals to freely share videos and express their thoughts w...

Interesting post about the problems with #vibecoding

N’s Blog

Karpathy’s ‘Vibe Coding’ Movement Considered Harmful

Last Tuesday at 1 AM, I was debugging a critical production issue in my AI dev tool. As I dug through layers of functions, I suddenly realized — ...

"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)

Réseau International - Site de réflexion et de réinformation

Ambiance «Mossad» en Israël ou la guerre des ombres devient l’apocalypse publique - Réseau International

par Phil Broq. L’arrogance militaire israélienne, alimentée par des décennies d’impunité, vient de rencontrer une réalité qu’elle n’a...

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).

Codeberg.org

paz

Nostr client based on nostralink. Uses an RDF events store.

Everything is stored as RDF triples, including followings, mutes, notes view/read status ...

nostralink is hosted on codeberg now:

Codeberg.org

nostralink

Linked data library for Nostr: store events as RDF and use SparQL queries to find nostriches in the graph maze.