You have a repository, call it alice/repo. You would like to transfer it to the user bob, so it will become bob/repo.
However, you make heavy use of the GitHub Pages feature, so that people are often accessing https://alice.github.io/repo/. GitHub will helpfully redirect all of your repository stuff hosted on github.com after the move, but will not redirect the GitHub Pages hosted on github.io.
| // Implements stale-while-revalidate | |
| self.addEventListener('fetch', event => { | |
| const cached = caches.match(event.request); | |
| const fetched = fetch(event.request); | |
| const fetchedCopy = fetched.then(resp => resp.clone()); | |
| // Call respondWith() with whatever we get first. | |
| // If the fetch fails (e.g disconnected), wait for the cache. | |
| // If there’s nothing in cache, wait for the fetch. | |
| // If neither yields a response, return a 404. |
| get_latest_release() { | |
| curl --silent "https://api.github.com/repos/$1/releases/latest" | # Get latest release from GitHub api | |
| grep '"tag_name":' | # Get tag line | |
| sed -E 's/.*"([^"]+)".*/\1/' # Pluck JSON value | |
| } | |
| # Usage | |
| # $ get_latest_release "creationix/nvm" | |
| # v0.31.4 |
| <script src="https://unpkg.com/@webcomponents/custom-elements"></script> | |
| <style> | |
| body { | |
| margin: 0; | |
| } | |
| /* Style the element from the outside */ | |
| /* | |
| fancy-tabs { | |
| margin-bottom: 32px; |
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.
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.
| # This would go into .bash_profile, .bashrc, .zshrc, etc. | |
| # Script to start the gpg-agent - in it's own file as it is also used when the machine starts up | |
| # Be sure to update the path to wherever you place this file! | |
| # Note, depending on shell you may not need this line enabling, if the global daemon is already running | |
| # OK. Some shells complain, others don't! | |
| ~/bin/startup-gpg-agent.sh | |
| # GPG | |
| if [ -f "${HOME}/.gpg-agent-info" ]; then |
| /*! Microsoft EdgeHTML 13.10586 | Copyright (C) Microsoft. All rights reserved. */ | |
| address { | |
| display: block; | |
| font-style: italic; | |
| } | |
| article { | |
| display: block; | |
| unicode-bidi: embed; |
brew install gnupg, pinentry-mac (this includes gpg-agent and pinentry)
Generate a key: $ gpg --gen-key
Take the defaults. Whatevs
Tell gpg-agent to use pinentry-mac:
$ vim ~/.gnupg/gpg-agent.conf
| #!/bin/bash | |
| LOCALADMIN="username" | |
| kickstart=/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart | |
| echo "Configuring Remote Management" | |
| if id -u $LOCALADMIN >/dev/null 2>&1; then | |
| echo "Defined local admin account exists" | |
| # Deactivate ARD agent, deny all access | |
| echo "Deactivating ARD agent" |
A Pen by Chris Coyier on CodePen.