AWS (which isn't Amazon, really, even if they share resources), used to bake the cost of keeping the lights on practically forever, or at least until the last user churns. The product may not see improvements if it didn't get traction, but you could bank on being able to use it forever.
When they did decide to kill something, like non-VPC EC2, you'd get the notice a literal decade ahead. For this specific example, sunset started end of '13, with the last instance shut off mid '23.
This all started to change a couple of years ago, when they became much more aggressive with doing the Googles and just killing a thing with a few months of a warning. Pity.
Using android.content.SharedPreferences, set one singaling the user purchased a license from the Amazon copy of the app, read it from the Google Play app.
It is doable, the main issues is:
1. Getting users to redownload the app from the Play store
2. Maintaining this registration transfer mechanism
Telegram isn't a messaging service. It's a social network with a messenger UI. Quite ingenious, if you'd ask me, but a social network and a private messenger can't really be reconciled into a single product.
Security is not privacy though. If I had a piece of information that could kill, I would trust Google with safeguarding it. What I don't trust them, is not to use information they got. Or rather, I expect them to use it (but safeguard it from others, because that's how they make money: by being the only ones allowed access to private information).
You'll then create two systems – PPOs for the healthy that can afford it, underfunded HMO for those who can't.
Just drop the rebates, and make any secondary insurance be primary. That would make sure the insured group for the public system includes the healthy rich (which makes the pool for those that actually need and can't afford their health).
A small business is low volume, hence going to have a hard time getting good rates. And they're also constrainted on resources, so the extra effort to get a few points off may cost more than those points (as written above – they're low volume. The cash value for a bp is much lower for them than for a high volume business)
Those are highly regulated, regarding which data they can or can not use, and that regulation is (surprisingly?) very consumer friendly. There's more of a risk of a CRA getting hacked and their collected data being sold
The basic square hardware is about 1/5 the price you listed, but I don't think it's the price, but the effort – filling a form in the app vs waiting for a package to arrive in the mail, and setting up some extra hardware (What I must wonder is what Apple charges Square for this feature)
The IRS doesn't make the rules, but enforces them.
Unlike a somewhat popular opinion on this website, the law isn't an algorithm, but a codification of societal norms, like that we all share the expanses of living in civilized society.
Yes, the TRANSFER of assets happens at time of sell or withdrawal, but the share taxes was painted such when we (the people, through legislation. Not the IRS!) decided that such share should be dedicated to society.
This isn't about letter of the law, and never was: it's being an asshole.
Seems to be working for the New York Times – “The publisher blocked all open-exchange ad buying on its European pages, followed swiftly by behavioral targeting. Instead, NYT International focused on contextual and geographical targeting for programmatic guaranteed and private marketplace deals and has not seen ad revenues drop as a result“ (source: https://digiday.com/media/gumgumtest-new-york-times-gdpr-cut...)
When they did decide to kill something, like non-VPC EC2, you'd get the notice a literal decade ahead. For this specific example, sunset started end of '13, with the last instance shut off mid '23.
This all started to change a couple of years ago, when they became much more aggressive with doing the Googles and just killing a thing with a few months of a warning. Pity.