| ** Public API v2 ** | |
| Usage: | |
| The API follows the general pattern of enumerating possible values of the | |
| subsequent path segment, with the fully qualified path yielding a json object | |
| of the type being enumerated. | |
| For example, /v2/colors will yield: | |
| [1, 2, 3, ... ] |
NOTE I'm trying to find the most optimal fav/touch icon setup for my use-cases. Nothing new here. Read Mathias Bynens' articles on re-shortcut-icon and touch icons, a FAQ or a Cheat Sheet for all the details.
I'd like to hear how you approach this: @valuedstandards or comment on this gist.
You have to include a boatload of link elements pointing to many different images to provide (mobile) devices with a 'favicon' or 'touch icon':
Google Chrome Developers says:
The new WOFF 2.0 Web Font compression format offers a 30% average gain over WOFF 1.0 (up to 50%+ in some cases). WOFF 2.0 is available since Chrome 36 and Opera 23.
Some examples of file size differences: WOFF vs. WOFF2
| // ==UserScript== | |
| // @name UTM param stripper | |
| // @author Paul Irish | |
| // @namespace http://github.com/paulirish | |
| // @version 1.2 | |
| // @description Drop the UTM params from a URL when the page loads. | |
| // @extra Cuz you know they're all ugly n shit. | |
| // @include http*://* | |
| // ==/UserScript== |
