42
Version 5.2 of PeerTube is out! | JoinPeerTube (joinpeertube.org)
submitted 2 years ago by 0x815@feddit.de to c/technology@beehaw.org
17 comments fedilink hide all child comments

Cheers!

top 14 comments
sorted by: hot top controversial new old
[-] asjmcguire@kbin.social 16 points 2 years ago

Next step - should be a server that simply coordinates video transcoding, and users can run an application on their computer which will do the transcoding when it's idle and deliver the transcoded video back to the server. Like the rest of the Fediverse, make the community actually part of the community. I'm sure many of us would be happy to donate spare CPU time.

[-] i_am_not_a_robot@discuss.tchncs.de 7 points 2 years ago

It's a nice idea but it sounds easily to abuse.

[-] bumbly@readit.buzz 2 points 2 years ago

Not if you have a consensus algorithm and the machines all return a hash of the video they encoded. If they build IPFS support then the encoding machine could upload the file there, return the IPFS content address and the server can then pick an agreed upon address.

[-] asjmcguire@kbin.social 1 points 2 years ago

Shouldn't fundamentally be much different to seti@home, boinc etc. Break a video into chunks, and let multiple computers encode a chunk each. If the chunks were small enough, most people probably wouldn't even realise their computer had just encoded a chunk of video

[-] kionite231@lemmy.ca 0 points 2 years ago

How? Can you explain

[-] xthexder@beehaw.org 2 points 2 years ago

I'm not OP, but if transcoding is happening on user CPUs, it's theoretically possible to modify or inject stuff into the transcoded video. There'd need to be some way of validating a transcode matches the original, which is non-trivial.
A consensus algorithm could work, but that would massively increase the required compute. I'm not even sure things like NVENC vs CPU ffmpeg are deterministic in how tbey compress video. Different encoders could very likely end up with visually identical transcodes, but the hashes wouldn't always match.
Maybe someone else has a better idea for validating transcodes?

[-] TheTrueLinuxDev@beehaw.org 2 points 2 years ago

Sometime it's better to let it happen and let the user find out the person who mis-transcode video maliciously and get that malicious person banned from the instance. Many instances are invite-only, so it works out in a way that the benefit outweigh the risk.

[-] i_am_not_a_robot@discuss.tchncs.de 3 points 2 years ago

The average YouTube user is not going to understand any of that. If they're watching a video and something unexpected comes up in the video, they're going to blame the person who uploaded the video.

[-] TheTrueLinuxDev@beehaw.org 1 points 2 years ago* (last edited 2 years ago)

I suppose although the documentation does point it out that the offender can modify such content with ease.

For live transcoding, I would suggest the broadcaster to purchase a good GPU and have it transcode the broadcast. While they are trying to suggest CPU-based solution, i would argue that they should explore the GPU based solution which can be much better optimized for this scenario.

Reference on Support Matrix for Encoding/Decoding support on GPU for Nvidia Information for Transcoding on Nvidia GPU

[-] narc0tic_bird@beehaw.org 8 points 2 years ago

Pretty cool. That means people could also donate CPU time to instances they love.

[-] Siathes@lemmy.dbzer0.com 6 points 2 years ago

how do we federate (connect) to peertube instances from lemmy? does it show up on our lemmy feeds?

[-] MeowdyPardner@kbin.social 3 points 2 years ago

I think you can follow a channel and see videos as posts. Then replying to the post shows up as a federated comment. I haven't tried it though.

[-] JayDurst@beehaw.org 1 points 2 years ago

I tried it and it works just fine!

[-] Dee_Imaginarium@beehaw.org 5 points 2 years ago

Very cool, can't wait to see where this goes. It'll likely never be a direct replacement of YouTube but it's great to have alternatives and an alternative on the fediverse no less!

load more comments
view more: next ›
this post was submitted on 21 Jun 2023
42 points (100.0% liked)

Technology

37804 readers
405 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org