angiolillo
Joined 15 years ago
Joined 15 years ago
What makes the comparison wild? The Amish are thoughtful and deliberate about what technologies they reject, adopt, and accept with constraints. Many of the people I know who have concerns about relying on LLMs are similarly thoughtful and deliberate.
That doesn't match my experience. Personally I've found Apple fans (not just Gruber and Nielsen but regular Apple users) to be the most vocally critical of their design missteps.
Is this true?
This is only anecdotal but my experience has been that the amount of exercise people need to maintain basic physical capability seems to vary with age, gender, diet, genetics, and other factors.
Personally, I find that as I get older I have to be more diligent about exercise to maintain basic physical capability, and I have older relatives who spend time exercising just to maintain sufficient VO2 max to be able to do things like walking up stairs.
And it's not just age. I have friends who can take a break from rock climbing for half a year or more and when they come back they're climbing routes at roughly the same difficulty as before they left, whereas others take a couple weeks off and have to work their way back up from easier routes when they return.
That seems very much like exercising, no? You need a certain level of exercise to maintain basic physical capability but past that point there are diminishing returns. So if you truly detest exercising (or socializing) then you can stop there and still lead a healthy, functional life.
Encouraging someone to push past their comfort zone is helpful. But it seems less helpful to imply that you know more about the bounds of their comfort zones than they do, or that their comfort zone must simply be a cultural construct because it doesn't match yours.
It's worth pointing out that the original Document Foundation blog post (https://blog.documentfoundation.org/blog/2026/09/03/yes-no-a...) seems to be doing exactly this:
> The criteria we have listed do not amount to a definitive rejection. The AI sector is evolving rapidly; on-premises inference is becoming manageable on standard hardware; and open models are improving much faster than most of us had anticipated. Should an approach emerge that meets all the conditions, we will evaluate it very carefully.
First, leaking a device's content filtering settings is not the same as leaking a user's age bracket. For example, if the server identifies a web browser that isn't loading tags annotated with "sexual-content" that might indicate that the user is a child but could equally well indicate that they're a corporate office worker, religious, or anyone else who prefers not to see such content at the moment.
Second, if the standard defined multiple semantic tags or levels (e.g. violence, extreme violence, substance use, unknown, etc) then this gives more granular control to device administrators who may care more about some types of content than others.
Third, web browsers wouldn't even have to leak the content filtering settings. For example, perhaps an administrator could configure the web browser to render content overlaid with a semi-opaque blur, in which case the server would not know.
Fourth, and this is more philosophical, asking websites to provide more information to the device so that an admin can do their own filtering leaves the choices to them. Whereas if the only way a device admin can filter content is to submit the age of the device's user to a third party so the third party can decide how to pre-filter the content it sends back, that gives an uncomfortable amount of control to platforms and regulators.
I don't understand why you think this is true when I specifically described a label that is applied to "an individual section" of the page.
To be more explicit: Today, each post on the Reddit front page appears in its own container element. If an 18+ post's container element could have some kind of "adult-content" attribute set then some web browsers could render the whole front page normally with the exception of that individual element. Perhaps they could black it out, collapse it, display it with a pixelated overlay and a "Request Access" button, whatever the browser supports and the device administrator prefers.
> The solution is obvious: you show it on the front page if the user is 18+. However, your proposal deliberately forbids this and says the front page must be the same for everyone.
Why do you think that my proposal requires that the front page must be the same for everyone? Providing different views to different users is the entire point of every child safety law and rating scheme I've ever seen. I'm merely saying that my preferred approach would be to mandate that potentially objectionable content is semantically annotated in the HTML somehow, so that each user's browser can apply whatever view restrictions (if any) the device's owner wishes. I think this is better than mandating that web browsers send personal information to every web site they visit and also mandating that sites pre-filter the content they send back.
As one example, the Internet Content Rating Association (ICRA) (and to a lesser extent the prior Recreational Software Advisory Council (RSACi)) had a rating scheme that allowed sites to provide a default rating label that was then overridden for individual pages and resources using <meta> tags and RDF-based labels. For example, Tumblr could set a family-friendly default rating and append a different rating on specific user pages, images, or ads.
An even more granular scheme could be applied via HTML attributes which would allow an individual section, image, link, or text snippet to be marked e.g. as "sexual", "violent", "substance use", "spoiler", or even "unknown" for unreviewed user-provided content. Then leave it up to web browsers to choose whether and how to render elements with these attributes. (Hidden entirely? With censor bars? Pixelated?)
There would be substantial logistical and regulatory challenges to get websites to comply, but it doesn't seem substantially harder than the current age verification schemes.
It might be useful to be able to configure the map viewing angle at the top and bottom of the frame, perhaps even the degree of curvature between them.
I say this because I wonder if a shallower gradient (slightly more top-down at the bottom and slightly more angled at the top) would be more understandable and familiar while providing almost as much information. Not as cool-looking, but potentially more useful as a real navigation aid.
I can imagine raising issues with a specific datacenter in a specific water-constrained location, but I agree that being vocally concerned about the teaspoons of water consumed to produce an AI response while being unconcerned with the thousands of gallons used to produce a cheeseburger seems like innumerate virtue signaling.
With respect to human lives it could mean the difference between tens of millions of deaths and billions of deaths. With respect to wildlife it could be the difference between losing 10–20% of the planet's species in the Holocene extinction versus 40% or more as per the IPCC. With respect to migration it could mean the difference between levels that are painful versus globally destabilizing. With respect to geoengineering it could mean that we have significantly more time to refine the technologies before they're inevitably deployed.
I think you're right that reputation systems are the best solution to a low signal-to-noise ratio.
Consumers (and the agents under their control) will increasingly prioritize content and other products with reliable attestation that they come from a trustworthy publisher, organization, brand, or individual.
I haven't eaten MacD's in decades, but why does it matter as a percentage? How much you're willing to pay should be dependent on how much it costs you to acquire the items yourself. For example, if the store is a 10 minute round trip and you value your free time at at least $30/hr then paying $5 for delivery is rational, regardless of the item's initial cost. Better than rational even, when considering fuel and vehicle wear-and-tear.
(Of course if you have a kitchen, equipment, and time then buying bulk ingredients and making your own meals is sometimes more efficient, but thats an argument against buying prepared food in the first place, not against getting it delivered.)