

Oh mb never thought of that, thanks, I will


Oh mb never thought of that, thanks, I will


yjs too! the trick that worked for me was just not round-tripping yjs -> json -> db on every update, canvas state lives in leveldb as raw binary (y-leveldb), the relational db is only used to seed it when the doc is empty. after that leveldb takes over. y-indexeddb on the client for offline, works pretty well actually
on your second question yeah same struggle lol. connections are loose by default, to keep it manageable folders have a single-parent rule, no reverse refs, collapsing hides the whole subtree. frames are there too but purely visual. for kanban task relationships i just moved them out of the canvas entirely and stored them in the yjs content object, otherwise the graph gets unreadable fast
auto clustering and edge bundling are still missing tbh, when the graph grows it gets messy and right now the answer is just “use folders and frames”, not super satisfying
the freeform vs structure thing is something i keep going back and forth on, leaning toward soft constraints that nudge rather than block. curious what you’re doing on that front!


Yep! One command. It just pulls a single docker image, asks for a few env vars, then starts the app :D


Thank you!


No worries you we’re right, I wouldn’t have noticed that on my own lol, I’ll keep it in mind


Thanks, glad that you like it !


No AI, just Google Translate. I’m French, I write in my language and translate. Probably why it reads too clean :)
node-red is a flow engine, you wire up automations and walk away. ideon is a workspace you actually live in: git, notes, files, tasks, all on a spatial canvas your team navigates together :)