ahoy! [[agora server]] and [[agora bridge]] are both mostly python (with some typescript thrown in), but the idea behind the Agora design is that integrations should be doable relatively independently of these codebases.
the TLDR for simple one-way syncing (meaning the garden -> agora direction, no agora -> garden updates): you write self-contained code in any language that dumps stuff to disk locally from a remote source, you got an [[agora bridge]].
Oh yeah, I’ve been dealing with facets while writing the Agora Bluesky bot! Available know at [[agora bridge]]. I’m into that [[pfrazee]] has been doing, there’s some notes from an old meeting with him at his node IIUC.
ahoy! yeah, so I went through the internal process to retain copyright on the Agora as a side project and I didn’t get it. so all code (repos [[agora server]], [[agora bridge]]) has Google copyright notices.
IIUC it doesn’t make a difference as I don’t personally care about copyright. it only affects contributors as they need to sign a [[cla]] (one time only) to contribute to [[agora server]] or [[agora bridge]].
Oh! Definitely a bug, thanks for reporting. I probably need to work on the [[agora bridge]] codebase, it’s essentially running pretty much the first code I wrote and it doesn’t manage any error conditions very well. Will look into this before work and report back!
by this I mean: as far as I can tell the only outcome from Google holding copyright for the Agora code ([[agora server]], [[agora bridge]]) is that 1. they choose the license, 2. they choose where the primary repos are to be hosted, 3. they require me to check for a signed [[cla]] before accepting contributions.
this is now fixed and I’m happier :) this also let me realize I need to handle several more interesting cases in [[agora bridge]]. thank you for the report protopian !