TIL that Backblaze has a desktop app. Seems this is specific to Windows and does not impact anyone using it as just a storage backend for backups through something like rclone.
I just want you to ensure you're not confusing B2 with the product being mentioned here. This is a custom Backblaze product which only works via their apps and I don't believe is available as a storage backend for backups through something like rclone.
I never tried this particular Backblaze product because I don't trust a opaque blob touching my most valuable data nor do I trust unlimited plans that dont mention what the limits are, atleast in fine print.
It is different when you have a billion customers, all with different setups. At that scale, you notice real defects through product telemetry, support ticket volume, or trusted channels. You receive a high volume of bug reports that are due to user confusion, misconfiguration, or misbehavior of other software on the device - where solving an issue for one customer doesn't result in improvements for the other billion. Triage, filtering, and winnowing are necessary here.
I got a lot of those too, it meant I inevitably did a little bit of free tech support for my customers. In the end I felt it was worth it as they raved about the quality of support and it was a real differentiator - not to mention built a lot of brand loyalty (and internal staff loyalty too once I grew enough to build out a team - they derived real satisfaction from actually solving problems instead of playing ping-pong).
I agree regarding the need to triage at scale, unfortunately most large companies I've encountered fail to do this well and seem ill-equipped to accept high quality bug reports of edge case defects generated by expert users (save for the odd exception that arrives by social media from someone who happens to have enough followers to get their attention outside the regular support pipeline).
In my experience this doesn't usually boil down to a systems issue (the ticketing systems etc. exist that should theoretically allow for eventual escalation to the right engineer/developer) but a corporate culture thing (the company just doesn't prioritize customer feedback especially at the level where staff who actually deal with customers interface with the teams that write/maintain the software). Often it's genuinely valued at the C-level (the Bezos story of calling Amazon"s tech support line during an exec meeting is a fun example) but diluted somewhere between them and the rank-and-file.
(Ps. I'm not arguing with you and appreciate you took the time to craft a thoughtful reply)
It should be the other way around - at billion customer scale you should be responsible for how your product interacts with other software whose developers have less resources than you.
Again, that is a lot of trust since it could trivially just… not show it. Which is already the default for most FDE systems for intermediate/system managed keys.
It could also just pretend to encrypt your drive with a null key and not do anything, either.
You need some implicit trust in a system to use it. And at worst, you can probably reverse engineer the (unencrypted) BitLocker metadata that preboot authentication reads.
? This may be one of those "90% of the audience doesn't care and is increasingly less likely to buy from either vendor the more they fight in public" situations
TIL they are called "hives". Windows Registry is an interesting thing. Even casual users have to interactive with it once or twice w/o fully understand it.
Raymond Chen explained why a registry file is called a “hive”:
Because one of the original developers of Windows NT hated bees. So the developer who was responsible for the registry snuck in as many bee references as he could. A registry file is called a “hive”, and registry data are stored in “cells”, which is what honeycombs are made of.
Since this is a Windows C++ app, why not use MUI? It solves this exact problem, and since it's a standard part of the platform, there's broad tooling support for it.
Every time I hear it, it befuddles me just like the first time. It seems like a syntax error or something. My mind literally reels, like the idea is a fish and I can nearly feel the fishing line drag but the syntax and grammar isn’t rigidly applied, and so I can’t increase the tension or the line will snap, as it isn’t rated for this hefty and impactful of an idea as when something occurs specifically. I don’t know if that fish story adds anything, but I realized that there was some potential for wordplay that helps explain how it feels perceptually to hear these English words in nonstandard order from someone to whom it is standard. It’s strange.
How do I know the missing word isn’t [up]coming, as in “Friday (coming [up] (this)) week”? As opposed to next week, which would be “Friday (next) week” in this syntax.
For that matter, the missing word could be this, as in “Friday (this) week” versus “Friday (that (as in the next one after the one contrasted with via the word this) week”. I have no way to disambiguate this, so I ask something like “Friday after tomorrow” or “Friday the 13th” or something. It’s hard being me at times, I’ll admit.
In Germany it‘s even more confusing. In the West people say „Viertel nach Neun“ and “Viertel vor Zehn” which is pretty much „quarter past nine“ and “quarter to ten”, while in Eastern Germany people say “Viertel Zehn” and “Dreiviertel Zehn” which rather means “quarter of ten” and “three quarters of ten”. Even though they are meaning exactly the same times.
My English-speaking father with German heritage said both “quarter to ten” for 9:45 and “quarter of ten” for 10:15. He’s the only person I’ve heard say “quarter of ten”. Now I know that could be from his German heritage even though he never learned German.
Reasonably commonly used in Commonwealth countries.
Next Friday is sometimes too ambiguous, you can never be sure you share the same definition with the other person. Is it the same as This Friday (the very next occurring Friday), or Friday Week (ie next week's Friday).
I heard it used this way in Australia, and I’ve heard it now and then in British TV programs. Only have heard it among very old timers in isolated areas in the US a few times when I was very young previously.
reply