Amio Jin amio

Overview of all `chrome://` pages.

This list may be out of date, for completely up-to-date information please refer to your browser's dedicated internal URL listing.

This list contains internal URL listings for Google Chrome and Microsoft Edge, the current most popular browsers based on the Chromium browser project. The Chrome URLs are current as of Chrome 127, whilist the Microsoft Edge URLs are still out of date.

List of Chrome URLs

chrome://about
chrome://accessibility
chrome://app-service-internals

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.~~

Using `<details>` in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here

Encoding Video

Installing

Install FFmpeg with homebrew. You'll need to install it with a couple flags for webm and the AAC audio codec.

brew install ffmpeg --with-libvpx --with-libvorbis --with-fdk-aac --with-opus

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

	import { h, Component } from 'preact';
	import Markup from 'preact-markup';
	import register from './preact-custom-element';

	// just a proxy component: WC -> Preact -> WC
	const A = () => <x-b foo="initial foo from <x-a>" />;

	// stateful component that can re-render
	class B extends Component {
	render(props, state) {

	function fish_mode_prompt --description 'Displays the current mode'
	# Do nothing if not in vi mode
	if test "$fish_key_bindings" = "fish_vi_key_bindings"
	switch $fish_bind_mode
	case default
	set_color --bold red
	echo 🅽
	case insert
	set_color --bold green
	echo 🅸

	[Unit]
	Description=Shadowsocks Server
	After=network.target

	[Service]
	ExecStart=/usr/local/bin/ssserver -c /etc/shadowsocks/ss-config.json
	Restart=on-abort

	[Install]
	WantedBy=multi-user.target

	#!/bin/bash
	sudo add-apt-repository ppa:chris-lea/libsodium;
	sudo echo "deb http://ppa.launchpad.net/chris-lea/libsodium/ubuntu trusty main" >> /etc/apt/sources.list;
	sudo echo "deb-src http://ppa.launchpad.net/chris-lea/libsodium/ubuntu trusty main" >> /etc/apt/sources.list;
	sudo apt-get update && sudo apt-get install libsodium-dev;

	[General]
	loglevel = notify
	skip-proxy = 127.0.0.1, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, 100.64.0.0/10, localhost, *.local, ::ffff:0:0:0:0/1, ::ffff:128:0:0:0/1
	bypass-tun = 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12

	# dns-server = 119.29.29.29,223.5.5.5,114.114.115.115
	# external-controller-access = [email protected]:6155
	# ipv6 = true

	// REMEMBER TO CHANGE THE external-controller-access' PASSWORD