0xACAB

Another consideration is that WordPress.org now has a built-in translation system for plugins distributed via their plugin directory, and it's become the recommended way to do i18n for plugins. So...

Hmm. If there's forwarding, you end up with six-degrees-of-separation issues - i.e. a friend of a friend might be an enemy. I know that if there is a forwarding feature...

> Hmm. If there's forwarding, you end up with six-degrees-of-separation issues - i.e. a friend of a friend might be an enemy. True, and see betterangels/better-angels#150 for more on how...

See d0042c1ba3c54ef8b6bbed5022ae4086306115b7 for the beginnings of a patch to address this.

CC'ing @mcverter, who's expressed an interest in helping with this process, too.

@hurtstotouchfire Have a look at #190, which is a PR for the first line item here (which I'm marking "done") because it "improves DOM spaghetti." All I've done is DRY...

@mcverter Look at #190.

Now that #204 is merged I think our next step with the Backbone stuff is to look at the remaining `.js` files and do the same sort of conversion that...

@hurtstotouchfire Also [the `suggest` field](https://getcomposer.org/doc/04-schema.md#suggest) in the `composer` schema: https://github.com/betterangels/buoy/blob/8c6fbd0bc9b09e89b2ea58965f3b8d16279905c5/composer.json#L38-L41 In fact, since we commit the `composer.json` file, the `WP_Buoy_Helper::checkLocalPluginStatus` method should probably be made [DRY](https://en.wikipedia.org/wiki/Don't_repeat_yourself)'er so it reads the...

Unfortunately this is a limitation of Safari. Buoy's livestream features are built on Jitsi, which itself uses WebRTC. Safari (famously!) does not support this capability. I think the quick-n-dirty solution...