Hafas.Texts.himPriorities = {
'2' : 'Ausfall'
,'8' : 'Teilausfall'
,'16' : 'Zurückhalten von Zügen'
,'23' : 'Umleitung'
,'24' : 'Totalsperrung'
,'25' : 'Streckenruhe'
,'37' : 'Fahren auf dem Gegengleis mit Zs 8 oder Befehl'
,'60' : 'Umleitung unter erleichterten Bedingungen'
(function() { | |
'use strict'; | |
window.__REACT_DEVTOOLS_GLOBAL_HOOK__ = { | |
checkDCE: function() {}, | |
supportsFiber: true, | |
roots: new Set(), | |
inject() {}, | |
onCommitFiberRoot(rendererID, root) { | |
const current = root.current; | |
if (current.memoizedState != null && current.memoizedState.element != null) { |
unpacking 'https://example.com/nixexprs.tar.xz'...
tar: Error opening archive: Failed to open '/nix/store/411sszfqfya5ad2wllmqcr15z5d30575-nixexprs.tar.xz'
error: program 'tar' failed with exit code 1
Discussion:
/* | |
* Concept for emulating higher-kinded types using Flow. Instead of passing | |
* a type that has not been applied to parameters, this pattern passes | |
* a type-level function that will map a parameter type to the desired | |
* higher-kinded type applied to the given parameter. | |
* | |
* @flow | |
*/ | |
// a higher-kinded type is represented indirectly via a type-level function from |
#!/bin/bash | |
USER=${1:-sebble} | |
STARS=$(curl -sI https://api.github.com/users/$USER/starred?per_page=1|egrep '^Link'|egrep -o 'page=[0-9]+'|tail -1|cut -c6-) | |
PAGES=$((658/100+1)) | |
echo You have $STARS starred repositories. | |
echo |
/*<?php | |
//*/public class PhpJava { public static void main(String[] args) { System.out.printf("/*%s", | |
//\u000A\u002F\u002A | |
class PhpJava { | |
static function main() { | |
echo(//\u000A\u002A\u002F | |
"Hello World!"); | |
}} | |
//\u000A\u002F\u002A | |
PhpJava::main(); |
/* | |
* `match` is a helper function for writing pattern matches on types that are | |
* implemented using Scott encoding. | |
* | |
* @flow | |
*/ | |
export function match<A,B>(matcher: A): (match: (matcher: A) => B) => B { | |
return match => match(matcher) | |
} |
Reference: RFC 2616 - HTTP Status Code Definitions
- 400 BAD REQUEST: The request was invalid or cannot be otherwise served. An accompanying error message will explain further. For security reasons, requests without authentication are considered invalid and will yield this response.
- 401 UNAUTHORIZED: The authentication credentials are missing, or if supplied are not valid or not sufficient to access the resource.
- 403 FORBIDDEN: The request has been refused. See the accompanying message for the specific reason (most likely for exceeding rate limit).
- 404 NOT FOUND: The URI requested is invalid or the resource requested does not exists.
- 406 NOT ACCEPTABLE: The request specified an invalid format.
The notion of Compose keys are brilliant. I really like the notion of pressing a key, typing a sequence of characters, and out pops a pretty Unicode character. However, the default sequences in X are immensely silly, and in any case, there's already an RFC for this.
RFC 1345 exists to specify a simple way of entering Unicode characters, and it's a crying shame that Compose keys don't use it,
Bla bla bla this is my personal opinion bla bla bla.
Patents. Can’t live with violating them, can’t live without violating them. The entire concept of patented cryptography is a bit beyond what I have the energy to deal with right now. Whatever. We’re going in.
It didn’t click with me yesterday, reading the crypto news, that I had already quoted one Dan Brown with whom we are now concerned. No, not the one who wrote the novels. One of the other ones. I cited him in my timeline of trying to reconstruct where and when exactly Dual EC DRBG went so wrong. Specifically, the paper has a casual mention (bottom of page 7) that the proof of security relies on initialization value Q being random, because if it is not random, an adversary in-the-know can recover the prestates and everything’s downhill from there. Therefore – and I quote – it is generally preferable for Q to be c