semisol @semisol - 21h
I am not sure whether to release the event cannon, or Nostr Agents The event cannon broadcasts all your events to all relays including old events Nostr Agents would be a platform for JS-powered agents that can fully interact with Nostr and possibly even self-fund
cc nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve might be interesting to you
node @node - 21h
prioritization
tanel - 21h
nostrobots wen
Would also be able to interact with the nostr.land aggregator and a secure key storage module.
vinney @vinney - 21h
negentropy would make way for p2p relays, event cannon would not, right?
Nostragents first. Nostr land already broadcasts new events (or will soon). More diverse set of features
This runs on CF Workers currently as the primary purpose is event delivery for Nostr.land. Will be open source and will offer a single-binary selfhostable variant, plus paid API for who don’t want to bother with hosting as well.
putting a slightly finer point on it: My client connects to ONE relay, publishes notes there, gets notes from there. That relay talks p2p to whatever other relays I want it to in order to sync and broadcast notes around.
That would be pretty amazing. Less bandwidth and less battery usage
you just described my plan with nostr.land ser
event cannon is only the write part, it could broadcast to a lot of relays and also support outbox at the same time. you tell it what to do and it just does it
Apparently soon ™
NFDB is also designed to allow microrelays, so you can build your own personal index from p2p syncing with peers, and they can too
is event cannon client side or relay side? my interest in this angle is keeping the client very performant and simple (connect to your one master personal relay). ideally, your relay would **serve** yourself the client code, as well. so it's a full-stack p2p nostr in a single box.
you looking for collaborators? this is my holy grail / maybe-insane goal for nostr.
cannon is relay side, meant to be run on either a server (which could be something at home) or serverless platform (higher ratelimits from different IPs)
I just bought a month of service to experiment !
hell yea
could. nostr.land is a commercial service (and it costs money to run), but I am also planning on having OSS for parts, and standardized APIs for these
