Embedding via // without explicit SSL should probably be considered harmful or malicious as there is no reason to make such scripts available without SSL. Even if the end website is not using SSL users can still fetch your script securely.
No! You should NEVER load javascript over https on a page that was served over http. It gives a false sense of security that doesn't exist. Because the source page was served over http, the source page can be modified by an attacker, making the script be loaded under ssl makes you think its protected. But its not since an attacker could just modify the script tag to remove the https bit in transit then modify the scr…
Show HN: Make your site’s pages instant in one minute
71–80 of 361 posts
Re: Show HN: Make your site’s pages instant in one minute
#72This is very nice idea, but isn't the problem initial liad time most of the time? How could we solve that? Does this also work for all the outgoing links as well? I don't want to improve other sites rendering time at the expense of my own. Very cool regardless.
Off the top of my head, a good way seems to be to write better sites that don't include 10mb of javascript libraries.
Re: Show HN: Make your site’s pages instant in one minute
#73Earlier quoted context omitted.
I think it would only prefetch GET links, which never have side effects.
There's nothing stopping GET requests from having side effects. It's like pointing to a list of best practices and saying "everyone surely follows these." For example, someone changed their signature to `[img]/logout.php[/img]` on a forum I posted on as a kid and caused chaos. The mods couldn't remove it because, on the page that lets you modify a user's signature, it shows a signature preview. Good times.
> It's like pointing to a list of best practices and saying "everyone surely follows these."
It’s not a ‘best practice’ it’s literally the spec for the web.
Re: Show HN: Make your site’s pages instant in one minute
#74Many people browse the web from an employer who has rules about what types of pages may be accessed. For example, a person applying for a job with my team may include a link to a web page about their job-related background -- portfolio.html or whatever. HR tells us to be sure we don't follow links to any other page that may be more personal in nature, such as a page that reveals the applicant's marital status (which…
Any companies with such onerous policies could block sites like instant.page at the firewall.
Re: Show HN: Make your site’s pages instant in one minute
#75Each time you hover over a link it's doing a GET request bypassing the cache (cache-control: max-age), even if you hove the same multiple times. Also this will make all your analytics false... Except that indeed this can improve greatly the user sensation of speed
The analytics should only be triggered is the page is rendered, assuming it's done client side. I believe Google does this for first top 3 results if I'm not mistaken.
What would be a good way to avoid prefetch requests in your analytics if you only derive analytics from server access logs?
Re: Show HN: Make your site’s pages instant in one minute
#76Many people browse the web from an employer who has rules about what types of pages may be accessed. For example, a person applying for a job with my team may include a link to a web page about their job-related background -- portfolio.html or whatever. HR tells us to be sure we don't follow links to any other page that may be more personal in nature, such as a page that reveals the applicant's marital status (which…
Re: Show HN: Make your site’s pages instant in one minute
#77Earlier quoted context omitted.
There's nothing stopping GET requests from having side effects. It's like pointing to a list of best practices and saying "everyone surely follows these." For example, someone changed their signature to `[img]/logout.php[/img]` on a forum I posted on as a kid and caused chaos. The mods couldn't remove it because, on the page that lets you modify a user's signature, it shows a signature preview. Good times.
I think it was a joke as GET requests are not supposed to change anything, but often they do (probably because many devs don't know about, understand or respect the RESTful concept). EDIT: For completeness, I have to add, that I am also part of the group of people who have violated that concept. Maybe neither frequently nor recently, but I did it too :-/
It's nothing to do with REST. It's part of the HTTP spec and has always been, that "GET and HEAD methods should never have the significance of taking an action other than retrieval".
Re: Show HN: Make your site’s pages instant in one minute
#78A problem with the loading instructions is that it reveals, to an unrelated site, every single time any user loads the site that is doing the preloading. That is terrible for privacy. Yes, that's also true for Google Analytics and the way many people load fonts, but it's also unnecessary. I'd copy this into my server site, to better provide privacy for my users. Thankfully, since this is open source software, that is easily done. Bravo!
Re: Show HN: Make your site’s pages instant in one minute
#79Many people browse the web from an employer who has rules about what types of pages may be accessed. For example, a person applying for a job with my team may include a link to a web page about their job-related background -- portfolio.html or whatever. HR tells us to be sure we don't follow links to any other page that may be more personal in nature, such as a page that reveals the applicant's marital status (which…
Re: Show HN: Make your site’s pages instant in one minute
#80Many people browse the web from an employer who has rules about what types of pages may be accessed. For example, a person applying for a job with my team may include a link to a web page about their job-related background -- portfolio.html or whatever. HR tells us to be sure we don't follow links to any other page that may be more personal in nature, such as a page that reveals the applicant's marital status (which…