Check out The Vampire Who Couldn’t Charm the Gondolier - Manga Oneshot by WolfEn-sensei

Mangatsu

#Anime #anime-inspired #digital-comic #indie-manga #light-novel-style #Manga #romantic-comedy #Vampire #Webcomic Get #mangatsu at

Mangatsu

Announcing #Mangatsu The new decentralised web app for manga and comic enthusiasts is officially live. Built from the ground up to support creators and readers directly on open protocols. - Read seamlessly with an optimised reader screen - Integrated NWC for instant creator zaps - Decentralised media storage via Blossom - Manage your personal collection with NIP-51 library lists - Robust offline mode so you never lose your place Check it out now:

Mangatsu

#manga #comics #nostr #nwc #blossom #opensource

- #qDHT now with a simple web showcase interface....

GitHub

GitHub - imattau/qDHT: A DHT implementation of the concept derived from the Quantum Relay (Nostr)

A DHT implementation of the concept derived from the Quantum Relay (Nostr) - imattau/qDHT

#nostr #dht #quantum #dev #nostrdev

Working through a qDHT idea. It started from the quantum relay work in rely, then drifted into a DHT-style discovery model. I’m not trying to replace Mainline DHT. This is a different approach. Classic DHT: query by key → route through keyspace → find providers. qDHT: signed announcements → local neighbour-state → discover routes, replicas, or pieces. The idea is that each node only keeps a small view of the network. Those views overlap, so discovery can move through the graph without every node needing a global routing table. The quantum-inspired part comes from the relay model: local propagation using the graph Laplacian / continuous-time quantum walk idea. One useful finding from testing: direct query routing did not work well. Announcement propagation looks much more promising. Current model: - identities announce current routes - content announces hashes and piece metadata - nodes remember which neighbours exposed them to each announcement - replicas form when content is fetched - clients retrieve from nearby replicas - rejoining nodes ask neighbours for missed deltas - reputation damping reduces spam propagation The main idea is pretty simple: qDHT uses propagation history as routing state. Small local views. Overlap between them. Signed records. Demand-driven content fetch. qDHT:

GitHub

GitHub - imattau/qDHT: A DHT implementation of the concept derived from the Quantum Relay (Nostr)

A DHT implementation of the concept derived from the Quantum Relay (Nostr) - imattau/qDHT

Original relay work:

GitHub

GitHub - imattau/quantum-rely: A framework for building custom Nostr relays you can rely on. Designed for the best developer experience.

A framework for building custom Nostr relays you can rely on. Designed for the best developer experience. - imattau/quantum-rely

Trying again to see if the quantum relay announces the post...

Relay testing... wss://quantum-relay.3nostr.com

Built a quantum-inspired propagation layer for Nostr relays. The problem -> clients publish to 20 relays just to ensure reach. It's wasteful and spam hits everywhere simultaneously. The idea -> relays form a mesh and intelligently pull notes from each other. A note published to one relay can reach relays the author never knew existed. Spam from low-reputation pubkeys never propagates beyond where it was posted. The relay mesh self-organises - no central coordination, no shared blocklists. Reputation diffuses naturally across the network. Built on rely v2. Code on GitHub (quantum branch). #nostrdev #nottested #trysomethingnew

GitHub

GitHub - imattau/quantum-rely: A framework for building custom Nostr relays you can rely on. Designed for the best developer experience.

A framework for building custom Nostr relays you can rely on. Designed for the best developer experience. - imattau/quantum-rely

#Nostr-over-BT --- Terminal style!

#honeytrap - Trying again.... #nostrdev #alphasoftware

#honeytrap - a #nostr client that uses #bittorrent to assist in propagating content - taking load of relays #nostrdev #alpha

Hello World #nostrbt

take 2? trying again

Message from the CLI - hoping to see in the web client

This is from the BT client

Trying a post over #nostr-over-bt

Trying now with WebSeeding #bittorrent #nostr #notsrdec #honeytrap

Trying the P2P only version of media sharing in posts #nostr #bittorrent #honeytrap

Honeytrap

Trying some new - again. Using #bittorrent to support nostr relays...

Testing the BT uploads magnet:?xt=urn:btih:8d9bd01bfa5216e301a8e049bb2a1d8680c99d74&dn=asknostr_logo.png&tr=wss%3A%2F%2Ftracker.openwebtorrent.com&tr=wss%3A%2F%2Ftracker.btorrent.xyz&tr=wss%3A%2F%2Ftracker.files.fm%3A7073%2Fannounce&tr=wss%3A%2F%2Ftracker.fastcast.nz

Testing the new BT seeding for media magnet:?xt=urn:btih:6c0084bdd7d9d9b2861d6ee74a5163c7f36d8efe&dn=asknostr1.png&tr=wss%3A%2F%2Ftracker.openwebtorrent.com&tr=wss%3A%2F%2Ftracker.btorrent.xyz&tr=wss%3A%2F%2Ftracker.files.fm%3A7073%2Fannounce&tr=wss%3A%2F%2Ftracker.fastcast.nz