lsanders
94
33
lsanders has not written any posts yet.
My answer to that question would not quite be a categorical yes or no. For example, there’s a difference between a manually taken selfie and a complete raw security camera feed.
But I do agree this is straying from the original topic a bit. Since the top-post use case is explicitly one where you’ve already decided you’re not comfortable posting the original photo publicly, I feel like the general acceptability of posting photos is mostly irrelevant here? I think a more on-point justification would be talking about why it’s more acceptable for an AI to see the original photo than for your general audience to see that same photo.
(To be clear I don’t personally have a major problem with this practice, at least as you’ve applied it so far, although I also don’t think it’s really added or subtracted much from my enjoyment or understanding of your posts so far. Mostly I just don’t find this particular justification to be convincing.)
Tiny typo: Indiana is IN, not IA. (Apparently there once was a Bloomington in Iowa, but that now-uninhabited locale was neither on your itinerary nor plausibly ever <7 hours of legal driving from Pittsburgh PA.)
Ah, that’s probably a better process than our house’s trick of having two separate MA EZPass accounts simultaneously associated with the same car in order to get a second transponder I can use when I rent. (Our way makes it hard to predict which account gets billed in the rare occasion that they have to fall back to the license plate because a transponder read for the double-associated car fails.)
My sample size is not huge, but personally I’ve never had a problem with associating mine with a rental using the timestamps of my rental contract and indicating that the car is a rental.
Fair enough, although I put a little less weight on the undesirable precedent because I think that precedent is already largely being set today. (Once we have precedents for regulating specific functionality of both operating systems and individual websites, I feel like it’s only technically correct to say that the case for similar regulation in browsers is unresolved.)
Also, the current legal standard just says that websites must give users a choice about the cookies; it doesn’t seem to say what the mechanism for that choice must be. The interpretation that the choice must be expressed via the website’s interface and cannot be facilitated by browser features is an interpretation, and... (read more)
In theory, yes. Do you have particular knowledge that things would likely play out as such if the regulations permitted, or are you reasoning that this is likely without special knowledge? If the former, then I’d want to update my views accordingly. But if it’s the latter, then I don’t really see a likely path for your regulatory proposal to meaningfully shift the market in any way other than market competition forcing all major browsers to implement the feature, in which case it doesn’t practically matter whether the implementation requirement has legal weight.
Once you’re willing to mandate browser features to bolster privacy between multiple users on the same device, I’d get rid of website-implemented cookie banners altogether (at least for this purpose) and make the browser mandate more robust instead. I could see this as a browser preference with three mandated states (and perhaps an option for browsers to introduce additional options alongside these if they identify that a different tradeoff is worthwhile for many of their users):
Good to know, thanks!
(And thanks in particular for linking to the original text — while your excerpt is suggestive, the meaning of “similar device” isn’t entirely clear without seeing that the surrounding paragraph is focused on preserving privacy between multiple users who share a single web-browsing device. I feel like that is still a valid concern today and a reasonable reason for regulations to treat client-side storage slightly differently from server-side storage, even though it’s not most people‘s top privacy concern on the web these days and even though this directive doesn’t resolve that concern very effectively at all.)
(I'd love to see the regulations changed here: there's no reason to single out storing data on the client for special treatment…)
I haven’t personally needed to pay super close attention to the e-Privacy regulations but I thought they exclusively focused on cookies as a specific technology? The web has client-side data storage that is not cookies, and cookies are more privacy invasive than simple client-side storage because they’re also automatically transmitted to the server on every matching request without any further interaction from either the user or the website.
It seems to me that it’s much easier to respect user privacy when using other mechanisms for client-side storage and for transmitting data from... (read more)
Yeah. Other folks have already mentioned that the degree of enforcement leeway in the U.S. increased when the federal government made artifically-lower speed limits a requirement of federal highway funding in the 1970s. Which I can’t confirm or refute, but does make sense: I imagine that some states who disagreed with the change might have grudgingly set the formal limits in line with the federal policy, and then simply used lax enforcement to allow the speeds that they preferred all along. I have noticed that it’s often seemed politically unpalatable for officials to stick to a program of stricter enforcement to rein in a particular area’s entrenched driving culture after speed limits... (read more)
Perhaps one common theme in the objections you find more compelling is that existing systems of accountability are unprepared to effectively allocate responsibility for outcomes that are (at least partially) generated by AI?