

Sorry, when crossposting I should have edited the title to be better one than the title used in the OP and in the article itself.
Flexitarian bicycle commuter (he/him) from the Netherlands.
My Pixelfed account on Pixey.
Sorry, when crossposting I should have edited the title to be better one than the title used in the OP and in the article itself.
The Guardian cannot spell “Mastodon”, it seems from this “article”.
I am running mostly Firefox or Librewolf on Linux these days, but I do not remember having to enable it. Not all of my systems support accelerating AV1 in their hardware, but they do play at 1080p (but with framedrops once above 30fps on the unaccelerated computer). But yeah, I do hope YT keeps VP9 around because of the acceleration.
I mean, given that many devices do not support accelerating it, it is in practice “hard to accelerate” unless you add a new gfx card or buy a new device.
I may not have worded it optimally (2L speaker), but I am sure it was fairly clear what I meant. 🙂
For AV1 that could still be okay, lol. It would be kind of meh for e.g. H264 but YT does not even use that anymore AFAIK.
I can only imagine that they (OP) set quality settings on [auto]. That way they might have YT constantly lowering bitrates/resolution. I do not have any issues either, but I use fixed quality settings.
Youtube pushes the AV1 “format” heavily these days which is hard to decode using hardware acceleration, given that a lot of devices still out there do not support that.
You forgot about ditching more of the chipset etc. in favour of integrating everything into the CPU die.
Some SBCs only boot from said SD card though, while some do support more robust media. However, too many images are presuming you boot from SD which is a pita.
With or without Das Uboot, they still rely on board specific firmware (even Uboot is customised for many boards to make it work). OSes that state they do support aarch64, often require to have UEFI on your system so no way they are gonna boot on e.g. your Raspberry Pi.
Add to that, that is unlikely that browsers compiled for arm64 will have feature parity with their x86-64 counterparts. Goodbye Digitale Rights Management, and with that goodbye services like Tidal or Spotify (unless you run an OS that is still supported by their apps).
And Wikipedia confirms that I was closer to the truth: https://en.wikipedia.org/wiki/The_Elder_Scrolls_V:_Skyrim
It kind of makes sense on many BIOS/UEFI-less systems where e.g. Uboot is used. And it does contain things like kernel images, sometimes initRD files etc. (which may not be bootloader files but are still system boot files).
I see. BTW, I never figured out the details either, but wanted to bring matters up anyway in case it still would be considered useful.
It did when it was still called Calckey, but around the time of the rebranding their main server got into issues (Kainoa, the previous maintainer, was messing around with it to improve performance but that just broke things).
Closer to Firefish would be Iceshrimp, a fork of Firefish started when the writing started to appear on the wall.
Did the Misskey network not advise against e.g. EU people signing up because of legal reasons like GPDR? Anyway, Iceshrimp works very much as intended and has active development so that could be an alternative for some people (have no experience with Sharkey).
As written in the article, letting through wavelengths other than green. So, yes.
When I see EVs (southern Netherlands) they are mostly model S or non-Teslas from mostly VW. Autonomous vehicles aren’t even allowed here AFAIK.
Edit: I am agreeing with you, for clarity’s sake.
Postal service PostNL uses them, so I happen too see them from time to time.