autonome

const https = require('https');

const token = process.env.AIRTABLE_TOKEN;

const url = 'https://api.airtable.com/v0/apptAzTf0HPbYkCbn/Responses'

const options = {
	headers: {
    'Authorization': 'Bearer ' + token

autonome

<style>   

html, body, div, a-scene {
  background-color: transparent;
}

#video {
  /* overrule a-frame default styles */
  width: 100% !important;
  max-width: 100% !important;

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

wget \
     --recursive \
     --no-clobber \
     --page-requisites \
     --html-extension \
     --convert-links \
     --restrict-file-names=windows \
     --domains yourdomain.com \
     --no-parent \
     --no-cache \

autonome

<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

autonome

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

autonome

{
  "coliseum": {
    "name": "Veterans Memorial Coliseum",
    "location": {
      "latitude": "45.532141",
      "longitude": "-122.6693299"
    },
    "link": "https://goo.gl/maps/sPJe9UY5Nqs"
  },
  "mainstage": {

autonome

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