autonome

SMS and Privacy

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.

autonome

/*
* 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
*/

autonome

Biryani

Ingredients

• salt
• chili powder (mirch)
• turmeric
• raw cashews
• tomato
• onion

autonome

Text

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

autonome

body {
  font-family: -apple-system, BlinkMacSystemFont, 
    "Segoe UI", "Roboto", "Oxygen", 
    "Ubuntu", "Cantarell", "Fira Sans", 
    "Droid Sans", "Helvetica Neue", sans-serif;
}

autonome

[
  {
    "namespace": "showonlythesetabs",
    "description": "WebExtension API to show only some tabs on the tab strip.",
    "permissions": ["experiments.showonlythesetabs"],
    "types": [
      {   
        "id": "Tab",
        "type": "object",
        "properties": {

autonome

A-Frame orientation bug on Firefox Android

A-Frame no longer responds to device motion on Firefox on Android after Firefox version 53.

Cause

Kip removed Cardboard support in bug 1250244, which caused the problem. However, A-Frame orientation still works on other non-WebVR non-Cardboard mobile browsers.

Why doesn't the WebVR polyfill kick in and wire up orientation API support?

autonome

diff -U 8 Carthage/Checkouts.bak/magnet-scanner-ios/MagnetScannerIOS/ScannerBle.swift Carthage/Checkouts/magnet-scanner-ios/MagnetScannerIOS/ScannerBle.swift
--- Carthage/Checkouts.bak/magnet-scanner-ios/MagnetScannerIOS/ScannerBle.swift	2016-10-10 20:59:47.000000000 -0700
+++ Carthage/Checkouts/magnet-scanner-ios/MagnetScannerIOS/ScannerBle.swift	2016-10-10 22:37:29.000000000 -0700
@@ -48,17 +48,17 @@
     centralManager.stopScan()
   }
 
   deinit {
     stop()
   }

autonome

(*

To install:

1. Open Script Editor
2. Copy the code below into the editor
3. File > Save > Choose type "application"
4. Give a name you'll remember like "openChromeURLInFirefox"
5. Save to your Applications directory (so it can be indexed by Spotlight)

autonome

 function start() {
    navigator.mediaDevices.getUserMedia({ audio: true})
      .then(onMediaStreamHandler)
      .catch(function(error) {
        console.log('getUserMedia error: ', err);
      });
  }

  function onMediaStreamHandler(stream) {
    stream.onactive = function(e) { console.log('stream active', e) };