[โ€“] 12 points 10 months ago (1 child)

This seems like a silly workaround at first but it's really not. If the network is unreliable, you can't really use normal video streaming, you need to send full screenshots. Probably still a better idea to use only I-frames than a bunch of JPEGs but whatever.

But they did make some very silly mistakes. Par for the course of an AI coding company I guess.

  1. WTF are you doing with 40mbps. Tone it down to like 8.
  2. If the network is reliable but slow, just reduce bitrate and resolution. Don't use JPEGs unless packet loss is the problem.
  3. WTF are you doing using a whole game streaming server for? It's meant for LAN, with minimal latency. Just capture the screen and encode it, send via WebSockets. Moonlight is completely unnecessary.
  4. Only keep the latest frames on the server. Don't try to send them all immediately or it'll fall behind. Wait for the client to finish receiving before sending another one. This way it won't lag behind increasingly. This should have been extremely obvious.
  5. H264 is so 2003, ask the client if it supports AV1 or HEVC then use that, more data for free.
  6. Use WebTransport when available, it's basically made for live streaming
  7. Why are you running a screenshot tool in terminal then grabbing the jpg... Unnecessary file overhead & dependency

I probably missed some but even for an AI company this is really bad

  • source
  • [โ€“] 1 point 10 months ago* (last edited 10 months ago) (3 children)

    The modern method is more efficient if your network is reliable.

    Modern: I-frame (screenshot) then a bunch of P-frames (send only what changed). If a frame gets lost, the following frames aren't really usable, frozen until next I-frame Old: Send only full screenshots. Each frame has all the data, so losing one doesn't matter.

  • source
  • parent
  • context
  • [โ€“] 23 points 11 months ago (7 children)

    The average person is not going to sign up and pay for 10 different things, even if it's slightly more private. Proton is similar to Google in that it's free and has a lot of things with one account, but vastly different in the way the data is handled, probably the most meaningful difference. I mean the best thing you can do is self host but it's obviously not something everyone can or wants to do. So there's nothing wrong with taking the next best thing.

  • source
  • [โ€“] 12 points 11 months ago

    Use the OS battery charge limiter (or Magisk "ACC" module). Most phones have the capability to bypass the battery and draw from the adapter. Keep it cool and at 60%, and it won't get spicy. Heat, cycles, and high/low voltages kill batteries, so by avoiding all of those they'll stay unspicy.

  • source
  • parent
  • context
  • [โ€“] 5 points 11 months ago (1 child)

    If there's a market for it, replacements will be made. You can buy a replacement PS5 battery for $5. You can also buy a iPhone 4 battery (still). LiPos are quite easy to make (geopolitics aside) so making one that fits is not hard at all.

    The PS5 battery has a plug, if the Steam Controller is like that (probably is), the only tool required is a screwdriver, which seems like a great tradeoff to replace the battery every 5+ years instead of every week or two, and being able to recharge it easily and quickly.

    Worst case scenario you have to use a generic battery that is about the right size instead of a perfect fit. Maybe a little less battery life but it's still more than enough anyway.

  • source
  • parent
  • context
  • view more: next โ€บ