-
Look for text you can remove. If text is on your slide, people will be spending time reading it instead of listening to you, especially if the text is not in their native language. The text should almost entirely come from you.
-
Often, text in your slides is text you're already going to say anyways. Remove any text you are going to say anyway, unless it's an important title or section change.
-
When using acronyms, make sure to explain them on first use.
-
Wall of text: Often I've seen a slide that is a beautiful or useful image, followed by a slide that is a wall of text on the same topic. Move all text into speaker notes, and have just one slide with the image.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
body { | |
font-family: -apple-system, BlinkMacSystemFont, | |
"Segoe UI", "Roboto", "Oxygen", | |
"Ubuntu", "Cantarell", "Fira Sans", | |
"Droid Sans", "Helvetica Neue", sans-serif; | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
* Do not remove the @namespace line -- it's required for correct functioning | |
*/ | |
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set default namespace to XUL */ | |
/* | |
Disable tab throbber to stop battery death. | |
https://bugzilla.mozilla.org/show_bug.cgi?id=1422090#c67 | |
*/ |
There are a few problems with delivering alerts via SMS, but they mostly boil down to this: SMS is not very private.
For vulnerable audiences, it’s preferable to not collect any subscriber information at all. This isn’t possible with SMS, because you have to know the recipient’s phone number to deliver a message. Unless you’re talking about burners—which most people won’t have—that phone number is tied to a real identity. This is a vulnerability in at least these scenarios:
- If the alerting app itself gets targeted (whether by LE or other malicious actors), user-identifying information could be leaked.
- Phone companies cooperate with LE, through legal process (subpoenas) or otherwise, to find out which phone subscribers are receiving SMS alerts.
- LE , IC, or well-resourced hackers snoop on the SMS network.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name | subscribers | ageinyears | |
---|---|---|---|
/r/programming | 1003937 | 12 | |
/r/technology | 6005355 | 10 | |
/r/learnprogramming | 517081 | 8 | |
/r/javascript | 227797 | 10 | |
/r/webdev | 208237 | 9 | |
/r/node | 54220 | 8 | |
/r/reactjs | 47536 | 4 | |
/r/learnjavascript | 40905 | 5 | |
/r/frontend | 32008 | 6 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"coliseum": { | |
"name": "Veterans Memorial Coliseum", | |
"location": { | |
"latitude": "45.532141", | |
"longitude": "-122.6693299" | |
}, | |
"link": "https://goo.gl/maps/sPJe9UY5Nqs" | |
}, | |
"mainstage": { |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
function build(callback) { | |
Metalsmith(__dirname) // __dirname defined by node.js: | |
// name of current working directory | |
.metadata({ // add any variable you want | |
// use them in layout-files | |
sitename: "foo", | |
siteurl: "https://foo.com/", | |
description: "Website!", | |
generatorname: "Metalsmith", | |
generatorurl: "https://metalsmith.io/" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<dietrich> asuth: do you know anything about whether indexedb should be available for pages that are non-http/s protocols? looks like it worked until 63. | |
<dietrich> (or who would know?) | |
<mconley> dietrich: maybe bevis? | |
<asuth> dietrich: Are you actually creating origins under new protocols? Many things won't like that. | |
dietrich: QuotaManager won't create directories for origins it doesn't understand. Here's the "okay" list: https://searchfox.org/mozilla-central/source/dom/quota/ActorsParent.cpp#8462 | |
<asuth> dietrich: In particular, are the protocols implemented via https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/protocol_handlers? Because if so I'd expect the semantics to conform to those of https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers | |
dietrich: And in particular the clause ```User agents must throw a "SecurityError" DOMException if the resulting URL record has an origin that differs from the origin specified by the relevant settings objec |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wget \ | |
--recursive \ | |
--no-clobber \ | |
--page-requisites \ | |
--html-extension \ | |
--convert-links \ | |
--restrict-file-names=windows \ | |
--domains yourdomain.com \ | |
--no-parent \ | |
--no-cache \ |