Can you provide some sources that support this claim?
raldone01
joined 1 year ago
Well the player and its controls are client side.
I think dd is the right tool for the job. Consider using pv though. It can be much much faster.
If you are on a samsung you can maybe still enable the good swipe up actions with good lock navstar. There one can enable advanced gestures. Then you can disable the app again. The old swipe settings should be back.
I tried the new ones but the swipe up ones are just way way better.
I went from DL380g6 to DL380g9 they are quite powerful for what you get. Also very noisy though. I have installed two p40s. I love it.
I have a samsung tv from 2016 and it always lags terribly when switching inputs. Sometimes the menu takes 20 seconds to load. What is it doing?
The biggest offenders for me are:
- I struggle to navigate and make out alle the controls of the settings app. Somehow finding the settings visually is very difficult.
- The new settings app is single instance. The control panel had lots of popup windows and you could open it multiple times which allowed parallel open settings windows.
It's like spectre and meltdown you also lost the advertised performance. Less performance is better than a gaping security hole or a broken chip.
Take a look at tubearchivisit. Works great and is in development.
And clearnet use is very difficult through Tor. Exit node ips are flagged and you have impossible captchas on many sites.
Unfortunate :/
And the custom Dvorak layout with the umlauts on linux?
So you would need buffer barrieres essentially.
Still user watches video. Ad avoidance skips forward to buffer barrier to play ad in the background. Streamed ad is thrown away and new buffer data is received. User does not notice if the video is long enough.
In this case the buffer limit is the metadata.