Tootfinder

Nine #HTTP Edge Cases Every #API Developer Should Understand
https://blog.dochia.dev/blog/http_edge_cases/

I have a question for anyone who happens to be knowledgeable about web standards:
The same way we had the (failed?) "DoNotTrack" header... Is there any working group or initiative working on an #HTTP header sent by the browser (or similar mechanism) to signal that the user wants an ecological/lightweight website? Something like "SaveEnergy" or "LowEnergy", or "LightweightMode".
Would it make sense? Or do you foresee that it would fail for some specific reasons?
P.S.: Of course I would prefer if we didn't have to signal our discontent with the unjustifiably big and unoptimized web pages that we are served.
P.S.2: Now I am feeling tempted to write a browser extension for people who want to use "alternative communication channels" (HTTP headers) to "yell" arbitrary stuff at certain websites (It would be glorious if we could coordinate a big "Fuck you, Google", or, in a more positive tone, "Free Palestine!").
#WebDevelopment #WebDev #Web #Ecology

RE: #HTTP since HTTP/1.1 was released in 1997!…

🛠️ Monitor logs & events: user prompts, tool results with accept/reject decisions, #API requests with detailed cost/duration/token counts, error tracking with retry attempts & tool decision patterns
⚙️ Setup options: Launch via #VSCode or terminal with environment variables, configure centralized #OTLP exports via #gRPC or #HTTP protocols, use administrator-managed settings for organization-wide control