(It’s not super obvious, especially on mobile, but once you see the site, just scroll down to see the content)

Apache Karavan: https://karavan.space/ Kaoto (Red Hat): https://kaoto.io

Both are end 2 end usable within vscode.

https://www.mashups.io

Then all those sites I used to post on stopped supporting rss one by one and finally pipes was killed off.

For a while I used a python library called riko that did the same thing as pipes without the visual editor. I have to thank it for getting me off php and into python.

https://github.com/nerevu/riko

It has the advantage of being open source, has well defined and stable APIs and a solid backend. Plus 10+ years of constant development with many learnings around how to implement flow based programming visually.

I used the Node-RED frontend to create Browser-Red[^2] which is a Node-RED that solely executes in the browser, no server required. It does not support all Node-RED functionality but gives a good feel for using Node-RED and flow based programming.

The second project with which I am using Node-RED frontend is Erlang-Red[^3] which is Node-RED with an Erlang backend. Erlang is better suited to flow based programming than NodeJS, hence this attempt to demonstrate that!

Node-RED makes slightly different assumptions than Yahoo! Pipes - input ports being the biggest: all nodes in Node-RED have either zero or one input wires, nodes in Yahoo! Pipes had multiple input wires.

A good knowledge of jQuery is required but that makes it simpler to get into the frontend code - would be my argument ;) I am happy to answer questions related to Node-RED, email in bio.

[^1]: https://nodered.org

[^2]: https://cdn.flowhub.org

[^3]: https://github.com/gorenje/erlang-red

I don't know if it was Yahoo Pipes that died, or a mainstream internet based on open protocols and standards.

We do have an answer for the "overhead scenario" though (we call it the "tutoring scenario"): rather than using a whiteboard, you point your external camera at your desk and share a piece of paper. Then you can all write on the shared surface while facing each other online.

Our original plan was to synchronize cameras with projectors and deliver a remote whiteboard-to-whiteboard experience. Tricky but we did it in lab conditions. Put it on the back burner though, given the much smaller market.

I do like the idea of facing the whiteboard and not having to turn around. I guess a simple hack for now might be to just video conference with your colleagues on your cell while the laptop/camera faces the board (and your back)? I'll play around with this.

Thanks for sharing. Please keep 'em coming!

I resisted the temptation to mention it earlier but I feel I must (if nothing else, to help with your continued exploration... and generosity of sharing your thoughts!), as it relates to this notion directly: it is, indeed, this interplay that underlies our team's product. Or, more broadly: a desire to get us (and others) back to the real world. I'm not saying that digital tools aren't useful, I'm saying that they should play a role, not all roles.

More than that: I think digital tools should carry more weight than they currently do. I'm shocked at how many latest-and-greatest tools promise me the moon if I only change all of my habits. Why can't the tool adapt to me? It's all our fault, of course, we've let this happen (both as creators and consumers).

So, with that, the next time you use your whiteboard, consider testing out our app^. Hopefully, you'll see some examples of the above motivations in action; and, if you're interested, I'll be happy to share our future plans.

^ https://sharetheboard.com -- use the free trial (not the "Tester/Free" version)

To be clear: my goal here is to facilitate your exploration. If using our app gets in the way of that (or your continued feedback), please disregard. I hope you share your reflections from your next whiteboard session either way!

An open-ended follow-up: is there any way the whiteboard could be improved upon (and/or is there a way to better incorporate it into your workflow)?

Just to make sure I understand correctly: does this mean that in all cases (whether you're presenting or viewing) you find that only one person needs to be able to write on the board?

Also, in your first comment, you wrote that digital alternatives are not the same as the real thing. In your opinion, what is the key advantage of traditional surfaces over digital tools?

Curious: * Is sharing the whiteboard via camera enough for you/your colleagues? * Are you ever the "recipient/viewer" of such a shared whiteboard or always the presenter? * (How) do you transfer your whiteboard content to other tools?