I wouldn't have been bothered by this at all (including the splash), if Windows hadn't reassigned Edge as my default PDF handler. Delving into the dark guts of the default programs settings, and finding a way to convince Windows that it was alright for Firefox to open PDFs even though it hadn't been installed from the Windows Store, took a far longer context switch than it deserved.
Same here. I have a work GitHub account, and a personal GitHub account, and am signed into each in a different container. Saves constant logging out and in, or using different browsers for each.
Progressive web app. They're kind of like JavaScript-driven websites that think they're native apps. They tend to be characterised by their use of modern web standards to do some useful things, like being available offline, and caching everything heavily to cut down load time. It's like a website you can install, basically.
For me, they’ve “fixed” that. I finally got their amazon couriers blacklisted, so they are shipping usps.
But, if i order from an account without prime, they wait 11 days to ship, thus giving me 12 day delivery (just within their promised 2 weeks). If i order from an account with prime, it alternates between next day and two days.
Editing to add:
Last order without prime, Dec 28. “Shipped” yesterday (usps shows it arriving to them at 4:35 this morning from amazon, out for delivery today).
I had to do the opposite because USPS is so bad about delivering packages. The Amazon branded couriers basically saved me as a Prime customer.
There was an article [1] from 2017 about USPS couriers lying about packages being delivered to keep up their Amazon delivery statistics. This routinely happened to me.
Constant complaining to customer support when the package kept being marked “building closed” when they decided they didn’t want to deliver (this is a house, not an apartment, so no building to close).
After 3-4 packages arrived a week or so late because of the same issues, they finally blacklisted amazon delivery. Since then, it’s been usps.
Typescript's increasing ability to type check JS code without modification (especially if it already has JSDoc comments or is already using npm-installed libraries with type information) is moving it to be a better fit as a solution for more situations.
This is probably a reaction to the news that Facebook is now officially tracking non-users to create shadow profiles and serve adverts to them off Facebook itself. I think it's the serve-adverts-off-Facebook-itself part that's the actual news; all of the moderately chilling tracking and profile construction was of course happening already.
And yet, Google started going down a similar path since December 2009 when they introduced personalized searches for non-logged-in users and nobody tries to block them.
The problem with blocking all google doains is the amount of sites it would break. Youtube, gmail, googleapis for js libraries, google's blog platform, maps based on google maps and more would break.
Technically true, but blocking all Facebook domains breaks comments on many sites and the login feature on a few crucial ones too.
<sarcasm>It also 100% breaks your social life, but maybe there's little of that left to disrupt anyway, amongst the typical target audience for these lists :P</sarcasm>
It's actually the other way around. Normal people have managed their social lives without facebook for generations. It's only the recent crop or two who seem unable to do it.
No, "Normal people" who care about their social lives use whatever their friends use to get together at the time. Nowadays this is social networking sites, i.e. Facebook.
This is factually incorrect. Just because you haven't personally seen people block Google domains doesn't mean those people don't exist. I've blocked many Google domains for a long time. Not only was GA the first domain in my blacklist, it's also the domain that many of my non-technical friends/family wanted blocked.
I seem to remember that they were using it to punish out-of-date browsers. But since I'm getting it with up-to-date Chrome, it doesn't seem to be very well targeted.
