4 ms·
That 9-hop shortening example is disgusting, I wonder if that could be alleviated by introducing some protocol: 1. Make all shortening services append a `This-
by xpressvideoz 4y ago
That 9-hop shortening example is disgusting, I wonder if that could be alleviated by introducing some protocol:
1. Make all shortening services append a `This-is-a-shortening-service: true` header to all the responses they send.
2. When a link is added to a shortening service, check if the response from the link has the header above and resolve the destination, recursively.
- westurner 4y agoawesome-url-shortener: https://github.com/738/awesome-url-shortener https://github.com/738/awesome-url-shortener /? shorturl api OpenAPI https://www.google.com/search?q=shorturl+api+openapi https://www.google.com/search?q=shorturl+api+openapi - TinyURL OpenAPI: https://tinyurl.com/app/dev https://tinyurl.com/app/dev - GH topic: url-shortener: https://github.com/topics/url-shortener https://github.com/topics/url-shortener A https://schema.org/Thing https://schema.org/Thing may have zero or more https://schema.org/url https://schema.org/url and/or https://schema.org/identifier https://schema.org/identifier ; and then first the ?s subject URI that's specified with the `@id` property in JSONLD RDF. You can add string, schema:Thing, or URI tags/labels with the https://schema.org/about https://schema.org/about property.
- citrin_ru 4y agoIt's disgusting but unfortunately it's not a bug - it a feature which allows each redirect hop to collect (and sell/use) some data about you.