DSMan195276
Joined 13 years ago
Joined 13 years ago
Put another way, the risk has to be worth the potential reward - expecting Amazon-like returns might be unrealistic, but what level of returns would be necessary to counteract the amount of risk you're taking on if you buy Anthropic stock? And what kind of valuation would Anthropic have to reach for that to be possible?
If you were to do something like run every cancer test possible then _eventually_ you'll find one that says you have cancer, but it's not a valuable result because statistically one of them was eventually going to say that. I don't think most doctors are doing significant statistical analysis to determine what tests to give you, but the general concept that you don't simply run every test you can for fun is very sound, screening beforehand can rule out a significant amount of false positives while hopefully not significantly increasing the chance that something is missed.
As somewhat more real example, rapid strep throat tests overall rarely give an inaccurate positive result, meaning that if the test shows a positive result you can be pretty confident you have strep throat and need antibiotics. However the false positive rate of rapid strep throat tests is extremely dependent on the patient first being screened for symptoms of strep throat - there are lots of asymptomatic strep throat carriers who have no symptoms but do have the bacteria, they don't need treatment but do give a positive result on the test. Thus if you were to give a rapid strep throat test to an entire school to try and eliminate all cases of strep throat then you'd find that ~10% to ~20% of the school gets a positive result. In that situation at least the tests are cheap and you could potentially resolve the situation over a number of weeks, but not every test is so simple.
This might be true for current processes but it seems like it should be possible to duplicate a hologram - use a hologram as a stand-in for the original scene when creating a new hologram. The result might have some blur (that progressively gets worse the more 'generations' you are from the original) but that seems like a solvable problem if someone worked at it.
I think the real reason we don't see them is more practical - it's amazing tech but a bit too much of a novelty in its current state, it's just not something that most people would want to put on their wall.
I'll challenge this, I don't think that's really possible, at least not to any high degree of confidence. Nobody can realistically evaluate if any particular out-of-bounds read/write or use-after-free is "safe", and if you're going to consider all of those as security risks then there's not really a point in trying to filter out the few bug fixes that might not lead to those things.
Try going to the linked page, pick any random CVE, and read it. I've checked a bunch and I'd say _at least_ 8/10 of them are variations on those two things.
But also, as long as the game works on the specific hardware it was designed for then that's all that mattered, which was my point. If it reads uninitialized memory or depends on exact cycle counts or some undocumented hardware behavior then that's _fine_ if it still works on the real hardware, plenty of that was even intentionally done to achieve things otherwise impossible on that hardware.
At the same time it makes it almost impossible to verify even trivial changes to a function. Once you start accounting for all the potential state differences the answer to "does this function work the same?" will basically always be 'no' unless the code is identical. The only way to eliminate various kinds of state from being a concern is to analyze where the function is _used_, rather than just the function itself, and that's an entirely different and much harder kind of challenge.
Emulators constantly run into games that don't run because of specific hardware nuances that may or may not have been intentionally used (Ex. relying on exact cycle counts, reading uninitialized memory, changing values while they're used, etc.).
I think the more important part is to define what "rare" actually means and save/digitize set copies of those books that are actually at risk of being lost completely (rather than letting them rot away somewhere or get bought up to be privately destroyed). I suspect many of them are just not at all interesting enough to justify the expensive though.
No they're not, the systems that exist today often don't even work and there's no alternative of "just mail a letter to Microsoft and they'll sort it out for you".
"Faster" is also a frankly a silly point - it's not like your parents were waiting at the mailbox until the letter came in the mail, the important question is the amount of time actively spent dealing with these things.
> I think this means any solution which involves active parent participation is going to get shunned by a vocal subset.
I don't think that's a fair assessment personally, rather you've missed a key detail that things are significantly more complicated than they used to be, it's not just an 'effort' issue. There is no universal "user is age X" setting that applies to everything everywhere, rather everything has a different system and pretty much all of them are terrible in various different ways.
I'm very tech savvy and I still struggled just to set up a Microsoft/XBox account for my daughter so that we could play some computer games together. Access to all the different age rating settings is spread across something like three different apps and websites and in my experience they don't even all work consistently. That experience is also not dissimilar from the experience with other types of accounts. For people I know who are less tech savvy it honestly doesn't matter how much time they put into it, eventually they give up and turn off age ratings because something isn't work and even if there's a solution it would take them hours to figure out.
Point being, if the existing tools were much better I don't think we would be having this kind of conversation.
The fact that 'unsafe' also enables all unsafe operations in the function body just makes it even messier, since you definitely _don't_ want that unless the entire body is really nothing but unsafe operations. Thus the "mark a safe function as unsafe" has a clear downside since it allows all the unsafe operations you didn't want to use.
Sure, you _can_ still sue them anyway and maybe get around the T&C, but you can sue the government to, the important question is if you can actually win.