Getting started with PeerTube
I doubt YouTube would ever have been successful if it had required this level of explanation.
This feels like a guide for an early podcast player, the way you connect to different instances and their channels using urls. Kinda refreshing actually.
peertube worked fine the few times I tried it, it's not in my mind when I want to see videos but I have to say it never felt a disappointment.. pretty neat for such an effort
My guess is that none of these things (including things like Mastadon) will become very popular. Then, one day, Amazon will create an AWS instance for it, and popularity will skyrocket.
And no, I’m not being sarcastic. I love the idea, but can’t for the life of me think what it will take to make something like this truly popular. (Though I wish I could!)
> I have a lot to say because I have a lot to think about.
Oh boy.
OK. So PeerTube doesn't actually host anything, right? You need a streaming server to publish. Maybe someone will let you have space and bandwidth on theirs. PeerTube is just the lookup system. Is that right?
PeerTube is very exciting and I've been thinking about running an instance. Only showstopper for me atm is lack of live streaming support, which admittedly is difficult to figure out.
I honestly think that article 11 and 13 will grow more decentralized options. Peertube is only federated, so it won't benefit as much as it could, but it will still help. If the platform is responsible for copyright, then it will definitely be easier to just burn that server and then spin up a new one. Just my 2 cents
How little empathy do you have to have to think anyone wants to watch or upload videos on a system so complex.
https://github.com/Chocobozzz/PeerTube
License is AGPL v3.0...
tldrlegal shows us this
https://tldrlegal.com/license/gnu-affero-general-public-lice...
Sadly all of those decentralized / federated app all have this same accessibility issue.
Maybe there is some sort of business case, or at least some preliminary solution to get there, that offers a middle ground between "you're only the customer of our SaaS" and "you have to be your own IT department"? something like a standardized cloud-ready deployment, where instead of only d/l the server side app, the site also points you to the cloud providers that also support that app (or this standard) so that you're just 3 clicks away from running your own instance.
That'd be nice, not sure it would pay for the team developing that standard though.