Update notes for 2016-10-25

This commit is contained in:
Alan Orth 2016-10-25 11:32:53 -07:00
parent cc3f2b2cbc
commit 3639434f47
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
5 changed files with 10 additions and 0 deletions

View File

@ -190,3 +190,5 @@ UPDATE 1
``` ```
- Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!) - Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)
- And now that I start looking, I want to fix a bunch of links to popular sites that should be using HTTPS, like Twitter, Facebook, Google, Feed Burner, DOI, etc
- I should look to see if any of those domains is sending an HTTP 301 or setting HSTS headers to their HTTPS domains, then just replace them

View File

@ -323,6 +323,8 @@ UPDATE 1
<ul> <ul>
<li>Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)</li> <li>Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)</li>
<li>And now that I start looking, I want to fix a bunch of links to popular sites that should be using HTTPS, like Twitter, Facebook, Google, Feed Burner, DOI, etc</li>
<li>I should look to see if any of those domains is sending an HTTP 301 or setting HSTS headers to their HTTPS domains, then just replace them</li>
</ul> </ul>

View File

@ -250,6 +250,8 @@ UPDATE 1
&lt;ul&gt; &lt;ul&gt;
&lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt; &lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt;
&lt;li&gt;And now that I start looking, I want to fix a bunch of links to popular sites that should be using HTTPS, like Twitter, Facebook, Google, Feed Burner, DOI, etc&lt;/li&gt;
&lt;li&gt;I should look to see if any of those domains is sending an HTTP 301 or setting HSTS headers to their HTTPS domains, then just replace them&lt;/li&gt;
&lt;/ul&gt; &lt;/ul&gt;
</description> </description>
</item> </item>

View File

@ -250,6 +250,8 @@ UPDATE 1
&lt;ul&gt; &lt;ul&gt;
&lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt; &lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt;
&lt;li&gt;And now that I start looking, I want to fix a bunch of links to popular sites that should be using HTTPS, like Twitter, Facebook, Google, Feed Burner, DOI, etc&lt;/li&gt;
&lt;li&gt;I should look to see if any of those domains is sending an HTTP 301 or setting HSTS headers to their HTTPS domains, then just replace them&lt;/li&gt;
&lt;/ul&gt; &lt;/ul&gt;
</description> </description>
</item> </item>

View File

@ -249,6 +249,8 @@ UPDATE 1
&lt;ul&gt; &lt;ul&gt;
&lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt; &lt;li&gt;Getting rid of these reduces the number of network requests each client makes on community/collection pages, and makes use of Font Awesome icons (which they are already loading anyways!)&lt;/li&gt;
&lt;li&gt;And now that I start looking, I want to fix a bunch of links to popular sites that should be using HTTPS, like Twitter, Facebook, Google, Feed Burner, DOI, etc&lt;/li&gt;
&lt;li&gt;I should look to see if any of those domains is sending an HTTP 301 or setting HSTS headers to their HTTPS domains, then just replace them&lt;/li&gt;
&lt;/ul&gt; &lt;/ul&gt;
</description> </description>
</item> </item>