So how does a diabetic get one of the older, worse insulins that they can afford? Certainly that's preferable to the better insulin that they can't afford.
At Walmart it is $25 for 1,000 Units of Novolin N [1], with no insurance or prescription. 1000 units is about a month for a lot of people. Novolin N is a third or 4th generation Insulin approved in 1950.
You can get 1000 units of Humalog (Approved in 1996) for $43 at walgreens or most pharmacies (or 19.99 with a Walgreens coupon) [2]
The more recently approved version of Insulin Afrezza, (approved in 2014) costs about $2,000 for a monthly supply.[3]
There has been a fairly consistent march of insulin improvements since the first versions were sold in 1926. [0]
I looked into Envoy a few years ago and found it difficult to get started. I recall the syntax involving long names that were hard to look up from the docs.
I'm assuming some of those issues may be why it isnt as commonly talked about as nginx or caddy
Google may use many anti-competitive practices, but that doesn't make them wrong when pointing out specific anti-competitive practices in their competitors.
I'd be quite pleased for ALL the big companies to point out their competitors' anti-competitive practices.
Edit: For context, the parent commenter was saying something similar to "The pot calling the kettle black"
I am all for a good Google bashing session and if you search for “crack addled flea”, you will see my opinion of Google’s attention span and business strategy.
But I haven’t seen Google do anything this egregious. But I’m in the cloud space.
Google Takeout is a masterful ruse. "You're the owner of your data! Export whenever you want!"
Perhaps my Drive files are recoverable. (Except, of course, for the linchpin Docs/Sheets/Slides.) The main issue I found with Takeout is, there's no corresponding "Import" function anywhere, to anyone, not even Google themselves!
At least 3 times, I've started projects in one Google account, then had a need to move that specific stuff into another. Takeout won't do it. Lossy exports means that you're leaving significant data behind, especially in YouTube and whatnot. Anything with timestamps or historical, how would that work? I basically found myself starting from scratch, losing metadata and manually recreating things like playlists and Maps lists. Photos? Forget it!!!
There's no export for settings or preferences, and certainly no import or programmatic management. You get comfortably ensconced in Workspaces, and there's no exit strategy.
Compare that to when I set up a new Google Pixel: it automagically cloned itself from my Motorola, without very much warning or consent, it had all my preferences and accounts in the blink of an eye. Granted, this was beneficial and welcome, but I doubt that the process would've been smooth if I'd chosen an iPhone.
Well, Google's concern may be a two-way path for import+export for people like me who did wish to migrate accounts. That seems the most useful and ideal situation, because Google gives you control of your data, yet they get to keep you in their system.
Export functions usually anticipate the format of the importing system: "do you want this contact exported in Outlook format, Apple, Google?" "Calendar export for iCal, etc." "Image export in jpg, png, webp format?" "Save as PDF, .docx?" So it's utterly strange to be exporting stuff where there's no complementary import function, like at all. Like Google itself has no such thing. You can't import back to Photos, or YouTube, or Gmail, or Workspaces. Forget it. Upload new content or GTFO. That's just lock-in.
But it's more like "malicious compliance": "here's your data! it's really yours! we let you have it! good luck now!"
I see that there are some guides on how to use Photos Takeout data and merge it back into something useful, reconstruct an EXIF or whatever, but they seem quite ad hoc and that addresses only one out of many products/services. There's simply no way to recreate YouTube accounts.
I've often simply built a playlist in one account, and/or I subscribed to dozens of channels, then I've got an alt account and I want to migrate all that over. There's no possible recourse but manually reconstructing all of it, click by click.
Sure, not Google's concern, I suppose. They've got your data, they don't need to offer Takeout service at all. It's mystifying to me why they would, other than checking a compliance box. It would seem that if "Import" were easier they would gain more users going through there, yes? Unusable exports are painless to them, because they can be sure no customers would just set up shop on MS 365 in an hour, but lack of Import functions must be detrimental to adoption rates.
I also don't like AWS's odd names, but there are competing priorities when choosing to name something. I thought of some things to consider when you're naming which may make you choose a (possibly terrible) proper noun instead of a generic term.
* Is what you're naming a product which you can trademark? Or is it just a feature that would be silly to trademark? (EC2, Sagemaker, CloudFront vs account, billing profile, user)
* Does the name help with people differentiating your product from your competitors product?
* Does the name help people find the product when searching online?
* Does the name help ensure that the product isn't regarded as "Just a (generic term)" when it is more than that?
The sad thing is that politicians who get these laws passed don't want to collect data about whether the laws were successful.
If they collect data and it turns out the laws aren't helpful or the laws are actually harmful, then the politician's career and reputation may be trashed. But if they pretend like the law can't possibly be bad and never check on that, then they're protected.
To those wondering why the quotes are given, I assume it's because no 23andMe system was compromised.
The data was retrieved via credential stuffing, which is trying username/email and password combinations from other data breaches.
It can be argued that 23andMe should have had stricter login requirements (e.g. require MFA, require longer passwords) and by failing to do so they were responsible for the leaked data. Or you can argue that the users didn't protect their own data since they didn't use long, secure passwords that were unique per website.
I've used Portainer, which works ok. It's web-based and is easy enough to run as a container itself.
My preferred UI for managing containers is Lazydocker. It's a terminal UI, so I can run it on servers too.
For the most part I just use the command line on Linux, but when I need to go through a large list of containers, images, or volumes to clean up, lazydocker is much better than the command line.
The other actually happened to me recently, my wife answered one of those automated bank texts checking on a transaction with no, which cancelled the card (and marked it stolen), and I tried to use it before she told me about it.
But yeah those are the only two I can think of and yours is the case 99.99% of the time.
reply