BUZZER
WRONG
sorry, that's incorrect. Trump is not president. Please try again.
CrowdStrike offers a $10 apology gift card to say sorry for outage
Several people who received the CrowdStrike offer found that the gift card didn't work, while others got an error saying the voucher had been canceled.
![CrowdStrike offers a $10 apology gift card to say sorry for outage | TechCrunch](https://lemmy.world/pictrs/image/950b87b1-59dd-4a3e-9aa5-c2c5f3999f8b.jpeg?format=webp&thumbnail=256)
I was thinking about it for a while. The posts encouraged me. The prospect of possibly wanting to leave the US in the next year or two depending on things also makes me want to learn a second language.
I was wondering what you'd do with yourself, r2o, after Biden dropped out. It didn't take you long to pivot to being negative towards Harris.
Now Donny's ear is pierced and I know why
That's what was said, but it wouldn't surprise me if that was just cover to plan and execute this maneuver
Yeah - for any dog with a strong enough stomach, any pizza is dog pizza
I feel like this is referencing something I'm out of the loop on
*as long as the blade is kept sharp
I used "Corrections" with the capital C - because I'm referring to the name of the department, not their actual results.
Bad take
If the label is paper, give it half effort at peeling, then let the dishwasher take care of the rest. If it's plastic, peel it off and let the dishwasher wash off the goo. I have had it take a couple cycles to get it all off, though. I do this with Calypso bottles mainly.
I'm not. I'm still disappointed it failed.
You're probably best off looking for a good quality NVMe drive and a good quality external NVMe enclosure and putting them together for this.
In a way they were, but then my version stopped receiving updates and version 2 came out and they wanted me to buy version 2.
That's... how it works? Surely you can't expect ongoing, infinite development without paying an ongoing cost. Eventually the current version will become the old version, and stop receiving updates.
I've seen this take before, and it's always been bad.
Back when perpetual licenses were normal - yeah, you could always install that software from the CD or whatever and input your key and activate it. As long as you were running it on a supported OS, it worked. Most of the time you'd get updates for a while, for the most popular software at least, but not always.
Then eventually, everyone who was going to buy it had bought it, mostly. The money stopped rolling in, and no one's going to make updates for free. So updates stopped.
Over time, it would just become not as good. It didn't change, the world around it did. New security vulnerabilities would be found, or the OS would update and it wouldn't be compatible anymore. Sure you could run the old OS, and it would work how it always had. But then vulnerabilities in the old OS would show up, or the newer OS would have a feature you want, or not be compatible with newer software you also want to run. It wouldn't be feasible to run that old software anymore.
That doesn't mean that the company didn't fulfill their promise. A perpetual license you bought, and a perpetual license you got. Office 2003 still runs on Windows XP. But neither of them are secure anymore, and besides, 2003 is missing a ton of features.
So they publish the next major version. It has new features (Office 2007 introduced docx, the ribbon, and SharePoint), and will get security updates while it's supported. People buy it and use it for a while, then the same thing happens as Office 2003. It ages, and goes to the wayside. People start buying Office 2010.
Eventually, the world speeds up. The Internet becomes faster and more reliable. Updates can happen faster and more consistently. People begin to expect updates for longer. The companies decide the best way to respond is to shorten the cycle. Instead of paying a large sum every few years for the latest version, they'll pay a small sum every month. Instead of major updates with new features every few years and only bug fixes or security patches in between, will trickle out new features as they finish along with security updates.
The thing is - the pricing hasn't actually changed that much. The only difference is that the cycle is smaller, and some people are just now realizing that there has always been a cycle.
CNET posted an article in 2006 with Office 2007 pricing, putting the Home edition at $150. That's $233 now. That's about 3 years, 4 months of Office 365 Personal ($70/year).
3 years after Office 2007 came out, Office 2010 was released. Do you see what I'm getting at? The cost you paid for 2007, in terms of a modern subscription cost, is the same as the time between the two major versions back then.
Sure, you could run it until 2017 with security updates if you were frugal, but trust me it looks pretty goofy to run Office 2007 on Windows 10. And besides, most people didn't. They bought their Windows Vista computer and bought Office 2007 with it at the Best Buy. When they bought their Windows 7 computer at that same Best Buy 3 years later, they bought Office 2010 to go with it.
So really, the license was perpetual, sure. But the software lifetime was never infinite, and people that act like they got cheated on their perpetual license because of that are foolish. The only thing that has changed is the length of the cycle. It went from paying every 3 years and getting major updates every 3 years to having money trickle out and features trickle in.
I know this is a controversial take here, but I don't think that's necessarily a bad thing. It just makes it more obvious how much you're spending, because you're paying more often, which some people don't like.
This is the only way to change that. I don't have much hope that it'll pass, though.
My phone is, yeah. My girlfriend is asleep next to me.
As with all things - the poison is in the dose (and delivery). It would depend how much fentanyl is added to how much candy, and how much candy the kid eats. Also how old and how large the kid is.
Lemmy.ml API returning incorrect information for community list?
So, I noticed something interesting while writing and testing a script.
The intent of the script is to connect to the API of your home instance, then list all of the communities for all instances that the home instance is federated with, sorted by number of subscribers.
The API endpoint to do this is "/api/v3/community/list"
My understanding is as follows:
- The argument "sort=TopAll" indicates that it should sort by number of subscribers
- The argument "type=All" indicates that it should show communities from the local instance and all federated instances.
- The argument "limit" indicates how many results to return (up to 50)
- The argument "page" indicates which page of "limit" items to return
So I should get more or less the same results if I run the same request against lemmy.world or lemmy.ml So I ran these two requests:
-
https://lemmy.world/api/v3/community/list?type=All&sort=TopAll&limit=50&page=1
-
https://lemmy.ml/api/v3/community/list?type=All&sort=TopAll&limit=50&page=1
With the first one, I get a mix mostly of lemmy.world, lemmy.ml, and beehaw.org communities. That's what I'd expect. However, with the second, it's all lemmy.ml communities.
So, like, what's the deal?
---
Edit 2023-06-14T16:03Z
Seems something similar when I request for the endpoint on breehaw.org. The first page is a mix of breehaw.org and lemmy.ml results, but no other instances.
---
Edit 2023-06-14T16:12Z
It's like they're all different and all seem to favor their home instance? Some more than others, though.
- Lemmy.world is pretty well balanced.
- Lemmy.ml is all Lemmy.ml
- Beehaw.org is mostly Beehaw.org and Lemmy.ml
- Lemmy.ca is mostly lemmy.ca and lemmy.ml, with some beehaw.org mixed in
- Midwest.social is mostly midwest.social, lemmy.ml, and a little beehaw.org
AAD Admin portal trouble?
Just started for me. entra.microsoft.com (specifically user list atm) is loading slowly or not at all.
Anyone else or just me?