Yes I am aware, it is why you don’t buy new, there are thousands of used computers out there that I made a side hustle out of buying them and reselling them after some cleaning and fixing, so many I found that’s beyond to list here, but for example I got asus zenbook 14 for $12 because it didn’t boot (which was just a loose connection inside), a macmini m1 for $50, and many other parts and finds. I even have a thinkpad with proxmox and run as a server, uptime now is more than a year.
I'm curious where are you going to find these used machines (EBay, govt auction, Facebook Marketplace, etc...)? I have been wanting to setup a home NAS and home server but am not paying these prices.
Seriously I can’t even get my refurb enterprise drives for reasonable prices anymore. Used to pay like $150 for 14TB ultrastars now it’s like $300 for 12TB exos
Last night I found a 3TB external USB 3.0 drive at the bottom of my "computer junk" drawer that I had completely forgotten I owned. It felt like winning the lottery.
Got some old gtechs I used for production work years ago, lots of 2-4TB that worked for 6-12mo then were moved to a closet and powered off for the last 8-10 years. Thinking of shucking them and checking them. Can’t imagine they’re bad yet.
> Why haven’t they fixed Amazon Linux then? Same as none of their AMIs for bottlerocket have emSign revocations.
Last I checked, Amazon has also not patched their Lightsail blueprints for WordPress, or even communicated about the vulnerability with those customers at all, which is arguably way worse, because
(a) by design, all-in-one blueprints aren't really intended to use system PHP or have system PHP updated in a meaningful way; and
(b) hosting static sites such as WordPress is 90% of the selling point of Lightsail as a product
That's pretty awful. I do wonder if they've bitten off more than they can chew with all the ancillary stuff to their core IaaS platform. That seems to be the only well maintained bit of their estate, well EC2/VPC/S3/R53 etc.
I don't have an objection to doing a different DNS security system, and in fact I like DoH a lot. You can do DoH all the way back from authority servers if you like, and that addresses domain validation without boiling the ocean with 1990s cryptography the way DNSSEC tries to do.
If you have entered into the contract and are even party to it in the first place, which is not clear in this case and is likely going to be one of the questions litigated here.
Didn't the guy run an instance himself? Clickwrap licenses are generally held to be enforceable so that's one way he "agreed" to the terms. Also even if he didn't, as a matter of practicality he probably needed to connect to the site to develop nitter , which exposes him there too.
> Force hospitals to expose API's with transparent pricing.
Unless you're uninsured (which is a whole separate clusterfuck), the hospitals aren't the ones who decide how much you pay for any service - the insurance companies are. The sticker price that hospitals charge is almost meaningless and is intentionally high because it's used as the starting point for negotiations, which always bring the price down (never up). There isn't any expectation that any insurer is actually going to pay the billed amount as-is.
That's how virtually all industries work though. The computer you are typing on right now probably costs a different amount depending on which retailer you bought it from, even though it's the same manufacturer.
The fact that it's already common doesn't mean it shouldn't be illegal.
And I'm talking more specifically about a single entity selling to multiple customers. If two different retailers want to charge two different prices of course that's fine.
Hospitals shouldn't have to negotiate with insurers. It should be illegal for an insurer to not pay for a necessary procedure at the hospital's standard rate.
> But this went out of the window when some genius decided that usernames were too complicated, so Passkeys had to be discoverable, which means they have to be fully stored token-side. Which of course has the nice side benefit of essentially killing hardware tokens and forcing people into using their Android/iOS/Windows device for it.
This part of your comment is incorrect. Discoverable Webauthn absolutely can be used with hardware tokens like Yubikeys.
reply