Big problem here is that Microsoft seems to have given up on sleep states, and just does S5 and then hibernates (which is horribly slow), so S3 on newer machines is often horribly broken in the firmware and can’t really be used. I’m not really interested in my system going to S5 - I want it in S3.
Yeah, things are getting to the point where just having a mobile device running Linux and using Waydroid for some useful Android applications is less painful than trying to make Android work.
Problem is that it not really is “just a store”. By using the google store you get access to the google play APIs, which are upgraded separately from the device OS - which is sensible from a security perspective, but they also were created by google specifically for regaining control over what goes on on Android devices.
A lot of applications are needlessly tied to play APIs - either because that way is a bit easier, or just because google is good at marketing them, and the developer didn’t think twice about it. Some relatively basic APIs are part of google play - for example maps, which needlessly is tied to google maps. Unlike Android itself the play APIs are not opensource.
Yandex tried about a decade ago to re-implement the play APIs to keep such applications working without the play store, by utilizing other services providing the same functionality, and tried to get other companies to join them. I’ve visited the Yandex office in Saint Petersburg a few times to discuss that back then (just checked, most of that seems to have been 2014 - that year Yandex was sponsoring my Russian visa). The effort failed for various reasons, unfortunately - the big one being that doing this required reverse engineering API changes on every play update google was pushing to stay compatible. There’s the microG project around now, but it seems to be less ambitious than what Yandex was trying to do back then.
My point is, as long as at least the API for play services isn’t maintained in a way that allows full open source reimplementations - or better, google releases parts as open source where we can plug different backends in - “use a different store” is not really a possible solution for many.
Almost a decade ago there was a discussion how to draw into display buffers for Wayland. Everybody agreed on using Mesa GBM, nvidia wasn’t really interested, but said they’d do EGLstreams.
As nvidia wasn’t interested, and generally is a dick to everybody anyway Wayland development just progressed ignoring nvidia, and now they have to catch up to where all the other graphics driver were at already years ago. While ignoring most of the things those others learned, because they want to keep their own tiny proprietary island.
Just avoid supporting nvidias dickish behaviour by not giving them money, and eventually they might learn and change.
A surprising amount of services (including Azure last I tried) can only handle RSA keys, so after trying ecdsa only for a while I ended up adding a RSA key again.
With that said - it’s 2023, in almost all cases you should have your keys in a hardware module nowadays, in which case you’d use a different command for keygeneration.
At least my kid remembers quite a few things from that time. She sometimes goes “remember when I was crying so much…” following by an increasingly detailed description of a situation until I do remember. And then she tells me what the issue was back then, which she didn’t have the ability to explain yet back then.
It did, but note that the linked picture is the full resolution of the camera. Also, the phone had very limited storage space, and the display was in no way suitable for displaying the pictures taken, so you just hoped for the best until you managed to check them on your computer.
The S55 got lost eventually, but the camera module should still be around here somewhere.
In IT contracting (at least the fields I’m around) it’s quite common that “being able to acquire new skills quickly” is one of the skills you get paid for, and the time needed for you to do that is accounted for in the project planning.
Yeah, but x86 was relatively cheap. Alpha and Itanium were in a similar price range.
At that time Alpha belonged to Compaq - and they stopped Alpha development (and canned quite a few good designs which were pretty much ready to go), expecting they’ll be able to replace it with Itanium.
I made a quick plugin to also run stuff from path, and am currently working on a proper ssh plugin for that - extending them is a bit more involved than the simple rofi/wofi scripts, but there’s a lot more things an anyrun plugin can do.
I’ve been using (or, in some cases, trying to use) that when it was brand new. Kernel side was relatively easy - but there was a lot of compiling custom versions of XFree86 trying to get acceleration working properly.
On the one hand a bit sad to see that kind of history I’ve experienced myself go - on the other hand, it’s probably been a decade since I’ve last used something without KMS, and the ease of use of modern KMS drivers is way ahead of all the older stuff.