This should be implemented at the browser level, not in a webpage.
Show HN: Make your site’s pages instant in one minute
151–160 of 361 posts
Re: Show HN: Make your site’s pages instant in one minute
#152Earlier quoted context omitted.
The part about viewing family.html seems kind of understandable. If you assume no bad actors, then it's crazy... But we're all developers here, we know that you have to assume the existence of bad actors, and assume that they are going to target you (which is why we you always validate data client data server-side). I could see how viewing family.html could turn into a real headache for HR/Legal, especially if the la…
We're talking about evidence in a discrimination court case that points to an IP address associated with a company that visited /family.htm around the time someone applied for a job they didn't get. Like, that person went through their blog's access.log when they got home, defeatedly looking up IP addresses, and going "aha, jackpot!"? And everyone in the company hovers links to be sure they don't go to /as-a-black-ma…
Yes, I can't see how anyone could think this is sane in any sense. Brb putting my kids in my GitHub profile picture.
Re: Show HN: Make your site’s pages instant in one minute
#153Re: Show HN: Make your site’s pages instant in one minute
#154Earlier quoted context omitted.
Enabling it by default Internet-wide seems like it could be a bad idea for many reasons. If I go out of my way to enable it on my site, I am taking responsibility for the bandwidth and any side-effects of prefetching a link and understand what I am doing. But if it is simply enabled Internet-wide, isn't that bordering on a DDoS? What about poorly-coded websites/apps where GETS are not idempotent or have side-effects?…
> What about poorly-coded websites/apps where GETS are not idempotent or have side-effects? They're already broken, exposing that is a good thing.
Vulnerable isn't broken
Re: Show HN: Make your site’s pages instant in one minute
#155Works very well for me. dieulot, is there a small bug with the allowQueryString check? const allowQueryString = 'instantAllowQueryString' in document.body.dataset I think should be: const allowQueryString = 'instantallowquerystring' in document.body.dataset If I have: then 'instantAllowQueryString' in document.body.dataset === false and 'instantallowquerystring' in document.body.dataset === true because html data att…
Uppercase is converted to added dashes. `document.body.dataset.instantAllowQueryString` corresponds to `data-instant-allow-query-string`.
Re: Show HN: Make your site’s pages instant in one minute
#156Reminds me of this optimization by Netflix: https://medium.com/dev-channel/a-netflix-web-performance-cas...
The talk (https://www.youtube.com/watch?v=V8oTJ8OZ5S0) was one of the most watchable performance optimization talks I've seen.
TLDR - they used a combination of the link prefetch technique, which works for HTML but is not fully supported by all browsers, as well as XHR prefetching, which will work for prefetching Javascript and CSS.
Re: Show HN: Make your site’s pages instant in one minute
#157Nice idea for HTTP/1.x, however, isn't this what HTTP/2.0 [1] is meant to achieve by pushing components at the user?
Re: Show HN: Make your site’s pages instant in one minute
#158Live demo on my website @ https://sysadmincasts.com/
Temporary added it in-line for testing. I was already in the sub 100ms level but this just puts it over the top! Also updated all admin add/edit/delete/toggle/logout links with "data-no-instant". Pretty easy. Open developer preview and watch the network tab. Pretty neat to watch it prefetch! Thanks for creating this!
ps. Working on adding the license comment. I strip comments at the template parse level (working on that now).
pps. I was using https://developers.google.com/speed/pagespeed/insights/ to debug page speed before. Then working down the list of its suggestions. Scoring 98/100 on mobile and 100/100 on desktop. I ended up inlining some css, most images are converted to base64 and inlined (no extra http calls), heavy cache of db results on the backend, wrote the CMS in Go, using a CDN (with content cache), all to get to sub 100ms page loads. Pretty hilarious when you think about it but it works pretty well.
Re: Show HN: Make your site’s pages instant in one minute
#159Is this kind of like turbolinks which Basecamp uses?
Re: Show HN: Make your site’s pages instant in one minute
#160I've been testing it for the past 30 minutes or so and found that it doesn't cause the same problems that InstantClick did. (Which was javascript errors that would randomly occur.) I'll limit it to a small subset of users to see if any errors are reported but there is a good chance this could go live for all logged in users. Maybe even all website visitors if all goes well. Seems to have no impact on any javascript,…
> Just make sure you apply the data-no-instant tag to your logout link, otherwise it'll logout on mouseover. Logout links should never be GETs in the first place - they change states and should be POSTs.
POSTs are not Links. And Logout service is indempotent even if you can consider it changes the state of the system