• 0 Posts
  • 95 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • And for any of the people saying “he changed”.

    One of his most recent “philanthropic” ventures was to partner with Nestle (good start) to “modernize and increase yields” of the dairy industries in impoverished countries.

    The two organizations then sold modern (likely non-servicable) equipment and entrenched them in corporate supply chain systems geared towards export and making it much harder to trade locally (not sure how that part worked, but was in what I read).

    For a grand total of… 1% increased dairy yields.

    Then 3-4 years later they pulled out, leaving heavily indebted farmers without the corporate supply chains and delivery systems they were forced to switch to, and making it very difficult to switch back to the old ways of working, so they can’t sell nearly as much locally.

    Who do you think will buy up those farms when the farmers go bankrupt and have to sell ar rock bottom prices.






  • Hey, something I can maybe help with.

    Flatpak IDEs on the main system are not very useful for development. I got rid of mine entirely. I am developing firmware so it might be a bit different from your case, but what I did in have a single arch distrobox where I could install everything embedded-dev-related that had to work together (JLink, nordic tools, code-oss, etc…) on that. Then a few standalone debugging tools like STLink and Saelae logic2 could be installed to the home folder by default and Code could still find them from the distrobox (but they could be installed in the distrobox also). It doesn’t even need to have an init system, but I ran into a few problems like having to manually chmod usb devices to give STLink access. Udev rules are also hit or miss in /etc/udev/rules.d, e.g. the STM udev rules just don’t work, but nordic does.

    High storage consumption is likely negligible (or at least nitpicky) since storage is so cheap nowadays. Your SSD doesn’t care if it has 15GB or 20GB of system programs, especially when development codebases and SDKs, games, and media will likely make up 90% of space and almost never share libraries even on traditional systems.


  • That only solves maybe one of the listen problems. Whatever instance you have, you still have to get and serve media to other viewers and instances. The only problem that this solves is potentially CSAM spam/moderation.

    Let’s say it was a cell phone, it could handle maybe 2 concurrent transcoding streams before stalling out and people running into buffer times (which makes them leave).

    If every person had their own tiny, low powered servers, then you could have max like 5 concurrent transcodes on any instance in all of peertube for old laptop or desktop computers. Assuming an average of people have a 100/30Mbps connection (which is true in much of the world outside of major cities, or even lower), then that would be absolutely maxing out at 10 concurrent viewers if everyone is running AV1 compatible clients (which is not the case) and more like 6 concurrent viewers per video at h.264. Those estimates are at low bitrates also, so low quality, absolutely no slowdown from your ISP, and absolutely no other general home or work-from-home use. In reality it would be closer to 3-6 concurrent viewers per instance (not even per video)

    Still not even counting storage which is massive for anyone that creates more than a couple videos per year.

    My point is just that it is an extremely difficult and costly problem that is not as simple as “more federation” like in text and image-based social media because of the nature of video, the internet, and viral video culture. Remember, federation replicates all viewed and subscribed content on the instance (so the home instance has to serve the data and both instances have to store it)


  • Just a few thoughts as to why it hasn’t taken off:

    Video is multiple orders of magnitude more difficult and expensive to serve than text or even audio.

    • Your server needs a great upload speed which is not achievable for on-site home servers for most people in the world

    • Your server has to have at least one dedicated encoding GPU (no raspberry pis or Intel nucs if you want any meaningful traffic)

    • Your server has to have a ton of storage, especially if you allow 4k content to be uploaded, which while much cheaper than before, is still expensive. Here in the EU, reliable storage is around 300€/12TB for drives, which fills up very fast with 4k videos or if you try to store different resolutions to reduce transcoded loads.

    • Letting random people upload video onto your instance is significantly harder to moderate than text or photos. Like think of the CSAM spam that was on Lemmy when it started in taking many new users…

    • The power usage (and bill) of the server will also be much higher than without peertube because of constant transcoding

    The cost, both financial and server taxation-wise is simply too great for me, and many others to setup a peertube instance.

    Regardless of how easy it is for people to create on peertube, someone has to bear the cost of hosting it. That is cheap-ish for Lemmy or mastodon, but there is a reason YouTube was a loss leader for a long time for google, and many streaming services restrict 4k video.

    That isn’t even getting into compensation for the content makers.











  • That is pretty expensive nowadays, if OP wants to go that expensive, getting a mini PC with the latest intel N150. The pi 5 doesn’t even have hardware AV1 decoding. By the time you have all of the pi accessories, it is not much of a price difference, but defi itely a performance difference.

    https://amzn.eu/d/85cytyZ

    Plus you get benefits like actual storage instead of a separately bought SD card, more RAM, 2.5G ethernet, and HDMI2.1 & USB–C displayport.

    Then you slap Linux on it (and also hope that plasma bigscreen is a success in the near future) and you have a very reliable 4K HTPC that can decode anything you throw at it. It has enough horsepower to be a home server at the same time, unlike a pi while also having just a bit higher idle power usage (2W or so).