It would be amusing if after all this turmoil the work came back to the US but it barely increased manufacturing employment.
It makes the taxes visible and painful and they will therefore (potentially) not rise as fast or as much.
But yes, that’s exactly why the American right makes taxation so cumbersome and horrible: to make people think that taxes are bad, as there’s this assumption you can have civilization without paying for it.
I think this is a smart move. Email isn't a platform where you need to conquer the world to be successful. Hey has been doing great business with an only-paid model. Might as well serve the paying customers first and build up revenue.
Also, whenever you're launching something new, you generally need to limit onboarding. Google did it with Gmail, Bluesky did it with their service. You can't have a flood of 10 million new users all at once before you've had a chance to scale things. Seems reasonable to let paying users in first given that email doesn't have network lock-in effects.
I think there is reasonable skepticism around how committed Mozilla is to this. However, I think that starting with the paid tiers is a smart move given that they'd have to limit signups initially anyway.
[citation needed]
Deleted Comment
I have a pre-Google Nest thermostat which I like quite a bit ... it's probably saved us thousands of dollars in the decade we've had it. Is this also destined for the Google hardware graveyard?
The alarms themselves should be able to work even without network connection, but you won't get to use any of the connected features, loosing all the "smarts" that they charged about $100 premium over other smoke alarms for.
It seems the current plan is to let the device reach their use by date before they shut off the servers, but Google being Google, who knows if they won't change their mind and decide to shut off the server before that.
How is this compatible with Bluesky's internal cultural vision of "The company is a future adversary"[1][2][3]? With Twitter, we've seen what happens with the bluecheck feature when there's a corporate power struggle.
[1]: https://news.ycombinator.com/item?id=35012757 [2]: https://bsky.app/profile/pfrazee.com/post/3jypidwokmu2m [3]: https://www.newyorker.com/magazine/2025/04/14/blueskys-quest...
If Bluesky becomes evil, you just configure your AppView not to trust their verifications.
Of course, that's the problem: right now we mostly have one AppView (bsky.app), which is the current SPOF in the mitigation plan against the "Bsky becomes the baddies" scenario.