fbender

(This is an extension to my proposal for the NetworkInformation.type enum at w3c/netinfo#9 to cover edge cases. Licensed as CC0 / public domain.)

Motivation

The Network Information API is designed to allow websites / WebApps to change their behaviour depending on the type of connection their device has. Discriminating by whether you are currently connected via WiFi or 3G, however, provides a footgun to developers: E.g. when you are roaming and tethering to your smartphone but your device indicates it's on a WiFi connection, you may assume that the user is on a high-bandwith, low-latency, low-cost connection

fbender

validInt = '^\d+$';
ri = regexp(value, validInt);

if size(ri, 2) == 1
  % integer
end

validDouble = '^(\d+(\.\d*)?|\.\d+)[dD][+-]?\d{1,3}$';
rd = regexp(value, validDouble); 

fbender

// License: MIT
// Wrote this to help me with merging two spreadsheets using a WinMerge diff report. This is in no way optimized.
// The report HTML only requires adding the JS and desired CSS for the toggled state, e.g.:
//     <style>span.toggled{background-color:lightcyan !important;}</style>
// Gecko-based browsers with context menu support have "Import" and "Export" items added to their context menu. 

"use strict";

function getNodes(selector) {
	var nodelist = document.querySelectorAll(selector);

fbender

Keybase proof

I hereby claim:

• I am fbender on github.
• I am fbender (https://keybase.io/fbender) on keybase.
• I have a public key whose fingerprint is 65AE C8A5 9890 99CC 951C 8CC2 38A5 7375 EFD0 B4D8

To claim this, I am signing this object:

fbender

Goals

• specify use cases of session management and persistence
• identify use cases of Cookies not concerning session management and persistence
• allow a website to act as an identity broker for other websites, (optionally?) factoring in OpenID/Persona/etc.
• replace Cookies with more user control and enhanced privacy (e.g. allow use case 1 below)
• find a technical solution for the EU Cookie Law resp. its goal
• propose HTTP Session & User Identification as an HTTP/2 extension (allow Cookie Upgrading?)
• propose HTTP Session & User Identification as a replacement for Cookies in HTTP/3
• the spec behaviour should be (largely) polyfill-able via Service Workers, i.e. user agent complies with spec even though it natively does not (requires complying server)

fbender

#!/bin/bash

# `wget` script to mirror / backup a site and its subressources even if they span across different domains
# 
# Author: Florian Bender
# Updated: 2015-08-31
# License: MIT
#
# Copyright (c) 2015 Florian Bender <fb+git@quantumedia.de>
#

fbender

#!/bin/sh
# mounts a folder to /var/discourse and installs bash (required by 
# Discourse launcher script)
#
# HOWTO:
# 
# 1. `docker machine ssh default` into the VM
# 2. `mkdir /mnt/sda1/var/discourse`
# 3. put this script at /var/lib/boot2docker/bootlocal.sh (this file 
#    will be persisted through reboots)

fbender

#!/bin/bash

# Copyright (c) 2013 Florian Bender
# License: MIT (see http://opensource.org/licenses/MIT)

function colorset {
	style=""
	case $1 in
		text)   style="0;3"  ;; ## regular text
		HItext) style="0;9"  ;; ## high intensity regular text

fbender

#!/bin/bash

# license: MIT
# author: Florian Bender
# original script: Sasquatch (https://forums.virtualbox.org/viewtopic.php?f=7&t=44337#p199593)
# see comment below!

version=$(vboxmanage -v)
echo -n "Installed: $version; "
var1=$(echo $version | cut -d 'r' -f 1)

fbender

function b64 = base64( str )
%BASE64 Encode string (array of chars) into Base64
%   Currently seems to fail for any input > 4 characters. :(
    
    %% Settings
    
    % Valid output codes to choose from.
    base64Chars    = char([65:90, 97:122, 48:57, 43, 47]); % +/ per RFC 2045 et al.
    %base64UrlChars = char([65:90, 97:122, 48:57, 45, 95]); % -_ per RFC 4648 §4
    base64PadChar  = '=';