Yggdrasil in the browser? Come on.

please fill an issue on the forge at https://framagit.org/framasoft/mobilizon/-/issues

Done! https://framagit.org/framasoft/mobilizon/-/issues/420

There is https://videos.lecygnenoir.info/about - you can contact him on https://miaou.drycat.fr/@lecygnenoirgame

Not sure he still has slots open though

I'll check it out.

Seems to be a bit french though for the moment and I'm not that well spoken in french :)

That brings another thing to mind, I tend to output stuff from Kdenlive with CRF 12 which results in quite high bitrate for 1080p (~25 mbit). Youtube just eats up the video files and transcodes them to all kinds of resolutions, but it also trashes the quality.

I wonder how peertube deals with that. Guess I can set up a local instance and test a bit first :)

You can also deactivate WebRTC and get a direct HTTP streaming fallback.

Technically it's to provide an opt-out switch in the interface. It's being developped and will land in the stable.

This shouldn't be an opt out, it should be the default. Most won't understand the ramifications of not opting out.

Breaks the distribution and cost model. You either need to join the swarm or pay to watch the video from a CDN. There is a cost to deliver bits, it's just been hidden from you by corporations subsidizing it. Therefore, it can't be default (although a modal could be provided that informed you prior to streaming and gave you the chance to bail out).

ActivityPub defines federation messages server to server and client to server. It is not a protocol per se, and rather a message exchange standard, which could perfectly be used only between servers, as is the case with federation of videos between PeerTube instances, and more recently for video comment feeds, that can interact with the larger fediverse (Hubzilla and Mastodon so far were tested).

In no way it defines how you access media. That is defined by the use of WebRTC, which is supported by a growing number of browsers, and anyway provides a fallback to direct streaming (HTTP), so that any browser can interact.

> and anyway provides a fallback to direct streaming (HTTP), so that any browser can interact.

Ah, that's awesome. That definitely assuages my fears somewhat.

> [ActivityPub] In no way it defines how you access media.

ActivityStreams (which ActivityPub builds on) does define an attachment property for messages [1]. Is this not a standard mechanism for clients to access ActivityPub media (via the attachment's type and url)?

[1] https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attach...

It is, but I don't see how web browsers would need to interact directly with ActivityPub. That's just a way to settle on a json structure everyone will be using in their web application (that acts as AP client), as is the case in Mastodon.

Here with PeerTube the client interface doesn't interact with AP to watch videos or get them. It just requests the list directly to the server.