However why do you need persistent connections ? I am thinking that the growing rate of the connections should be very low as the instances increase, given that the queries are quick.
I haven't used persistent connections although I have been tempted in the past. I believe, if you haven't used it before, it might come with more trouble than it solves.
As an alternative I could propose using amphp (or maybe react PHP) which will let you handle a pool of connections in a single long running process. But it's a bigger change really, the more I think of it.
So as I understand from your post here, every piece of software is responsible to define its relationship with a different kind of software while all use ActivityPub underneath?
I have been reading on the ActivityPub protocol and trying to understand these days.
I am really new here but if it adds to anything I fully agree with any direction that will or reasonably should, lead to everyone here having a better space.
Also want to add that I do appreciate the effort that the mods/admins are putting into it.
I've been working on a small TUI framework and sound was something I was wondering if possible to be done. My code is in PHP though not Rust. So this might give me some insight on how capturing works (I have no idea how sound works) but what I wanted to create is the capability (more or less) that for example TIC-80 provides where you have input from sound and make graphics respond to it (see Lovebyte jam sessions on youtube for example).
I really like the detail on the non filled ones where the last one on top might not always be a full one.
I thought the ActivityPub IS that open standard