| on GET /notes | |
| fetch the 20 most recent notes filtered by tag | |
| show as h-feed | |
| on GET /notes/new | |
| the user must be an admin | |
| show autofilled note-form | |
| on GET /notes/{id} | |
| fetch note |
An h-media card describes a single media stream or multiple media streams.
<p>Conceptually, <span class="h-media">Mylo Xyloto</span> is a concept album, and a thematic rock opera.<p>Conceptually, <a class="h-media" href="//wikipedia.org/wiki/Mylo_Xyloto">Mylo Xyloto</a> is a concept album, and a thematic rock opera.
| Trying to get WebRTC DataChannel to work via STUN. |
Adam Brault, the “producer and creator” behind Realtimeconf, announced shortly after it was over that this one was the last. I have a hard time believing that. Maybe the next &yet conference will have a different theme or different branding, but I’m incredulous that anyone who has that much energy and passion for bringing the tech community together can resist the urge for long.*
Throughout the weekend, it was obvious that Adam and the entire (massive) team behind Realtimeconf was incredibly excited about making a unique, compelling experience. They didn’t have to put everyone in the same hotel, but doing so made it easier to have the impromptu encounters that are critical for forming relationships. They could have left us to disperse for dinner Friday night, which would have resulted in people who already knew each other cliquing up and going out alone. Instead, the team provided dinn
So, promises are the big thing now in JavaScript and all that shit. Though they are a fairly old concept. In short using promises means you're giving up on your dependency on time and mutable state, and buying into dependency on your data, regardless of time, or structure, or any of those unnecessarily complicated things.
First, let's build a conceptual understanding of promises, and then I'll show how this maps to the particulars of the Promises/A+ specification. A promise is a placeholder for a value. Instead of saying what your value depends on through your program structure, i.e.: doX(a); doY(a); ... you say what the value depends on through other values. ie.: b = doX(a); c = doX(b); — here b depends on a; and c depends on b, which depends on a.
Or, a more "visual" representation of this would be:
var a = Promise();
b = a.then(doX);
When you build a community you're creating a culture. That culture will be about more than the code, the modules, or the language. The people you draw in will have their own biases and behaviors that impact the kinds of people you continue to draw as you grow.
Cultures will naturally fight behavior that is divisive. That is, behavior that is divisive to the established members of that community. As a community grows larger it is harder and harder to change what the culture finds acceptable because changing it, even if it is inclusive in nature, is disturbing and divisive to existing membership. Fighting for change in established cultures means dealing with a lot of dismissive language and attacks for the "tone" of your argument.
That is why it is so important that a culture becomes comfortable with aggressively fighting exclusionary behavior. While it is certainly more beneficial to make pro-active steps to increase diversity we cannot be dismissive of the effect that passionate reactions to poor behavior
Libertarianism when applied to the social and political structure of technology and open source (Meritocracy) perpetuates inequality by failing to acknowledge the role of power and current state of inequality.
American libertarianism is uniquely American, unfortunately Silicon Valley happens to be in America. It is a political and social philosophy that believes individual ownership and power should supplant collective ownership of any kind. Most immediately the ownership and interventionist powers of government should be dismantled and the free market should be left with the responsibility of creating equality and individuals expected to protect their own interests.
Filtered through the lens of technology this becomes a more unified theory of Meritocracy. Being that we don't trade goods for currency we don't have a traditional market and libertarians must invent one. A strange mix of experience, social capital, and skill are a sort of currency in technology communities. Merit
Today, there is no reliable way to persist metadata for digital media as it travels across the internet.
Mine is working to build a global content registry on top of the Bitcoin blockchain to serve as an open metadata layer for canonical representations of digital media.
The goal of such a registry is to enable a new decentralized hypermedia protocol that powers the next generation of digital content applications, where creators and consumers to own their media, identity and interactions across the internet, without dependency on industrial or platform gatekeepers.
In March, we published a high level summary of how such such a system could work, titled the Canonical Content Registry. Today, we are taking the first steps to start building it by sharing a proposal for a technical implementation on top of Blockstore. We welcome your feedback and look forward to starting a conversation.
I've been building a number of parsers in Rust lately while studying or doing code challenges. One of my side projects that involved parsing is weechat-notifier. I set about building the parser in the most intuitive way to me as a primarily JavaScript developer these days.
Before we get into the mistakes I made, lets talk about the protocol I'm parsing. The
| From b716088dbc674ef205d68b90fd5b33266892974c Mon Sep 17 00:00:00 2001 | |
| From: Myles Borins <mborins@us.ibm.com> | |
| Date: Sat, 28 Nov 2015 14:27:17 -0800 | |
| Subject: [PATCH] Smell Ya Later Anti-Feature | |
| --- | |
| src/message.c | 2 +- | |
| 1 file changed, 1 insertion(+), 1 deletion(-) | |
| diff --git a/src/message.c b/src/message.c |