robinhowlett

Seems like quite a complex solution for 500,000 concurrent users.

Why not just use Akamai for RTMP ingest and delivery? From my experience they can do all that was described and at scale.

I also created an SDK and CLI application for Mashape's Mockbin (http://mockbin.com/) service using Spring Social Bootstrap SDK and Bootstrap Shell:

* Spring Social Mockbin: https://github.com/robinhowlett/spring-social-mockbin

* Mockbin CLI: https://github.com/robinhowlett/mockbin-cli

Was playing the goal song through home audio system triggered too? How (or is it Mac's audio piped through speakers)? Great idea btw

We'd like to lead the Series A round please. We think the integration opportunities with our existing product are endless!

Sincerely, the Yo app investors

Would it plummet out of the sky if the wind dropped suddenly?

I met the executive driving this project earlier this year. He explained to me that Twitter only cares about one metric: growth.

In particular they are hyper-focused on signing up new Twitter users and then "on-boarding" them so that they can follow other users, posts tweets etc. within the first session. That means that products using the Twitter platform need to be focused on that too.

Twitter wanted to position themselves around three core features:

* the feed itself * the platform (recent third-party hooks/features such as voting (World Cup) and payments (Stripe et al) are part of this) * developer tools

It was explained to me that the latter was needed because too often Twitter felt that social/twitter features were "bolted on" too often at the end of projects, meaning that the integration was naturally segregated from the other features.

Twitter felt that for developers to create products that were inherently social, they would need to provide the tools to build those products themselves, and that social integration would be encouraged early in the product development cycle.

Fabric appears to be the first output of this strategy.

STATS was recently sold by Fox Sports and the Associated Press to the SF-based private-equity firm Vista Equity Partners. The rumored sale price was around $200M.

We work with STATS data daily and their products are excellent, albeit very expensive.

Very well done. I experimented once with Sports broadcast captioning (not real-time though; using YouTube videos) by using Amazon Mechanical Turk for crowdsourced closed-captioning.

An example is here: https://www.youtube.com/watch?v=MCgc1jAXGSk

I wouldn't be surprised if this scenario will be repeated within the free software tech community for other contentious issues. As we see with recent Supreme Court actions taken by Hobby Lobby, company leadership's personal viewpoints do influence people's relationships to those companies.

It appears the most vocal against Eich view, I imagine, same-sex marriage as a fundamental human right.

Will other topics go this way, like, for example, the "climate change" debate, especially as those topics evolve? There seems is a rising group of people who view skepticism/denial of catastrophic anthropogenic climate change akin to that level.

Mozilla's Manifesto doesn't speak to holding any particular viewpoint outside of promotion of a free, accessible Internet and free, open software.

However, the principle of "transparent community-based processes promote participation, accountability and trust" must have influenced both the internal culture and its users, who felt that Eich's actions didn't reflect their views. Chick-fil-a is in the reverse scenario but doesn't seem to experience this kind of thing.

I'm also seeing a nice change to using custom formulas/scripts.

Normally when I return a 2D array, most of the grid is results from the CONTINUE function - now it writes the actual cell value calculated.

This is a lot nicer for then sorting this data.

The island pivoted.

A. We know pretty well how he did it - all he needed to do was stay within the limits and there is considerable evidence that the UCI and testing labs were suggesting to him how to do that. When the UCI picked a max hematocrit number of 50%, it was an invitation to the athletes to dope up to that limit. When he came back to competition in 2009 & 2010, the USADA report clearly states that his blood passport profile shows almost certain non-legal manipulation.

B. He isn't being forced to do anything. He had the opportunity to challenge USADA's report in arbitration; he declined and again denied he had ever doped. Going on TV to speak with a talk-show host after you have retired is not a coerced move, especially to say that you have been lying for 15 years. Yes, he may want to return to some kind of competition (triathlons) and needs his life sentenced to be reduced to the minimum 8 years to do this. But oh look, he says the last time he ever doped was 2005 (not when he raced in 2009 or 2010, how about that?), which would mean he could return to sport in 2013.

C. George Hincapie never tested positive either, had an even longer career than Armstrong and was a long-time friend of Armstrong. He admitted to doping for years and testified against Lance. There's a rather simple truth here and it isn't driven by doubt and jealousy.

D. I'm not even sure what you are trying to say. But I imagine it is similar to arguments made before about scored rivals and journalists seeking vengeance. I've followed pro cycling for many years now; the truth is much more boring. The sport was rife with drugs, Armstrong would do anything to win and I don't think to this day he thinks he did anything truly wrong.

I watched the movie "Shattered Glass" two nights ago. It had this great scene:

Caitlin Avey: What the hell did you do to Steve? He called me from his car, hysterical. I asked him what was wrong, he said, "ask Chuck?" Chuck Lane: I fired him, okay? Not suspended, fired. Because this wasn't an isolated incident Caitlin. He cooked a dozen of them, maybe more. And we're going to have to go through them, you and I. We're going to have to go through all of them, now. Caitlin Avey: No, the only one was Hack Heaven. He told me that himself. Chuck Lane: If he were a stranger to you, if he was a guy you were doing a piece about, pretend that guy told you he'd only did it once. Would you take his word for it? Of course not! You'd dig and you'd bury him! And you'd feel offended if anyone told you not to.

I think it's easier to understand his argument when you think about the problem at scale. Consuming one API is meat and potatoes to most of us; with decent documentation and the REST style largely being followed, API clients can be created rather quickly.

However, if I asked you to consume 1000 "REST" APIs, this becomes problematic. There is no agreement on representation, nor is there metadata available to infer commonalities.

So what have people done? They've tried to introduce solutions from other "protocols". As mentioned in the article, HAL attempts to introduce a predictable envelope around the data, using links and embedded resources to become so HATEOAS friendly.

However, there still are holes. How do I know what to do with links? The rel can tell you only so much - back to the documentation we go. How about we introduce a rel to a schema, like XSD, WADL or JSON Schema? Not many have done that and even fewer enjoy working with them.

How about knowing if I can PUT or POST to one of these links? Well the API could support OPTIONS request, but does this suit your data intensive mobile app consuming the API? Not too snappy. We could list them out individually in the representation (thereby replicating the HTTP design through representation) but now the size of the representation is growing dramatically just to support metadata that rarely changes.

OData, GData and even CMIS have all tried to take a stab at data communication protocols. Yes, they bring solutions to some of these issues at the cost of complexity and verbosity. Plus, they use use discovery endpoints. And they still tend to fall back on XML over JSON because of use of Atom etc. And now we are halfway back to SOAP.

How about the versioning issue? Should client be aware of representation structure changes and adapt accordingly? Well WRML (http://www.wrml.org/) tried to take that one on and all the best to you if you read that through once and understand it, never mind implementing the actual clients and servers.

As ori_b summarized "REST isn't a protocol, it's a protocol pattern". REST can't fit all scenarios. But I think what's becoming clear is that no-one has found anything better, just more specialized. So the days of auto-building clients to consume APIs is far away.

I guess we'll just have to embrace the chaos and keep building snowflakes.

The HAL specification was created by Mike Kelly and a very readable introduction to it is here: http://stateless.co/hal_specification.html

We've been using it recently and we like it a lot.

It's interesting to see how many of the same anecdotes he reuses. I think this must be the fourth time I've heard him tell the "bicycle" story.

Kind of interesting I guess.

I find most of the repos I'm interested in on GitHub, so I've a Google Spreadsheet that calls the API and populates a sheet with all my watched repos' details - it's a pretty good way to filter and remember those good ideas you've seen.

The username is a variable so I also use it when interviewing people and seeing what kind of topics they are interested in. This could be used similarly.

This seems very similar to the Amazon Route 53 Alias record which I've found quite useful for pointing to ELB instances:

http://aws.amazon.com/route53/faqs/#Supported_DNS_record_typ...

Really nice! Reminds me of Apache Camel components + Content Based Router EIP as a service.

Subbu Allamaraju (ex-Yahoo, now eBay) has been the one proponent of REST that I believe speaks the most sense.

He understands that most "RESTful" APIs out there leave HATEOS as an afterthought, but he doesn't believe there is such a thing as a 100% RESTful API - you match the architectural style to the context of the problem you are trying to solve.

http://www.subbu.org/

Not to nitpick but the linked article's title is "NODE.JS - A GIANT STEP BACKWARDS?". That question mark is important.

I liked this - it was a clever but simple way to get the point across.

I concur, great example documentation like this makes it so much more appealing to dive into the library with clear goals and not worry about whether I'm using it correctly.

D3 looks very nifty - I'd like to investigate building a Google Motion Chart-type widget with it.

Ash Maurya (author of Running Lean) is also working on something similar called Lean Canvas (http://leancanvas.com/)

While it would be extremely difficult to detect or enforce, and generally the language around the law is very much designed with traditional working environments in mind, it is somewhat of a gray area legally in most countries.

I've received many different explanations over what's acceptable and, of course, many government documents will seem to contradict each other. However it is not beyond the possibility that one would run into a problem with this when dealing with some local authorities.

The other thing to keep in my is that residency is often tied to a minimum number of days spent within the country you are filing taxing in. They also can take into regard your "intent" of where you plan to be living next year. You can be judged to not actually fulfilling the residency requirements and be taxed on foreign earnings.

Most people who do this won't have issues but I've witnessed had one border agent mull over whether to deny entry or let them through, based on answers to questions about activities in other countries.

Disclaimer: this is not legal advice

I've used GV with my iPhone 4, HTC EVO 4G and HTC Hero. Also with SkypeIn/Out numbers.

Mirrors my experience, especially on iPhone: freezes often, messages can be delayed, unreliable voice service, voicemail transcription is rarely accurate. As soon as there is a problem and I have to switch to my carrier number, and confusion exists again.

I also run into the problem stcredzero describes; showing up as "Unknown", forcing me to move back to carrier number.

In short the biggest benefit I get from GV is actually the Chrome extension where I can send SMS messages very quickly and play voicemails (the transcription is usually useless) - really wish Apple would acknowledge that tying your phone to a browser is really powerful.

I've switched to giving out my GV number professionally and using my carrier number for close friends and family.

That vanity number is just not worth it.

Disclaimer: I am not an idiot and I understand how GV works.

Thanks very much for this. I'm new to the country and have been looking for this kind of info. Much cheaper than I expected.

It's right there in the FAQ.

"Why can't I view more pages from a specific book?

We help our customers discover and sample books to ensure that they'll be satisfied with their purchases. Our agreements with publishers and copyright holders currently limit how much of the book is available for preview. We continue to work with publishers to expand these limits."

But wasn't this the expected outcome by people who actually work in this industry and knew the type of oil being released into the Gulf?

From the sources I read, this is what they said would happen. But this didn't sell as well as the catastrophic view point.

The whole company. From the WSJ:

"Qatalyst Partners, the boutique firm run by veteran technology banker Frank Quattrone, has been hired to shop the Go Daddy Group Inc. ..."