Wow, such a risky bet, I'm not sure it'll pay off.
3,943 karma · joined August 15, 2011
Wow, such a risky bet, I'm not sure it'll pay off.
I Am Not A Doctor And This Is Not Medical Advice.
(I think?).
This wasn't big enough in Tokyo to send out one.
I think you're right to be skeptical, but they _have_ talked about the process publicly.
And I don't think there's anything there that is not reproducible by outsiders? They have access to the same Opus 4.6 that you and I do; though not having to pay for the tokens certainly helps.
I'm pretty sure if you wanted to burn a couple thousand bucks, you'd reproduce at least some of these findings.
They also say publicly in their Opus 4.6 post (https://red.anthropic.com/2026/zero-days/):
>In this work, we put Claude inside a “virtual machine” (literally, a simulated computer) with access to the latest versions of open source projects. We gave it standard utilities (e.g., the standard coreutils or Python) and vulnerability analysis tools (e.g., debuggers or fuzzers), but we didn’t provide any special instructions on how to use these tools, nor did we provide a custom harness that would have given it specialized knowledge about how to better find vulnerabilities. This means we were directly testing Claude’s “out-of-the-box” capabilities, relying solely on the fact that modern large language models are generally-capable agents that can already reason about how to best make use of the tools available.
Maybe bundling these under the same system is a mistake and they should be separate systems with different considerations; it would certainly help with arguments about it online ;P
- - -
Hey, I tried restoring a file from my backup — downloading it directly didn't work, and creating a restore with it also failed – I got an email telling me contract y'all about it.
Can you explain to me what happened here, and what can I do to get my file(s?) back?
- - -
Hi Jan,
Thanks for writing in!
I've reached out to our engineers regarding your restore, and I will get back to you as soon as I have an update. For now, I will keep the ticket open.
- - -
Hi Jan,
Regarding the file itself - it was deleted back in 2022, but unfortunately, the deletion never got recorded properly, which made it seem like the file still existed.
Thus, when you tried to restore it, the restoration failed, as the file doesn't actually exist anymore. In this case, it shouldn't have been shown in the first place.
For that, I do apologize. As compensation, we've granted you 3 monthly backup credits which will apply on your next renewal. Please let me know if you have any further questions.
- - -
That makes me even more confused to be honest - I’ve been paying for forever history since January 2022 according to my invoices?
Do you know how/when exactly it got deleted?
- - -
Hi Jan,
Unfortunately, we don't have that information available to us. Again, I do apologize.
- - -
I really don’t want to be rude, but that seems like a very serious issue to me and I’m not satisfied with that response.
If I’m paying for a forever backup, I expect it to be forever - and if some file got deleted even despite me paying for the “keep my file history forever” option, “oh whoops sorry our bad but we don’t have any more info” is really not a satisfactory answer.
I don’t hold it against _you_ personally, but I really need to know more about what happened here - if this file got randomly disappeared, how am I supposed to trust the reliability of anything else that’s supposed to be safely backed up?
- - -
Hi Jan,
I'll inquire with our engineers tomorrow when they're back in, and I'll update you as soon as I can. For now, I will keep the ticket open.
- - -
Appreciate that, thank you! It’s fine if the investigation takes longer, but I just want to get to the bottom of what happened here :)
- - -
Hi Jan,
Thanks for your patience.
According to our engineers and my management team:
With the way our program logs information, we don't have the specific information that explains exactly why the file was removed from the backup. Our more recent versions of the client, however, have vastly improved our consistency checks and introduced additional protections and audits to ensure complete reliability from an active backup.
Looking at your account, I do see that your backup is currently not active, so I recommend running the Backblaze installer over your current installation to repair it, and inherit your original backup state so that our updates can check your backup.
I do apologize, and I know it's not an ideal answer, but unfortunately, that is the extent of what we can tell you about what has happened.
- - -
I gave up escalating at this point and just decided these aren’t trusted anymore.
The files in question are four year old at this point so it’s hard for me conclusively state, so I guess there might be a perfect storm of that specific file being deleted because it was due to expire before upgraded to “keep history forever”, but I don’t think it’s super likely, and I absolutely would expect them to have telemetry about that in any case.
If anyone from Backblaze stumbles upon it and wants to escalate/reinvestigate, the support ID is #1181161.
I contacted the support asking WTF, "oh the file got deleted at some point, sorry for that", and they offered me 3 months of credits.
I do not trust my Backblaze backups anymore.
To _their phone_ specifically? Probably almost nobody. But to their Google/Apple Photos library?
A lot, if not most of people who use DSLRs and other point-and-shoot cameras. Most people want a single library of photos, not segregated based on which device they shot it on.
I don't understand why they do this at all; but at least it's still a single checkbox you can toggle off, FWIW.
(Desktop & Dock -> Mission Control -> "Automatically rearrange Spaces based on most recent use".)
It's just that for _most_ cases it's perfectly fine to make the users wait until the animations is finished, and handling users tapping multiple things in a quick succession can get annoying and unwieldy.
There are some apps when it's infuriating though, especially when they're quadruply badly engineered and _tie the internal logic state_ to the UI state.
As someone living in a country where I don't speak the local language, I swear at Google Translate engineers daily because I do a "swap the active pair of languages and then quickly launch the camera mode" combo _very_ frequently, and the selected pair of languages isn't actually updated _until the animation finishes_.
It's maddening. [2]
[1]: A quick demo: tap an app on a Springboard to open it, and very quickly swipe up from the bottom to hide it. You'll absolutely be able to interrupt the animation of it launching.
[2]: I'm actually sorta guessing that this is a workaround for a different bug they had; when if you tapped this quickly enough a couple of times you could end up in a situation where the UI displayed a different pair of languages than the internal logic had, so they added that delay, but who knows, maybe I'm theorycrafting too much.
This is a very funny quip.
A famous anecdote about a 3* restaurant in NYC is about the servers overhearing a group of diners mentioning how they ran out of time try a "real NYC hot-dog", and the restaurant staff running out to grab one from the corner cart and plating it up nicely; and how this was a highlight of everyone's experience.
The points-based system is used to allow you to apply for a PR _on an accelerated timeline_; not apply at all.
Having 70/80 points lets you apply for a PR after being a resident for 1/3 years respectively; you can apply without any points after living here for 10 years.
The quotes very much read to me like someone realizing what the change of Paragraph 2 means to Paragraph 3 means in real time and having to figure out what to answer to journalists.
I’m curious how that would work administratively though - would they require you to have that when trying to do Ausmeldung? And what about those who moved out before this law got changed?
Technically, do I need to go Bundeswehr office when I come back next time, to get the permission?
I _want_ to believe if this was a deliberate change that someone cared about; we wouldn’t be having this discussion right now because there would be clear answers to the very obvious questions here, but maybe my hope is misplaced.
AC+ includes what they call "Express Replacement Service", where you will send you an entirely new device as part of your claim, and they'll reuse your old one for parts.
If you _just happen_ to accidentally fall with your phone in hand right after the new ones come out, the delta in price between "a scuffed up, used 1-year old phone" and "brand new refurbished device from Apple" is higher than the price of the insurance and incidental damage fees.
I literally toss my phone to my couch or my bed from across the room dozens of times a week without worrying about misjudging the throw (which happens more than I’d like to admit), toss is on the ground at the gym, have no problems taking long baths with it, washing it under the sink if it gets dirty, and do dozens of things I would not do if I had to pay a full price if I ended up actually breaking it.
Having AC+, lets me treat the device with the level of carelessness that is worth the price to me.
Math-wise with how durable recent flagship devices are, you are probably correct that I’d be better off financially to just accept that I will break a phone every couple of years and just eat the cost.
But psychologically, I’m happier paying ~120bucks a year, than $500 in repair fees once in a while.
"Peace of mind" is not free.
Paying ~ten bucks a month to insure my phone and not have to worry about it getting damaged is worth it to me, even if I could afford to replace it if I broke it; because now I just _don't worry about it_.
_The_ point of that the article you're commenting on, is that a keyboard replacement on a MacBook is very expensive. Why would you make that assumption?
The "most expensive way" to shit the bed is also not the peripherals of the computer dying, it's the logic board giving up the ghost.
Are you working 996 weeks or something?
At standard 40h work-week the math works out to 8.75 weeks to "pay for itself".