Welcome 🙂 We hope you continue enjoying it!

Proof ?

Edit: none, it seems

I’m not sure you’re aware, but peertube also federates videos. Instances can choose to federate the metadata and the data too. That means if one instance goes down, there’s a chance the data will be available on another peertube instance. Furthermore, as I said, using webtorrents will allow alternative clients (like qBittorrent) to store copies of the data. That’s why I brought up (maybe in another comment) tools written around that which could, independently or with coordination from an instance, download and see the X “hottest” videos of the day, most viewed videos of interval Y, or whatever else.

Regarding torrents solving the storage problem: it’s possible. The main instance where the video is uploaded to will still have to keep the primary copy of the video and all the different resolutions. You can’t just upload the video, make a torrent, and then delete the content. It will have to be distributed to be kept redundant. And if the primary copy is deleted without any redundancy, you will have a problem. You could hope that all federated instances copy the data and that many do-gooders (probably archivists) decide to seed every video of every instance out there, but I think it’s more likely that popular videos will be seeded and obscure videos only exist once on one instance.

One could imagine the main instance deleting the content after a certain seed threshold has been reached (e.g 500 seeders have 100% of the file), but that could be easily abused: somebody wants to take down a video and controls a few hundred IPs --> tell the instance you have 100% of the file, instance deletes video --> video is gone. So, again, I don’t think it solves the storage problem. Federation could though. If instances have a max number of users they accept, users would have to spread out across instances and thus distribute the storage requirements.

In any case, webtorrents would improve the current situation. Right now in order to duplicate a video and contribute bandwidth, you must run an entire peertube instance. It’s simply the “easiest” way to do so. Nobody, to my knowledge, has successfully written a minimal client that just communicates with instances and downloads, then hosts the video files and makes itself aware to instances as another instance (though stripped down).
Webtorrents would allow somebody to just grab the torrent file (or magnet link) paste it into qbittorrent, and be part of the swarm without having to go through weird hoops or run an entire instance.

All on Github, yay!

That is indeed simpler 🤣 Thanks for explaining.

Is this in the US or Canada? Must be US, right? It seems like more than just big tech. Has this Ben character thought of uploading to peertube? Then random blurring and take downs wouldn’t happen.

Get yourself nixos, get omarchy-nix and configure on top of that. It seems like it’d be more stable anyway.

Torrents alleviate the distribution problem, not the storage problem. You can’t tell me that distribution isn’t a problem. A few federated instances won’t be able to scale viewership if it goes into 1M concurrent views or so. Hell, even 100 or 1k streaming a 1080p video can easily bring a server to its knees.

There have been proposals to use IPFS for storage, but frankly, IPFS is nowhere near ready for production usage.

Webtorrents are torrents that run in the browser. From my understanding, they have all the features of torrents except that they run in WebRTC (because browsers don’t directly speak torrent). If they do, then requesting specific chunks of torrents should be possible. Therefore, it should be possible to have torrents by resolution.

There could be preferences per user / per session to allow customisation of the seeding preferences with reasonable defaults depending on network speed.

As for hard drive space, it probably won’t be an issue. Users can selectively seed what they want by using qBittorrent which supports WebTorrent. If there were thus a webtorrent solution, tools could also be written to download and seed videos depending on preferences e.g most watched videos, least watched videos, hottest videos in last 24 hours, maybe even a protocol where the server dynamically requests seeders depending on which video is being streamed by users, and so on and so forth.

WebTorrents in peertube could really change the video distribution game altogether.

Pro: it’s GLOSS - Gratis Libre OSS.

Con: it’s run terribly. The Linux foundation could be doing a much better job. 1-2% of its funding go into the linux kernel.

Straight to jail.

As in email? You must be joking. They are the worst. Even for encryption they are bad. They leak metadata like crazy.

Matrix is a step up. Unless that’s what you mean by “mail server”.

Could you just tell us what this is about? I started watching the video but am 100% lost. Nowhere is anything explained. We’re just dropped into something.

I would have appreciated some of my creators at least copying their releases but nobody does.

People do, you just don’t notice it because they aren’t in your sphere. And FYI it’s easy to setup. You can setup a sync on peertube with a YouTube channel and just let it get the videos forever. No maintainance is necessary. Odysee does the same thing and there ate creators on there too.

Peertube is far from perfect, I grant you that, but I use it through GrayJay ever day and do not face issues.

Seeding was a thing with webtorrent, then they defaulted to their new HLS method and it is now practically unused. You can still download the entire file via torrent on some instances.

Their problem was they needed to be able to stream chunks of the video via webtorrent and also switch between different resolutions. Supposedly that isn’t true, but I do believe it is ( I’ve seen other people talk about possible implementations). Dunno if the maintainers are actually receptive to a webtorrent HLS or DASH solution.

Could you put it on peertube please?

Thanks for having a look!

Thanks for having a look!

Servo is going he Firefox and gecko route: claim to be embeddable but only target one example browser and actually be horrible to embed anywhere else.

I hope they snap out of it because the way things are going, nobody will use servo and it will just stay an engine with an example implementation.

Move to codeberg. Sanity by obscurity. Only the really devoted go to codeberg for now.