Goal

Add Content Security Policy (CSP) and Subresource Integrity (SRI)

• Ensure there is no inline JavaScript
  1. ca3d270
  2. 3d4cf25
• Ensure there is no inline CSS
  1. ac21a7b
  2. 63b5c62
• Add and verify CSP & SRI
  • not including upgrade-insecure-requests as it interferes with local development
  • not including block-all-mixed-content as it interferes with local development
  • 24ddffa

Resources

• Content Security Policy
  • Report URI: Generate your Content Security Policy
  • Ensure CSP is effective against XSS attacks - web.dev
  • Add CSP to github pages
  • brycejech/Content-Security-Policy: Guide for using Content-Security-Policy HTTP header for Cross Site Scripting (XSS) defense
  • Content-Security-Policy - HTTP | MDN
• Online JavaScript tools
  • Online JavaScript beautifier
  • ESLint Demo - ESLint - Pluggable JavaScript linter
  • JSLint: The JavaScript Code Quality and Coverage Tool
• Subresource Integrity
  • Subresource Integrity - Web security | MDN

Resolve issues identified by web.dev/measure:

Impact	Category	Audit/Guide
High	Performance	Eliminate render-blocking resources
Medium	Performance	Remove unused CSS
Medium	SEO	Document does not have a meta description
Low	Accessibility	Background and foreground colors do not have a sufficient contrast ratio
Low	Accessibility	Links do not have a discernible name

Investigate structured data

Schema Markup Testing Tool | Google Search Central | Google Developers

Description

I would like to change the default branch to main. However, that is not currently supported by GitHub Pages.

Rationale

Master-slave is an oppressive metaphor that will and should never become fully detached from history. Aside from being unprofessional and oppressive it stifles participation

(1.1. Master-slave - Terminology, Power and Oppressive Language)

While not everyone may interpret a git master branch as representing a "master-slave" metaphor, it is not unreasonable for anyone to do so:

First appearance of "master" in git is in a CVS helper script[1]:
git/git@3e91311

Why is that branch called master? Probably because BitKeeper uses
"master" for its main branch:
http://www.bitkeeper.org/tips.html#_how_do_i_rebase_my_work_on_top_of_a_different_changeset

But maybe this "master" isn't the same one that's in "master/slave"?
See the documentation about
master/slave repositories:
https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/HOWTO.ask#L223

But repositories and branches aren't the same! They are in BitKeeper:
https://users.bitkeeper.org/t/branching-with-bk/158/2

So, yes, the "git master" branch probably isn't even a "master copy"
reference, but a straight up master/slave reference.

(Re: Replacing "master" reference in git branch names (was Re: Proposal:)

Continuing to use master as a default branch name is unwelcoming of too many.

Additional context

• Easily rename your Git default branch from master to main - Scott Hanselman
• Terminology, Power and Oppressive Language
• Additional proof that it has been a "master-slave" metaphor since the beginning:
  • 'Re: kernel.org and GIT tree rebuilding' - MARC (2005 email from Linus Torvalds to git mailing list)

Issue

When I post blog entries to FB, the CC BY-SA image is used, cropped square. It looks terrible.

Solution

Provide Open Graph metadata.

Resources

• The Open Graph protocol
• Facebook
  • Images in Link Shares - Sharing
  • Sharing Debugger - Facebook for Developers

Replace Unlicense with CC0.

Also see:

• Don’t use the Unlicense, an inferior license with an atrocious name - an article by Chris Morgan
  • Hacker News discussion: The Unlicense is an inferior license wrapped in an atrocious name | Hacker News
• May I apply CC0 to computer software? If so, is there a recommended implementation? - CC0 FAQ

  Yes, CC0 is suitable for dedicating your copyright and related rights in computer software to the public domain, to the fullest extent possible under law.

• Using CC0 for public domain software - Creative Commons
• Creative Commons Zero v1.0 Universal | Software Package Data Exchange (SPDX)