gregable

10 ms·

121.
by gregable 7y ago
Oh nevermind, the original url was archive.org apparently.
122.
by gregable 7y ago
Weird. The site is served by cloudflare and backed by an s3 bucket. Totally static. You shouldn't get forbidden unless cloudflare or your isp are doing something odd.
123.
by gregable 7y ago
That's a good point. It's not as though adding a little demand is likely to do anything other than increase supply in this case.
124.
by gregable 7y ago
I've sort of wondered if recycling plastics is actually maybe bad from a CO2 angle. It seems that using mined virgin oil for plastics that gets tossed in a landfill means that at least a little more of the oil we are mining ends up not
125.
by gregable 7y ago
Worth noting for anyone who thinks "why bother recycling", this is specifically about plastics. If you have metal, aluminum especially is a very valuable recyclable, so definitely keep recycling that.
126.
by gregable 7y ago
That's fair.
127.
by gregable 7y ago
I'm not sure I agree in the usual case. This is sort of what sourcemaps are for. Provide a link in a comment in the resource source to a prettified or at least non-minified version at a separate URL. The typical user won't need to
128.
by gregable 7y ago
I was curious about this. It looks like it has numerous individual plugins that provide the actual functionality. Do you know if some of the plugins are lossless, while others lossy? It may be possible to pick and choose the lossless ones.
129.
by gregable 7y ago
AMP documents are delivered with a Content-Security-Policy which instructs the browser not to load javascript resources outside the AMP origin, including inline scripts. The AMP Cache ensures no remote images or other remote resources can b
130.
by gregable 7y ago
Yes and no. The browser is making an HTTPS request to the AMP Cache for the document. The document's integrity is ensured by the cryptographic signature of the publisher's origin which the browser verifies. As far as the integrity
131.
by gregable 7y ago
It's also worth noting that the cache is necessary for prefetching. Without the cache, the prefetch would leak user's query intent to an origin that the user has yet to decide to visit. This would violate the user's privacy,
132.
by gregable 7y ago
This is a misunderstanding. Browser requests to ad and analytics networks are never proxied by the AMP Cache. They are made directly from your browser to the vendors listed. You can verify this in network tools. The AMP Cache proxies: AMP P
133.
by gregable 7y ago
See https://webmasters.googleblog.com/2019/04/instant-loading-am... which addresses the concern about the URL. You can see it for a number of sites already. For example, search for an AMP result from collins dicti
134.
by gregable 7y ago
#1 is being fixed for supporting browsers (Chrome so far). https://webmasters.googleblog.com/2019/04/instant-loading-am... You can see it for a number of sites already. For example, search for an AMP result from c
135.
by gregable 7y ago
If you encounter this again in the future, I'd love to take your bug report with the specific page in question. You can email me directly. My email is pretty easy to find from my profile.
136.
by gregable 7y ago
Locks are often fairly weak against real attackers. I enjoyed this youtube video of another smart (fingerprint?) lock being broken due to a digital reset. It has a plastic panel on the front where the fingerprint reader is. If you remove th
137.
by gregable 7y ago
The reason prefetching is particularly difficult to do for regular pages is the privacy implications. The act of preloading the page is a network event that is observable by the server serving that page. If the server is the same as the lin
138.
by gregable 7y ago
AMP hides the entire page to avoid what is known as a Flash of Unstyled Content (FOUC). The document unhides as soon as a single AMP javascript resource loads, or an 8s timeout if that fails. That javascript is very cacheable and is often a
139.
by gregable 7y ago
Do tenants really decide like that? Moving is costly and insulation is hard to judge on a tour?
140.
by gregable 7y ago
The intermediary (Google in this case) can choose not to serve an expired exchange.
141.
by gregable 7y ago
The share button simply calls the browser's share API, for example: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/s... > The Navigator.share() method invokes the native sharing
142.
by gregable 7y ago
If a Google search results page instructs your browser to request some bytes to preload from a Google server, that request does not reveal anything new to anyone. Google already knows it instructed your browser to preload, so knowing that y
143.
by gregable 7y ago
There is in fact some draft language around this kind of a mechanism to update a signature to extend the lifetime of the document by fetching a remote URL. See https://tools.ietf.org/id/draft-yasskin-http-origin-signed-
144.
by gregable 7y ago
Bandwidth increases do not fix latency. If a document has to round trip from the other side of the planet, that adds about 200 milliseconds until we break the speed of light. If that same document must make several round trips to be able to
145.
by gregable 7y ago
Good question. If you make a search query, but have not clicked on any results, you have a privacy expectation that the web servers of the search results you have not clicked on will not know you performed this query, your ip address, cooki
146.
by gregable 7y ago
Currently, it's difficult to implement however unlike rewriting a page in AMP, signing the page is a purely mechanical operation. All that's required is to improve the tooling, it is theoretically possible to be a one-click change
147.
by gregable 7y ago
This is true with TLS as well, though it also requires man-in-the-middling (MITM) the connection. MITM is usually rather easy compared to stealing a private key.
148.
by gregable 7y ago
I appreciate the comment. My goal here is simply to correct some of the misunderstandings about the format, rather than express opinions.
149.
by gregable 7y ago
AMP documents don't share user data with Google, which can be trivially seen by inspecting the network events that the page generates. If the publisher chooses, they can send logging to Google Analytics, but this is not part of AMP. Th
150.
by gregable 7y ago
Good question. The publisher signs an expiration timestamp in the Signed HTTP Exchange. The publisher can choose this timestamp and the browser will not respect signatures with expirations in the past. Note also that the specification requi

More ›