baduhai

Ahh, I am familiar with the term, but not the acronym.

BDFL privilege

Big Dick For Life?

Aye.

Havjng a look at CalyxOS may also be an option. It’s another privacy android ROM, but it runs in more devices than just Pixels.

There are a handful of repos that have also been updating the extensions too, so all good. Most active seems to be from keiyoushi.

Tachiyomi is dead, long live Tachiyomi.

That’s correct.

the boot keys are burned into OTP memory so they can’t be erased or changed

Which is good, as otherwise it would defeat the purpose of secure boot.

That’s usually not how secure boot is configured on microcontrollers. They usually come with no code installed and an unsigned bootloader, and therefore no barrier for you to flash what you want on it.

In fact, the STM32 has secure boot, and it’s still one of the most popular microcontrollers for makers and hackers. That’s because the secure boot feature is there for developers, hackers and makers to use if they want to.

RP2350 specs:

• Two 150MHz Arm Cortex-M33 cores, with floating point and DSP support
• 520KB of on-chip SRAM in ten concurrently accessible banks
• A comprehensive security architecture, built around Arm TrustZone for Cortex-M, and including:
  • Signed boot support
  • 8KB of on-chip antifuse one-time-programmable (OTP) memory
  • SHA-256 acceleration
  • A hardware true random number generator (TRNG)
• An on-chip switch-mode power supply and low-quiescent-current LDO
• Twelve upgraded PIO state machines
• A new HSTX peripheral for high-speed data transmission
• Support for external QSPI PSRAM

Looking pretty good. I especially like the security features.

I mean I guess I’d rather Trump didn’t win, but I can’t do anything about it. So no, I have no horse in the race.

It was an honest question, I’m not from the US, so I have no horse in the race.

What’s your alternative?

Nah, their question is why do so many people use it. And the answer is because it’s pretty good.

It’s pretty good, innit?

I like it.

The “Leave…” text was indeed very ambiguous, but I’m not sure “Show logout screen” is better. It fixes the ambiguity problem, but it’s a clunky name.

It’s a tough one, cause I don’t have any better suggestions.

Internal combustion engine.

Yeah, I thought of these points too, my fear is that it won’t matter that it isn’t managed by meta and people will go along with whatever meta does.

Though to be completely fair, I have the exact same fear for other decentralised protocols, including nostr. Perhaps the only one I think is resilient to this situation is bitcoin, for better or for worse.

Sure Meta will probably extend AP for their own use but it’s not that they can simply decide that the new feature that they introduced and is at first only working on their platform is the standard from now.

Maybe not formally, but it might not matter. Looking at how google implemented XMPP, then slightly changed their implemetentaion until it was incompatible, and clients tried to keep up with changes, makes me fear meta will do something similar.

I wrote a long answer to this, but forgot to post and lost it :(. But here’s what I wanted to say:

I forgot about Threads, that’s indeed a big user base.

Just because the standard is managed by the W3C doesn’t mean they’ll do a good job of managing it, but it’s probably more positive than negative.

I don’t know enough about how the W3C is organised and accepts contributions, but wasn’t one of the concerns of many AP users when threads announced their AP integration, that threads would immediately become a big player and essentially EEE AP? Tbh, I still fear that.

I’m enjoying this conversation, it’s brought my hopes for AP a bit higher, I hope I’ve managed to convince you that nostr is something to keep an eye on.