Matei Stanca Ambient-Impact

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

Popular Drupal core src/ subdirectories

If you're writing a custom / contrib module, it can sometimes be helpful to see how Drupal core organizes its data.

The list in the file(s) below is generated with the following command...

  find . -type d -name 'src' -exec ls -F1 '{}' \; | sort | uniq -c | ggrep '/' | sort -r

... which looks for src/ folders, lists what is in them with a depth of 1, sorts the whole thing, filters them out to be unique (printing the number of duplicates), filters the list to only directories, and sorts the result in reverse (i.e.: so the biggest number comes first).

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

	# One liner
	wget --recursive --page-requisites --adjust-extension --span-hosts --convert-links --restrict-file-names=windows --domains yoursite.com --no-parent yoursite.com

	# Explained
	wget \
	--recursive \ # Download the whole site.
	--page-requisites \ # Get all assets/elements (CSS/JS/images).
	--adjust-extension \ # Save files with .html on the end.
	--span-hosts \ # Include necessary assets from offsite as well.
	--convert-links \ # Update links to still work in the static version.

	#!/bin/bash
	# Script to use custom ssh keys for various git repositories
	# Run without arguments to get usage info.
	#
	# How it works:
	# When used with SSH, git sends the path to the repository in the SSH command.
	# @see: https://github.com/git/git/blob/e870325/connect.c#L1268
	# We extract this info and search for a key with the name.
	# Based on the source, this seems to be used format since v2.0 at least.
	# @see: https://github.com/git/git/commit/a2036d7