At this point it's nice hacking, but not very productive yet. It needs to become more proactive and autonomous, while being conscious of token limits, or hopefully running on decent local models soon. But I think we'll have actually useful and easy to set up agents later this year.

Encrypted media & file attachments over hashtree (nostr & blossom)

Nostr-double-ratchet ts & rust libraries and ndr command line tool: https://files.iris.to/#//nostr-double-ratchet Chat.iris.to code: https://files.iris.to/#//iris-chat No other client using it atm

They're on docker containers on a dedicated server

Pull requested to clawdbot https://github.com/moltbot/clawdbot/pull/2729

Iris has had double ratchet messaging for a long time, but trying to support multi-device made it flaky. Now I made https://chat.iris.to/ which is single device and works pretty reliably. Using it to control my clawdbots. Had to set it up because whatsapp / signal setups were such a pain. Also I didn't want to use nip04 which would reveal all our chat history if the private key was ever leaked. On command line the clawdbot uses nostr double ratchet tool ndr in rust: https://files.iris.to/#//nostr-double-ratchet And of course my clawdbots use git-remote-htree for decentralized code sharing on nost + blossom — not annoying github tokens.

I have an extension for nostr double ratchet chat that i use to control my clawdbots. Haven't pull requested yet. I use https://chat.iris.to web interface

Unfortunately no: content is encrypted by default so there's no way to tell what's in there. Limited storage quotas for free users (per user & total) and dropping least recently requested files is the best spam prevention policy I can think of. Maybe combined with IP based filtering, although that can be bypassed. I'm currently running my own cdn.iris.to (writes via upload.iris.to) which only allows encrypted binary uploads to avoid moderation issues.

can you enable binary uploads to nostr.build so it can be used with my blossom based git / github system 😇 https://files.iris.to/#//hashtree

It has no relation to radicle.xyz

You don't need to trust blossom servers, content is verified by hash. There might be direct nav problem in urls right now, working on it. In the meantime you can go to files.iris.to root and paste the url into the search input once relays have connected.