Important systems to decentralize 👍 many things have secure private messages as a prerequisite — still working on it!
🔔 This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
Edit
Important systems to decentralize 👍 many things have secure private messages as a prerequisite — still working on it!
This is not replacing Noise, but NIP-17 gift wraps. My PR was poorly titled, changed to "Add double-ratchet encryption for Nostr relay DMs".
Nostr double ratchet pull requests for Bitchat. Forward secrecy enables disappearing messages feature: past messages on relays can't be decrypted anymore after key rotation. Also future messages stay safe even if one key is compromised. I don't know how mergeable it is in its current form, but I've tested it to work between real Mac and Android devices. https://github.com/permissionlesstech/bitchat/pull/1107 https://github.com/permissionlesstech/bitchat-android/pull/697
Artists claim is an interesting problem looking for a solution. I'm hoping that could somehow work via social graph attestations. Artists would be represented by a UUID in the catalog, which would be connected to an npub by users in your social graph, and the npub itself. Similarly the npub-uuid link can be revoked if keys are lost, band members change etc. It's useful if different catalogs converge on same UUIDs, but they can be also linked to the same entity. The same arrangement would of course work for npub attestation / revocation in general, allow targeting of reviews for entities that are not on Nostr and much more.
You can add any audio files. Someone had the 100M song dataset...
Hmm, that's for webrtc peerfinding and signaling. I could make it stop asking after a reject, and maybe display toast notification about how to re-enable.
This has its own kind of data structure
https://audio.iris.to/#//metal-catalog Spotify clone on nostr / blossom / hashtree. Data is loaded from peers over webrtc even if you disable the blossom servers. Hashtree is a nostr native "IPFS lite", basically just blossom + directories and file chunking. Everything is content hash key encrypted by default, which is nice for blossom server admins. More: https://hashtree.cc/#/dev Btree indexes on hashtree enable large, searchable decentralized databases that can be used for all kinds of "platform" applications. Hashtree indexes can be queried a bit like nostr relays, but they're not tied to any IP address, domain name or host. You can sync them over any transport and search offline. Content-addressed indexes are transparent: you can verify that you see the same search results as others and aren't shadowbanned. You can easily fork the large indexes (such as audio.iris.to catalogs) and add your own results into them, even in the browser.
Awesome! I've got to fix the links on hashtree.cc though. Here's a version that works https://enshittifier.iris.to/#/song//enya-only-tjme-pt-2-the-sequel-h83fch
Even un-enshittified, midis are a great way to kill your love of music
I may have created the killer app of Nostr: MIDI Enshittifer Also demonstrating Iris Sites, a way to easily deploy websites over nostr / blossom / hashtree. https://63dvmlmvh6sxd65q7abane2j23fl4e7hmub4lwdjvl6vwmzlobda.hashtree.cc/#//enshittifier/index.html
It works just fine. You just need multiple remotes and sync between them, instead of everyone pushing to the same remote.
It should work now. Integrated the debugging improvements. Thanks for testing!
The url https://upload.iris.to//releases%2Fhashtree/latest/install.sh is working for me. I wonder if it could be different handling of the url encoding. What os did you run it on?