d0ntpan1c

Even so, google being forced this way will make app installation/updates much more convenient for non-root and oem-rom users. And ensure rhe aurora store or a future iteration of it aren't going to flag peoples accounts for google to take action against them.

FWIW some of the problems are on website/app developers. Not sure on specifics on the app side, but with websites if the dev doesn't use semantic html input elements with the correct type attribute to denote the password form, autofill won't work (since neither android or the password manager know its time to do stuff)

Nothing wrong with username/password on different screens (one at a time is good for several accessibility-minded reasons) but again, there are some best practices to follow which allow screen readers and password managers to still act as you would expect.

I'd assume android app dev is similar.

That said... I do think it's gotten a bit clunkier at times in ways I dont recall being problematic in the past. I use 1password and heliboard or floris board and while those keyboards seem to bug out a bit, sometimes the bigger problem seems to be that android isn't always telling 1password enough info to find the right account. Idk how apps "inform" the password manager (maybe via url's in a metadata file or maybe passwors managers have ro keep theor own internal db?), but apps that use web wrappers (specifically the old and/or shitty ones) report their url as http://localhost since the wrapper just renders a local page in a web view. that'll wreck a password managers day real quick.

Idk if Android is worse than iOS here, not that it is a reason for google to punt on improving it. iOS has its own autofill quirks thay can be just as annoying. Esp constantly asking if you want to use your app or apple keychain without a way to just pick a default...

Except they didn't... If you read more than headlines

So the site should just... Not work in firefox then?

A lot of the sites in the about:compat block or don't work in Firefox because the sites don't follow web standards

All web browsers have semi hidden pages like this for all sorts of purposes. Its not really intended to be secret, its just not stuff worth even adding to a file menu. Some of the about: pages in firefox are in some submenus, some on settings, but def not all. Tho you'll fimd them mentioned and linked in support guides.

If anything, the ability to access these is better than them being blocked...

No, but if its prohibitively impossible to do so, people with legitimate good ideas will never be able to do anything about it. Barriers to entry only serve the wealthy.

I'm not in a rush to move over from K-9, but once they add account sync with desktop to the mobile app I'll def be migrating. Getting to be a bit of a pain to manage Thunderbird on a few PC's + phone and i'm very much looking forward to simplifying all of that

The main thing they want testing for is the migration tool from a k-9 app installed and configured already on the device, which would be net new code.

I, personally, think that you should not have a website if you can't pay for it yourself

You might want to consider how expensive web hosting can be, depending on the content and traffic. A belief like that can shut out a huge portion of the world from being able to even bother with a web site. Even a simple blog can get very expensive due to traffic. Maybe not expensive enough for your average 1st world individual... But that still excludes a large portion of the population with internet access.

American Libertarians (in case you aren't familiar or for anyone else with the sentiment) tend to be very conservative compared to lowercase libertarianism as a whole, and especially compared to European libertarianism. Much more focused on classical liberalism, but also more likely to lean towards selfish solutions than community solutions.

Idk if you've had the pleasure of /r/libertarian on reddit, but that place was always conservative as hell with little room for anyone of the libertarian-socialist persuasion to have an opinion or any desire to come up with group-based solutions.

Google does a really good job convincing you they care with the shuttle system, cafeterias, break spaces, and otherwise.

It convinces you to work more than you would otherwise, too (sure, why not finish up that task on the shuttle with WiFi... Hey I'll just grab food here instead of go home. Food at home cost money anyway... Lemme just finish that thing before heading home now that I've had dinner...)

I've also had struggles with arch with printing, more so than debian-based distros. EndeavourOS is where i did the most troubleshooting, but its also a problem on my manjaro install (whicj ill move to endeavour... Someday) But learning how to use cups directly was worth it.

Currently, printing via GUI is like 5ppm and very low dpi so... Not great. But at least I can print for the casual use cases out of the box and could work out a terminal solution if I needed to in the meantime.

I don't print much so haven't put time into getting things working better for bigger jobs, but printing is definitely going to be a more hit/miss experience with arch. Its looking like better GUI experience for my specific model will require a driver from the AUR or scripting the Debian install from brothers drivers site. But my model is apparently not as widely used and just hasn't gotten as much community support I guess