@ChristopherA’s Lists of High-Signal, Low Noise Links

• Web View: https://christophera.github.io/Lists-of-High-Signal-Low-Noise-Links/
• GitHub upstream master: https://github.com/ChristopherA/Lists-of-High-Signal-Low-Noise-Links/blob/master/README.md

A series of annotated lists of opinionated, high-signal but low-noise links on topics I care about.

I also have a number of gists where I save raw lists of links, rough drafts and slightly annotated versions. I move them here when they have some level of maturity.

Table of Contents

• Table of Contents
• Support My Advocacy Efforts
• Lists
  • My Current Lists in Focus
  • All Lists
• Copyright & License
• Status & Versioning
• ToDo

Support My Advocacy Efforts

If you like my advocacy, my point-of-view, and my writing, as well as my travel to support local communities, my talks for those communities, and my work with organizations such as Blockchain Commons, Rebooting the Web of Trust, and the W3C Credentials CG, I invite you to sponsor me.

Plus, it's a way to plug into an advocacy network that's not focused on the "big guys". Most of the large corporations have full-time people representing their desires in the various standards orgs, making it hard for small companies and lone developers to fully participate. I work to represent smaller developers in a vendor-neutral, platform-neutral way, helping us all to work together.

You can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! Alternatively, you can support my efforts by sponsoring Blockchain Commons and our vision of the open web via a monthly GitHub Sponsorship or with Bitcoin via our BTCPay contribution page, Bitcoin contribution.

But please don’t think of this as a transaction. It’s an opportunity to advance the open web, digital civil liberties, and human rights together. You get to plug into my various projects, and hopefully will find a way to actively contribute to the digital commons yourself. Let’s collaborate!

-- Christopher Allen <ChristopherA@LifeWithAlacrity.com>, Github: @ChristopherA, Twitter: @ChristopherA

Lists

My Current Lists in Focus

Key Hashtags in List	Version
Gordian Envelope Links	Gist Minor Release 0.0.2 [2024-01-21]
#SSH #Signing #BestPractices	Gist Minor Release 0.1.0 [2024-01-17]
#Passkeys #WebAuthN	Gist Minor Release 0.1.0 [2024-01-16]

All Lists

Key Hashtags in List	Version
#COVID19	Index Stub
Gordian Envelope Links	Gist Minor Release 0.0.2 [2024-01-21]
#LocationPrivacy #ContractTracing #PublicHealthVsPrivacy #COVID19	Version 1.0.0 (2020, April 14)
#ImmunityCredentials #Verifiable Claims #COVID19	Version 1.0.0 (2020, May 27)
#Passkeys #WebAuthN	Gist Minor Release 0.1.0 [2024-01-16]
#SSH #Signing #BestPractices	Gist Minor Release 0.1.0 [2024-01-17]

Copyright & License

Unless otherwise noted (either in this /README.md or in a file's copyright section) the contents of this repository are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

I do not make any claims to the copyright of links or the list of links of themselves, only to my expression, organization, and annotations of them. However, if you use these significantly for your own work, I'd appreciate the attribution and link to my original list and that you would share your own annotated list under a similar license.

Status & Versioning

These lists are mostly for myself, my professional clients, and my GitHub Sponsors, as I've not found any bookmarking tool that quite does what I want. The content of these lists can change every day, and different sections will get more focus and attention, and thus evolve or even need major refactoring over time.

To make it easier to understand the status of any particular list, I use a modified form of Semantic Versioning.

Version Revision	Description	Example
Major	A significant reorganization of the previous edition, or even refactoring of content out to another list and thus a file name change. If the major revision is 0. it likely isn't in this repo but is a first draft in my gists. Once I have polished a gist enough I move it to this repo.	3.0.0
Minor	A significant new edition of this list is complete. A number of new links are added and some annotations are complete, maybe minor sections reorganized, a TOC, and some old links filtered out. I've likely moved on to focusing on a different list. If you see that a list version was set to 0.3.0 few weeks ago, the list is probably pretty current. If that 0.3.0 was a few months or even years ago, I may have added links, but I've not reorganized them or filtered old ones out.	0.2.0
Patch	Minor additions to the list. I've added some new links into the approriate section and have annotated them, but I've not reviewed or filtered the list a whole since the last Minor revision.	0.1.3
Raw	Here is where I vary from classic Semantic Versioning. Before I declare a new list is sufficient organized and annoted to be called 0.1.0, I will capture links and thoughts with little or no review or annotation. I may increment the least significant Patch level to let me know that this list may be ready for organization, annotation and filtering.	0.0.1
Index Stub	An empty topic hashtag that points to other topics	None

I only use this versioning approach for the individual lists. I do not use git release tags as they really don't work well for individual files inside a repo — only for a repo as a whole.

ToDo

• Add to top a short summary of what these lists should be in their ideal, for instance how a final results should lead the reader through a journey.
• Add section about methodology, the rubric for each stage.
• Needs style guide.
• Add section (or #SocialBookmarking list) about the vaours bookmarking tools and techniques that I use.
• Add section to list my supporters in the last quarter
• Add thanks to people like Vinay and Shannon who contributed effort.
• Where do I put related topic #HowTo:s? This repo, or another?
  • Also where of my gist tips, bio and vanity links, etc.
• Setup GitHub Actions
  • Markdown Link Checker
    • Install gaurav-nelson/github-action-markdown-link-check@v1
    • Investigate alternative markdown link checkers
    • Set up link-checker badge on each page
  • Markdown TOC Builder
    • Currently manually using https://ecotrust-canada.github.io/markdown-toc/
  • Markdown Lint
• [ ]