Android Tablets with Mobile Internet are perfectly fine phones. I've used a LTE Samsung tablet exclusively as my only "Smart" phone for a while, and had a Dual-Sim to share the same Phone number as on my "Dumb"-phone, (Nokia 8110 4G) ...
From 2015-2019, my only mobile device was an Android tablet with no SIM card. At purchase, I signed up for a Google Voice number, and I sort of got by with VoIP service over WiFi wherever I could.
Since then, I've purchased a proper mobile phone, and I transferred my landline home phone over to that SIM card, and it's my main line now. I use my Voice number very rarely.
One of the drawbacks to SIM cards is that you can't really get the phone service mirrored or transferred to a regular computer. Sure, you can "link" the phone if it's nearby, but the service itself stays there.
I've had a number of times where I'd really like to have voice/SMS service on that number available via computer (some people I know are actually creeped out by my having two phone numbers at once), but what can you do.
I haven't traveled since the Before Times anyway, so boarding a plane with devices is the least of my worries.
That's only cosmetic filters (or at least it used to be). "I don't care about cookies" or the open source fork "I still don't care about cookies" also clicks the buttons to accept/refuse.
The best one seems to be Consent-O-Matic as it actually tries to disable all trackers, but it doesn't work on some sites/popups.
I was scratching my head why I'd want addons at all (running DNS66 on the phone, so no need for an adblocker.) but this is honestly a great idea. God how I hate the cookie banners.
Here’s one. I currently have about five or six small PRs open for bug fixes and minor features. However, they’ve languished a bit in review and haven’t been merged yet. In the meantime, I’ve started a fairly significant refactor. It’s not too complicated but involves moving files and changing some core structures. I am dreading having to rebase those open PRs!
Interesting, you can potentially use MQ for automatic rebasing as well, but if there is a merge conflict, MQ will not be able to resolve it for you. If a rebase can be automatically resolved, then MQ will update the branch for you.
Most of the currently popular frameworks follow the pattern of organizations that make the case that "Designers" and "Programmers" need to be strictly separated.
Interfaces should be strictly separated from the internal application code, with generic layers between them. To do it otherwise means ending up with a "big ball of mud" style app, that cannot have its interface redesigned in any way other than by refactoring it completely.
It is run by a small local webhosting company, at which I've been a customer for my whole adult life (~20 years)