seen from Macao SAR China
seen from Türkiye
seen from United States
seen from Poland
seen from China
seen from Russia
seen from Germany
seen from Portugal
seen from United States
seen from United States
seen from Portugal
seen from Russia
seen from Portugal
seen from Portugal
seen from United States
seen from United States
seen from Germany
seen from United Kingdom
seen from China
seen from Malaysia
Intersection of API documentation and Search optimisation
I have long said that APIs are more than just payload definitions. For public APIs or those being made available within large organisations, where discoverability and making it easy for APIs to be adopted are just as important to the definition of the API. API specification standards such as Open API Specification and Asynchronous API Specification have addressed some of the challenges, the…
Web Bot Auth
Block all bots is officially outdated. Web Bot Auth is a new IETF backed standard that lets AI agents carry a cryptographic ID card so websites can verify who is legit and who is just scraping your content.
In my latest TechGlimmer post, I explain: - How Web Bot Auth actually works (keys, signatures, directories) - Why Cloudflare, AWS, Fingerprint & SEO tools are jumping in - What this means for creators, e‑commerce, and security
Read it here:
https://techglimmer.io/what-is-web-bot-auth-web-bot-auth-explain/
¿Quién es el dueño de Internet?
A menudo, al navegar por la red, nos preguntamos: ¿quién controla todo esto? ¿Existe un “dueño” de Internet? La respuesta, aunque sorprendente, es más sencilla de lo que parece: nadie posee Internet.
Internet no es una empresa, ni un país, ni siquiera un solo servidor. Es una red global de redes interconectadas, creada por gobiernos, universidades, empresas y personas. Funciona gracias a acuerdos técnicos y normas compartidas, no por la autoridad de una sola entidad.
¿Quién gestiona entonces Internet?
Aunque no hay un dueño único, sí existen organizaciones clave que ayudan a que Internet funcione de forma ordenada:
- ICANN (Internet Corporation for Assigned Names and Numbers): gestiona los nombres de dominio (como .com o .org) y las direcciones IP. - IETF (Internet Engineering Task Force): desarrolla los protocolos técnicos que permiten que los dispositivos se comuniquen (como HTTP o TCP/IP). - ISOC (Internet Society): promueve el desarrollo abierto y el acceso equitativo a la red. - Gobiernos y empresas: regulan aspectos legales o comerciales dentro de sus jurisdicciones, pero no controlan la infraestructura global. ¿Por qué importa esto?
Entender que Internet es un recurso colectivo nos ayuda a valorar su neutralidad y a exigir su uso responsable. No pertenece a una compañía o gobierno, sino a todos los que la usamos —y por eso, todos tenemos la responsabilidad de cuidarla.
WEBCAST JUL 30 - ISOC Trinidad & Tobago - The Internet Engineering Task Force (IETF): Opportunities to Build the Internet
LIVESTREAM |PARTICIPATE VIA TEAMS | ADD TO CALENDAR | PERMALINK On Wednesday 30 July 2025, at 5pm-6pm AST (13:00-14:00 UTC) the Internet Society Trinidad & Tobago Chapter hosts a webinar ‘ The Internet Engineering Task Force (IETF): Opportunities to Build the Internet‘. University students (Tech, Law, Policy, Mgmt), IT pros, engineers, digital policy minds, and curious Internet users with a…
Someone paid a voice actor to read this particularly pedantic internet standards document, as passive aggressively as possible
Search IETF mail list archives
This specification provides a way for an ephemeral or transactional OAuth 2.0 client to signal to the AS that the client does not ne
The short version of the process goes like this:
Client makes a PAR request with a special client_id value to trigger this (we’ll use “dynamic” in the example but it’s a fixed string that’s always the same for all clients). The request includes its redirect URI and optionally any other DynReg client metadata, and can also include any keys and challenges for PKCE and client auth
AS returns a request_uri like normal PAR, but this creates an internal transaction that is bound to the parameters sent in (1)
Client calls the authz endpoint with the request_uri and the special client_id value, “dynamic”
AS loads the configuration based on the request_uri and processes the request as usual
AS returns the “code” and anything else relevant, as usual
Client calls the token endpoint with the code, PKCE verifier, proof of its keys from (1), and the client_id value of “dynamic”; could include a DPoP/MTLS proof too
AS loads the approved request from the “code” value and processes it as usual
AS returns a token as usual
Client uses the token as usual
Search IETF mail list archives
When requesting a specific resource, a resource server could use this protocol to tell the client that it needs an access token with specific authorization_details which the client can then obtain before requesting the resource again.
just in case you want to send a picture and receive a request
The Hypertext Jeopardy Protocol (HTJP) inverts the request/response semantics of the Hypertext Transfer Protocol (HTTP). Using conventional
