I live in the town and met the dude he's ment to be training he seemed like more of a musician and in all my last 20 years in christchurch have not once seen the actual wizard in the square
I'm reasonably confident that the protocol I was working with was json over websocket https://openwebtorrent.com/ tracker
this was a few months ago now so peertube could be running something different
So each peertube instance runs its own openwebtorrent compatible tracker, which then has its own protocol inforced at the wire level, compared to when i looked at the other openwebtorrent implementations depending on the server didn't enforce the wire format and you could send json over the wire, the trackers seemed to just be a sort of pubsub system where announces would get resent to other connected clients under the same infohash or whatever they used
I'm not sure webtorrent have a way to do peer exchange without centralised trackers like e.g Bittorrents PEX does, so if the core websocket trackers go down, are peers still able to share lists of known peers with each other or is the peer discovery centralised to the webtorrent/websocket trackers?
Last time I checked the way that webtorrent/peertube queries for peers watching same video is centralised over websockets to a a select few webtorrent trackers, I think theirs only 2 or 3 running, meaning if you wanted to take down peertubes p2p functionality all you would have to hit would be their webtorrent trackers with a ddos and the platform would go down, I'm not 100% about sibil protections but I do know that peertubes webtorrent trackers verify the structure of an announce, and if it is in invalid format bans you from the tracker, compared to the other webtorrent trackers which are more happy to accept something less strict as an announce