I use two forks on a daily basis - Floorp and Waterfox. Both sync FF accounts just fine.

Alphabet

Right now: Waterfox and Florp, both based on FF.

In long run: I hope Ladybird will become usable in the next couple of years.

> Security.

Ironically, TPM requirement comes from the same company that invented logging your screen every few seconds and storing it unencrypted and without your consent.

Copilot+ thing is due to Metric stuffing. AI is big and Microsoft wanted to juice the numbers so stuffing copilot down everyone throat.

Security is important but like every company, will take a backseat to "revenue" or "growth".

Imagine your local cafe notices and starts feeding you poisoned food instead of asking to pay.

Yet hackers would be outside shouting and banging the doors, demanding to be let in to have the free poison, writing five hundred miles of comments about why they should not pay.

>> it’s almost like punishing users for making the choice to browse the web without ads,

MP is one of the best univariate methods, but it's actually mentioned in the article.

I don't think it's being updated. Latest blog posts are from 2020, and Github repos haven't seen commits for the last 5-6 years. MP went a long way since then.

> At this point the hardware side of things was fine but my Zigbee network was gone.

How come the hardware was ok but the network was gone? Did some Z2M config files go wrong because of two dongles? Did you try to restore VM from snapshots?

Losing the network and having to re-pair everything would be a nightmare for me given the number of Zigbee devices I run (~35) and that some of them are mounted in switch boxes in the walls.

Honestly, I don't think I can answer your question. I didn't change the config but I had to delete and re-pair all devices (or they had been gone from Z2M already at this point, I can't remember - it's mostly an academic distinction though).

Thanks anyway :)

Also, the OAuth RFC does not use "MUST" for 400 response and allows some freedom in this regard:

> The authorization server responds with an HTTP 400 (Bad Request) status code (unless specified otherwise)

https://datatracker.ietf.org/doc/html/rfc6749#section-5.2

TL;DR: OpenBSD is bad as a desktop (no bluetooth, limited gamepad support, etc).

Sounds like it's not great as a server either, if the virtualisation support still isn't up to scratch.

And losing files after a crash is something that hasn't happened to me for at least a decade (not with NTFS,ZFS(FreeBSD),UFS2(FreeBSD), ext4 or XFS), maybe rip out soft updates was a bad idea?

She states in that post she had issues running virtual machines on OpenBSD. This isn't the same running OpenBSD in a virtual environment.

I think the reference was to VMM, OpenBSDs own hypervisor.

Usually you use it as firewall or router in bare metal.

And it was starting to stupidly lag for those use cases by 2007, because after some point you start care about firewall/router performance too...

I adore OpenBSD because it's so lightweight, but I dropped it for FreeBSD when the same hardware couldn't max out a 1 gigabit connection running OpenBSD but could with Free. Since then they have made network changes so I'll probably try again even though the bar's moved and now I need 2.5 gigabit connections to be saturated. Happy to give it a chance anyway.

I just remember considering it for routing/firewalling duties about 2007, grabbing then-current performance optimization guide, and finding whole chapter in how to force irq sharing so that interrupts from any NIC will trigger driver code from all NICs...

I can't argue about gamepad support although I would say it is less desktop territory than console/steam machine territory. But for bluetooth support there are definitely good workaround with those usb class compliant soundcards that autoconnect to nearby bt headset/speakers.[1]

[1] I assume you would want to use bluetooth for audio only because anything else usually sucks and can be done better/faster/more reliably with wifi or USB.