Post
Yes, that would be nice. But I don鈥檛 think anyone is holding their breath waiting for C2S to be realistically usable.
For years, we鈥檝e all just filled the gap in C2S with the Mastodon API, which isn鈥檛 great.
For the foreseeable future, we鈥檙e probably going to have a patchwork of overlapping solutions that all combine into a semi-coherent system. FEP-3b86 is one more patch in the tapestry.
Not a browser developer so my opinion is worth exactly -1..
But "Chromium" is just the rendering engine, yes? This seems like a higher level feature (not unlike custom protocol handlers) that might exist in the Chromium package, but sure seems like something a browser developer would have control over.
But again, I have zero experience here, except to say that I wouldn't wait on Vivaldi (or anyone) for us to move on this.
Just for the record dropping the open issue on the Fediverse Experience curated list where I keep track of a list of #ActivityPub C2S supporting projects and attempts. Any updates most welcome if there's stuff missing.
https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130
A space for Bonfire maintainers and contributors to communicate
