apisandipas

Creating share buttons with just URL's

Twitter

http://twitter.com/share?text=<TITLE>&url=<URL>

E.g. http://twitter.com/share?text=This+is+google+a+search+engine&url=https%3A%2F%2Fwww.google.com

Facebook

http://www.facebook.com/sharer.php?u=&p[title]=

Heydon

// Elements with `data-observe` toggle `data-visible`
// between `true` and `false`

if ('IntersectionObserver' in window) {
  const callback = (entries, observer) => {
    entries.forEach(entry => {
      entry.target.setAttribute('data-visible', entry.isIntersecting)
    })
  }
  

QWp6t

<?php

namespace Valet\Drivers\Custom;

class BedrockMultisiteValetDriver extends \Valet\Drivers\Specific\BedrockValetDriver
{
    /**
     * Determine if the incoming request is for a static file.
     *
     * @return string|false

DavidKuennen

(function (context, trackingId, options) {
    const history = context.history;
    const doc = document;
    const nav = navigator || {};
    const storage = localStorage;
    const encode = encodeURIComponent;
    const pushState = history.pushState;
    const typeException = 'exception';
    const generateId = () => Math.random().toString(36);
    const getId = () => {

nevillepark

CBC Radio Stream URLs

Using these URLs, you can listen to CBC radio streams with applications like VLC or Transistor. The files are M3U playlists, so you can use them as-is, edit them to suit your tastes, or use individual URLs.

This playlist contains the .m3u8 URLs from the CBC Listen website, which uses the HLS (HTTP Live Streaming) protocol. The audio stream is broken up into multiple tiny files, which are then fed into the .m3u8 playlist file that delivers them to your computer in the right order. This should work with modern media players.

This legacy playlist uses good old-fashioned MP3 streams found on PublicRadioFan.com. It will work with older programs like Winamp that don't support HLS. I don't know how lo

jkrems

JavaScript File Format Differences

There's the pervarsive notion that all JS is created equal and that there's only minor and easily detectable differences between the various file formats used to author JavaScript. This is correct, from a certain point of view.

For many people writing JavaScript that gets passed into build tools,

jvns

const fetch = require('node-fetch');
async function run() {
    let username = "YOUR USERNAME HERE";
    let password = "YOUR APP PASSWORD";
    let authBasic = new Buffer(username + ':' + password).toString('base64');
    let session = await (await fetch('https://jmap.fastmail.com/.well-known/jmap', {
        headers: {
            "Authorization": "Basic " + authBasic
        }
    })).json();