Skip to content

Instantly share code, notes, and snippets.

Version 5 was not only a complete rewrite, but a complete re-imagining of the library, of its architecture, of its approach, of its goals.

A bit of history: versions 0 through 4 had a pretty simple goal: to work. Notify first started because I wanted to build cargo-watch. I never planned to write a cross-platform library spanning years of work and powering many different applications in the Rust world. I just wanted a tool that would recompile my code when I edited it. As time went on and more and more demand piled on Notify, the limitations of its humble beginnings and approach got to show.

Version 5 started as a technical redesign. And then I burnt out. Then I came back to it and re-imagined Notify with a focus on people instead. With a focus on well-being. Mine and others'.

The overarching goal of Notify is now to make it easy for people. For consumers: easy to use. For power users: easy to customise. For developers: easy to contribute to. For me: easy to manage and maintain.

The truth is:

  • I have
#![feature(custom_attribute)]
struct Something;
struct Bar;
trait SomeTrait {
type Result;
}
macro_rules! mac {
($some:ident, $my:ty, $mys:expr) => {
@passcod
passcod / oia-1718-0473.md
Created June 14, 2018 03:18
OIA response on the spelling of names for NZ citizens
  • Document dated 14 June 2018, received the same day.
  • Pasted here from the source PDF, with minor formatting.

You requested

  1. Any currently-applied policy or guideline to deciding which names are acceptable for New Zealand citizens, especially pertaining to the spelling of names. You are not interested in policies and guidelines around offensiveness, length, or resemblance to official rank and titles. You also clarified on 6 June 2018 that by ‘New Zealand citizens’ you are
// ==UserScript==
// @name BTD from_list mute filter
// @namespace http://tampermonkey.net/
// @version 0.1
// @description mm
// @author You
// @match https://tweetdeck.twitter.com
// @grant none
// ==/UserScript==
@passcod
passcod / javascript.json
Created February 24, 2018 04:32
Source (Balsamiq) of the JavaScript Map
{
"mockup": {
"controls": {
"control": [
{
"ID": "1",
"typeID": "Arrow",
"zOrder": "1",
"w": "36",
"h": "109",
const { permutation } = require('array-permutation')
const nouns = ['tucker', 'children', 'school', 'america', 'evil']
function verb (noun) {
return noun === 'children' ? 'are' : 'is'
}
function phrase ([ a, b, c, d, e ]) {
return `${a}: ${b} ${verb(b)} learning in ${c} that ${d} ${verb(d)} ${e}`
}
{
"version": "2.4.0",
"devDependencies": {
"babel": "^6.5.2",
"babel-cli": "^6.18.0",
"babel-preset-es2015": "^6.18.0",
"babel-preset-react": "^6.16.0",
"babel-preset-stage-2": "^6.18.0",
"babelify": "^7.2.0",
"bpb": "^0.2.2",
extern crate backend;
extern crate futures;
extern crate inotify;
use backend::prelude::*;
use backend::Buffer;
use futures::{Poll, Stream};
use inotify::INotify;
use std::path::PathBuf;
@passcod
passcod / dcloud.md
Last active May 24, 2016 02:40
Docker Cloud rant

I ranted about this on Twitter, @ah3rz advised me about these forums, so here goes, hoping the team sees it. Strong language ahead, I was (and still am) fairly upset.

Browser is Firefox, latest, on Arch Linux. Flash is not available, JS runs fine (I don't have noscript), I do have uBlock enabled with the default lists. Firefox's Tracking Protection doesn't detect (and block) anything. In the console, I see a bunch of HSTS errors, but it doesn't seem to be be affecting behaviour:

Strict-Transport-Security: The site specified a header that could not be parsed successfully.

Background: I use Docker Cloud both for managing my personal services (blog, various websites, irc bouncer, etc) and at work, for production and staging services, as well as a few ops tools. We have several dozen services across three nodes total, and probably will be doubling that in the next year. Not big, but not tiny, either.