• 1 Post
  • 11 Comments
Joined 5 months ago
cake
Cake day: May 28th, 2024

help-circle
  • There are sections of both the right and the left that have anti-authoritarian tendancies.

    The libertarian right tends to view things purely in terms of government over reach, whilst the left tends to view things in terms of the power of capital.

    Leftists saw Facebook pushing propaganda for the highest bidder, Reddit trying to be safe to sell to investors and twitter basically becoming a project to reflect Elon Musk’s personal opinions.

    Out of that came a bunch of attempts at creating new social networks. The right wing attempts were not cognisant that the aforementioned were the natural result of trying to get rich off it, while the left attempted to make it impossible to get into that position.









  • I don’t know what that post is about. It’s not possible to change the contents of a torrent. The torrent file itself is a list of checksums which validate byte ranges within the files being downloaded. If a client downloads a poisoned piece, it discards it and deprioritises the seed it got it from. Perhaps they’re transcoding a file, whilst still seeding the original.

    Torrents can work as a CDN for static files, because the downloader has to validate that the file is the same one as on the server using the checksums in the torrent file.




  • I think something like peertube would be a good solution for media, but there’s obstacles to getting it deployed in terms of adoption.

    The player is quite mature and does everything you could want. For servers it saves resources by being peer to peer using webRTC. For clients it handles graceful degradation and redundancy.

    A way it could be implemented for other drivers servers could go like this…

    I upload a video to Lemmy. My Lemmy instance forwards that video to peertube. Peertube processes the video and releases it as unlisted. Peertube sends the URL back to my Lemmy instance. Lemmy publishes my post with the peertube player iframe as a video.

    The issues with this are getting app developers and instance owners to adopt the changes and getting users to understand the implications of the P2P aspect.