Adam Brault

We believe WebRTC is one of the most important technologies to hit the web in many years. There is a significant opportunity for WebRTC to help deliver on the promise of the open web—but for communication and collaboration.

In several of our colleague Henrik Joreteg’s talks the past couple years, he’s said, “WebRTC needs more Open Web hackers!” It’s very true.

But WebRTC is much more complicated than other browser APIs that web developers deal with.

It seems, from our vantage point, like a large portion of the users of WebRTC have not been Open Web hackers.

Continue reading »

Marcus Stong

At &yet we have become big fans of CoreOS and Docker, and we’ve recently moved a bunch of our Node applications there.

We wanted to share a little tidbit for something that seems like it should be easy, but ended up being a minor stumbling block: making CoreOS’s Etcd cluster available in Docker.

Here’s a little background for those not up to speed on CoreOS or Etcd. CoreOS bills itself as “Linux for Massive Server Deployments.” CoreOS is usually deployed with Etcd, “a highly-available key value store for shared configuration and service discovery,” giving servers in a cluster the ability to share configuration data. We have been using Etcd and Confd for some time, so we naturally thought: “wouldn’t it be cool to configure applications and services within Docker from Etcd?”

Continue reading »

Mike Speegle

Hey folks! It’s the holiday season, the goose is getting fat, the decorations are filling the air with glimmery goodness, and the yeti is plodding through the snow with gifts for all its web-loving friends.

But oh no! What if it doesn’t know where to go?!

The yeti could shower its gifts onto the twitters, sure, but then how would it know you received it? It could leave it on this here blog, but what if–gasp–you FORGET? You might accidentally leave the yeti’s gift out in the cold, cold snow where it could develop abandonment issues.

Continue reading »

Mike Speegle

First: so hey, it looks like our novel, Something Greater than Artifice, was selected as a Kirkus Reviews Indie Book of the Year!

Which is nice.

So are badges

Second: which means that the message behind the book is getting out there.

Which is even better.

Because Something Greater than Artifice, while being a sci-fi romp through the countryside featuring futuristic tech and faceless villains and people getting punched square in the face, represents something greater than the sum of its parts.

Because silos

We at &yet believe in a free and open web, and we support that idea by making open source projects based around the idea that siloization is bad, and that sharing is good. And sometimes we make cool apps like Talky and share all the fundamental components we used to make it!

Continue reading »

Eric Zanol

Enterprise Week is the name of a week-long activity for high school seniors in the Pasco School District. It’s loosely affiliated with Washington Business Week, which is our state’s incarnation of a program that many states run aimed at exposing young folks to the business world.

During Enterprise Week, every senior from the three high schools in the district are pulled out of school and dropped into their “offices” in a local convention center. Volunteers from the local business community are asked to be a “Company Advisor” for each group of about a dozen students. I volunteered to be one, and I had no idea what to expect.

Continue reading »

Henrik Joreteg

Henrik follows up on his “Opinionated rundown of JS frameworks” blog post with a presentation at FFConf, in which he explored topics related to single-page apps, including:

  • Should we build apps that require JavaScript to run
  • What is a “native web app”?
  • What about progressive enhancement?
  • The performance implications of clientside apps
  • Twitter’s move away from clientside back to server-rendered
  • The two classes of web apps
  • User expectations of modern applications
  • Installable web apps
  • True offline support for web apps: ServiceWorker
  • Isomorphic (dual-rendered) applications
  • Picking tools for a rapidly changing environment

Continue reading »

Peter Saint-Andre

Yesterday Fippo talked about applying the principles of the open web to realtime communication with WebRTC. Consider this post the first installment of providing in-depth descriptions of what that means in practice.

Where codecs fit in

A key component of realtime audio and video systems (like Talky) consists of methods for encoding the light waves and sound waves that our eyes and ears can understand into digital information that computers can process. Such a method is called a codec (shorthand for code/decode).

Because there are many different audio codecs and video codecs, if we want interoperability, then it’s important for different software implementations to “speak the same language” by having at least one codec in common. In the parlance of industry standards, such a codec is specified as “mandatory to implement” or MTI (often an MTI codec is a lowest common denominator, but software can use better codecs if available - a model that has also worked well for cipher suites in SSL/TLS and other technologies.)

Continue reading »

Philipp "Fippo" Hancke

There’s a lot of talk about this topic of “the web we want,” and a lot of it has focused around WebRTC lately.

I have been working with WebRTC since mid-2012, both in the Chrome and Firefox browsers, as well as the native library. So far I have filed more than sixty issues in the WebRTC project issue tracker and the Chrome bugtracker. I’m especially proud that I’ve crashed the production version of Chrome eight times.

I am among the top non-Google people to file WebRTC issues. And I managed to get quite a few of them fixed, too. I visited Google’s Stockholm office in September and had a conversation with the team there about how I use the issue tracker and how that process works. Full disclosure: I got a t-shirt (even though it turned out to be too large). And I even started reviewing the Chrome WebRTC release notes before they’re sent out.

Continue reading »

Nathan "Nlf" LaFreniere

For those of you who don’t know, hapi is a web framework with a rapidly growing community led by Eran Hammer.

Over the last month, a lot of work has gone into it to prepare for the release of version 8.0.0. hapi 8 represents the biggest release since the start of the framework, and with it come quite a few changes.

No more packs

That’s right, those confusing pack things are gone. If you used them, though, don’t worry. The functionality still exists, just in different ways. Instead of a pack that contains servers, we now have a server that contains connections. You can still create a server with multiple connections, but if you only need one; everything will feel much more straightforward and intuitive.

Continue reading »

Mike Speegle

As a semi-official part of the &yet Blog Team and a super-official, semi-professional antagonizer, I spend a lot of time kicking in office doors and demanding that people write things. Some of those folks (once they’ve come to the realization that I will not stop making this pose in their doorframe)


…will buckle down and whip out some words about JavaScript or Node or NodeScript or JavaNode or BackBonemBerGular or whatever in a jiffy, and if only to dislodge my presence from their immediate vicinity for one more day. Others flatly refuse, and that’s okay too.

Continue reading »