CIRCLE WITH A DOT

@Stellar if you have the energy and skill feel free to

I have neither energy nor the skills anymore, I think ;_;
only thing I've done with android was read-only poking around in jadx

@Stellar right but in-app license check

on this phone I installed it from an .apk backup (the exact same version as above), but I had already bought the Pro license in-app, I don't remember if sync etc works without it

@Stellar https://github.com/noinnion/greader/blob/master/beta/gReader-4.3.1_pro-beta.apk

last updated in 2016 or so

not sure if you can still do a new install, they pulled it from Play Store when they moved to subscription model for later versions (and eventually they pulled *that* from Store too, at least it's not showing up in search anymore)

still syncs with Feedly though so I continue using it

(I am still using a 10-year-old beta build of gReader because all the new apps kinda suck)

bit late to post a Friday screenshot but I thought it was funny

"Restart your device
Wait 24 hours"

I don't like that this exists at all, but honestly IMO this kind of implementation is... acceptable. better than having to talk to some "notarization" API server, at least.

Google details new 24-hour process to sideload unverified Android apps

The "advanced flow" will be available before verification enforcement begins later this year.

Ars Technica (arstechnica.com)

@foone I've yet to see a single person using ĄŽERTY. Or a single physical ĄŽERTY keyboard on sale anywhere. It's /universally/ QWERTY with accented letters on number row

* UEFI dbx
Update Error: Not enough efivarfs space, requested 30.7 kB and got 20.2 kB

surely there's a better way to do secureboot than revoking hundreds of individual file hashes

@ignaloidas yeah but it specifically avoids advertising support for the highest link rate when that happens

(and once I bounce the switch port down/up, it negotiates 100M again)

also Real Networking Guys kept telling me that Ethernet devices and switches do not renegotiate link speed when the ethernet link quality is bad. I am very sure they do. it might be a nonstandard feature but it exists

(iirc Intel drivers call it "downshifting")

(the issue isn't RF absorption or anything, the issue is badly secured Cat5 cable that's probably not rated for outdoors, dropping down to 10Mbps whenever it snows)

the situation with one of the wireless PtP links at work:

@cazabon yeah, Wubi from Ubuntu used to do that. I used it for a while back in the day. It's not going to bypass Secure Boot, though (which it seems Foone's Surface doesn't allow disabling) – and it had zero support for UEFI style boot in general – Wubi would just install grub4dos and configure it to be chain-loaded specifically from WinXP's NTLDR.

(I don't think it touched the MBR? nor the VBR? I don't remember for sure, but I *think* it was ntldr->grub4dos specifically to reduce the chance of failure. Traditional dualboot would go rearranging things to do grub->ntldr instead, but Wubi was for a very non-technical audience.)

These days as far as I know Windows's BOOTMGR refuses to boot anything that isn't digitally signed as a Windows component (unlike NTLDR in WinXP where you could still add arbitrary entries), so you can no longer chain bootmgr->grub, have to boot directly into grub from the beginning.

imo, installing GRUB "from the outside" has become *kinda easier* in EFI world; the equivalent of "fiddling the MBR" on UEFI systems would be "fondling the EFI boot variables", which Windows has an API for (and you can do it through bcdedit, etc) – the bootloader lives on a FAT partition, drop grub.efi in there, add a new boot entry that points to grub.efi – but of course that grub.efi isn't "Microsoft-signed" so it still won't boot no matter what.

as I understand the Surface won't boot even the MS-signed "Shim" because the hardware deliberately lacks the "third-party" UEFI certificates... although mjg59 said elsewhere in the thread that allegedly those are now possible to install thanks to the 2023 cert rollover, which actually sounds like it would work (as soon as there's a version of Shim out there that's signed using the 2023 "third-party" cert, and not the 2011 one)

yesterday at work I was poking at a relatively new computer's ASRock firmware settings, and for the first time saw:

"CSM is disabled. To enable CSM, please install an external graphics card."

...interesting, so the (11th gen i5) supports CSM, but its iGPU does not?