3 ms·

Can we just create a community standard of plain-jane HTML to separate it from all this "publisher" junk that AMP stands for, and then build a gigantic web ring

Can we just create a community standard of plain-jane HTML to separate it from all this "publisher" junk that AMP stands for, and then build a gigantic web ring and a search engine and all that? Like tilde club but with standards enforcement. I'd put a weather forecast site like that on my home screen in an instant.

wtbob 10y ago
> Can we just create a community standard of plain-jane HTML to separate it from all this "publisher" junk that AMP stands for, and then build a gigantic web ring and a search engine and all that? These guys might be a good first step: https://indieweb.org/ https://indieweb.org/
Animats 10y ago
Here's a possible set of restrictions: 1. HTML5, without syntax errors. UTF-8 only. 2. IMG and EMBED tags must have size info. 3. All CSS, Javascript, and font files must have subresource integrity hashes. The browser can cache anything with subresource integrity, even across site boundaries, since the hash guarantees the content value. This will speed up asset loading. No more loading "jquery.js" over and over. 4. All off-site content (ads, trackers, etc.) must go in iframes. All iframes must have a height and width, so rendering can proceed without waiting for them. This eliminates delays caused by slow ad servers. Iframe content is requested at a lower priority than main page content. 5. Rendering doesn't start until the entire main page is loaded, or a <page> tag is encountered for really long pages. Almost everybody has enough bandwidth now that we don't really need to frantically re-render as pages come in.
- flukus 10y ago
  Number 3 is already possible and widely used by minification frameworks. They generate a file with a hash in the filename that is cached forever. It cuts network time but browser still re-parse it every time.

3 ms·

Can we just create a community standard of plain-jane HTML to separate it from all this "publisher" junk that AMP stands for, and then build a gigantic web ring

by themodelplumber 10y ago

wtbob 10y ago
> Can we just create a community standard of plain-jane HTML to separate it from all this "publisher" junk that AMP stands for, and then build a gigantic web ring and a search engine and all that? These guys might be a good first step: https://indieweb.org/ https://indieweb.org/
Animats 10y ago
Here's a possible set of restrictions: 1. HTML5, without syntax errors. UTF-8 only. 2. IMG and EMBED tags must have size info. 3. All CSS, Javascript, and font files must have subresource integrity hashes. The browser can cache anything with subresource integrity, even across site boundaries, since the hash guarantees the content value. This will speed up asset loading. No more loading "jquery.js" over and over. 4. All off-site content (ads, trackers, etc.) must go in iframes. All iframes must have a height and width, so rendering can proceed without waiting for them. This eliminates delays caused by slow ad servers. Iframe content is requested at a lower priority than main page content. 5. Rendering doesn't start until the entire main page is loaded, or a <page> tag is encountered for really long pages. Almost everybody has enough bandwidth now that we don't really need to frantically re-render as pages come in.
- flukus 10y ago
  Number 3 is already possible and widely used by minification frameworks. They generate a file with a hash in the filename that is cached forever. It cuts network time but browser still re-parse it every time.