@noffle I don't know, but I suspect it doesn't. The protocol is a line oriented one over HTTP and is actually only HTTP, the SSL part means have a proxy in between to handle crypto and let fossil receive plain old HTTP, which is kinda cheating but works very well. I can see it two paths for implementation of some interoperability with Fossil and SSB:
Bridging HTTP to SSB, not unlike blob serving is done. In which an sbot plugin exchanges the needed HTTP requests with a fossil client but would probably require reimplementing large portions of fossil.
By going from fossil to git and then to git-ssb as described in this guide for synchronizing fossil with git. It sounds quite hackish but it might actually work and require minimal plumbing. The advantage over git would be the included ticketing, wiki and site system.
Still, the main advantage for me is the benefit from storing things in SQLite. Repos are a single file, easy to transport and safe keep.
Still, all the above would be opaque in the feed, all the fossil stuff would be masked into git deltas that are not useful to the other SSB applications, I mean that even though fossil has wiki and tickets, that data would only be visible to the user after a repo is reassembled from its git deltas and checked out from fossil cli. I don't know if that is what we're aiming for.
We might want ticketing, wiki and web, to be visible in the feed in a usable way so that apps such as patchwork, patchbay and future hypothetical patchhub can see them. We might be better served by studying fossil and then replicating part of it in our ecosystem while keeping git-ssb
as the file repository.
As some additional info about some fossil qualities I like, check out how easy it is to do complex queries (which we don't do by hand but fossil does on its own, there is more info about Fossil Vs Git from this page, just be aware that some points there are controversial and the author is biased, and don't forget to check this really nice page with reprt examples which provides quite nice project awareness for contributors.