alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-11-22 06:35:03 +01:00
Code Issues Projects Releases Wiki Activity

Update notes for 2016-10-25

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/post/2016-10.md
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!)
- 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

2
public/2016-10/index.html
View File

@ -323,6 +323,8 @@ UPDATE 1
<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>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>

2
public/index.xml
View File

@ -250,6 +250,8 @@ UPDATE 1
&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;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;
</description>
</item>

2
public/post/index.xml
View File

@ -250,6 +250,8 @@ UPDATE 1
&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;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;
</description>
</item>

2
public/tags/notes/index.xml
View File

@ -249,6 +249,8 @@ UPDATE 1
&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;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;
</description>
</item>