muaddirac

Is the damage American Football causes to its players a valid reason for disliking the activity?

I got really into mechanical keyboards but found that I was pretty quickly sated after getting an ErgoDox (http://ergodox.org/).

Now I subscribe to updates from these two particularly interesting community projects and may consider buying them when they're available:

Axios (improving ergodox): https://geekhack.org/index.php?topic=44940.0

Reviving the DataHand: https://geekhack.org/index.php?topic=41422.0

Otherwise, after a few months of reading forums, it's hard to get excited about a new color of keycap.

I assumed they were using the other meaning of intelligence, as in "signal intelligence"

I would also point out that API Blueprint allows you to describe your API responses with json schema. They sit at different levels - blueprint for specifying urls resources are accessed with, and json schema for validating the payload.

I work in an open space (when I'm in the office), and the uncomfortable feeling of people walking by and glancing at my screen is the main reason I dislike working in the open.

The panopticon metaphor is apt - I feel uncomfortable taking well-deserved minute-long breaks when I have no privacy.

I do the same thing - NAS to store media, with plex running on my laptop (which is always on anyway) chromecast on my tv and the plex app on my phone to control everything. Definitely feels like the future, but like you I'd be curious to know how this setup compares to others.

It's pretty interesting to see this in picture form, but it wasn't a big secret that you could eat a days worth of calories in a single meal in most chain restaurants.

The comparison to home-cooked at the end is a little ridiculous. A 22oz steak will be a lot of calories whether you cook it at home or have it at a restaurant. They intentionally picked healthier options for the home meal, and always included large sugared drinks or milkshakes with the fast food options. It would be interesting to see the same article, but comparing each individual meal at a restaurant with a home-cooked version of the same meal (and I'd imagine you'd mostly be shaving off a couple hundred calories unless you're really messing with the ingredients.)

I read those when I was younger as well. I came away not a huge fan of the series because of the (in my opinion) poor writing and huge plot holes.

Why didn't he just bless the kid with "May you be a killer of Galbatorix, and may no one else die in the process."

You can set up multiple DNS providers before the DDOS attack begins.

It's kind of funny that even in glassblowing circles this myth gets propagated...where the old methods of making panes are generally well known and understood (see the picture of the crown glass in the article).

It doesn't directly, but for example I run plex on my network and I can stream all of my local files to the chromecast with the plex iOS app.

Only tangentially related, but: It would be interesting to consider physical(ish) methods of federated authorization.

Hand the valet a key fob that you've enabled for use within a 1 mile radius and two car starts?

I went there in college (went for the physics, stayed for the fun science room) - what I remember most was an exceptionally well-built Chladni plate that you could control.

"At least 80% of all audio calls, not just metadata, are recorded and stored in the US."

It definitely seems like he meant that 80% of calls are recorded and stored. Whether that's true or not will (hopefully) come out in time.

It does sound really cool. I just don't get why the shorthand part is important. Why not jot "grandma" and "poodle" and then tap the pen there for when the interviewee starts talking about his grandma and his poodle.

I guess I was thinking in the context of the author using this particular pen for shorthand - it records audio, so even if he's just writing shorthand, it's still recording.

Really good points though, it didn't occur to me that someone would be willing to go "on the record" but not be actually recorded.

There are some other solutions that use keyboards that wouldn't be as intrusive as a keyboard or tablet (and may be something to consider for you personally if you have a disability in only one side); things like portable one-handed chorded keyboards: http://www.handykey.com/ and http://chordite.com/

I don't see the utility of shorthand anymore. If you're just taking short notes, you don't need to write 225wpm...and if you've recorded everything, then you can listen to the recording later and take notes or type up a transcript verbatim.

It would seem better to learn a stenography system so you don't waste time inputting actual text, which surely you would need to do anyway? (How is the time the author saves writing in shorthand not negated by the time it takes her to type it up afterwards?) I guess if you knew shorthand and steno, you could do everything pretty quickly.

> The tweet was in shorthand, but was transcribed as follows.

I like this and hope other news sites start to do this as well.

This is awesome because I like Mou but it had some pretty big pain points:

- Large files caused it to slow unbearably/crash

- Scroll tracking was terrible (TexWorks is the only similar thing I've seen that does it well).

It looks like these aren't necessarily fixed in MacDown 0.1, but at least there's the opportunity to improve it with time.

Thank you for this. I find explanations that eschew category theory bizarre, this really cleared things up for me (having spent a lot of time with functors mathematically, and almost no time with them in a programming context).

My eyes just really don't see any of the mice in these photos as "beautiful," least of all the Apple Pro Mouse.

These sorts of things are so subjective. Where the author sees an homage to the marbles he played with as a kid, the glare reminds me of a J.J. Abrams lens flare, distracting from the environment rather than blending in.

HTTP methods, status codes, and headers are all you need to understand for developing at the level of HTTP APIs.

It's impressive that it can run in a browser now.

When I try in chrome on OSX, the main document fails to load text. Still, with a little more polish, I could see actually using this (a fully annotated, interactive wikipedia would be a neat demo).

I never trust apple keynote benchmarks, but I was really holding out for the swift ones to be true.

It probably makes no difference in the majority of common iOS/OSX development, though.

Looks nice, but doesn't play well with autocomplete in chrome (tab completing my name didn't show up on the card)

In the long term, if all cars are autonomous and communicating, it's reasonable to think that most situations could be handled by carefully coordinated group action so that no one is injured. (Especially in the example given in the article - if only one car has a problem, the others should compensate.)

In the near term, though? For legal reasons it might be necessary to hand control immediately to a human driver to let them make the decision.

Or perhaps far, far more stringent inspection requirements could help mitigate some of this?

I read this comment, and was searching for something unrelated when I found this:

http://www.newscientist.com/article/mg21028115.400-talk-with...

and decided to report back.

"PRIVATE AND CONFIDENTIAL. DO NOT DISTRIBUTE."

Right on the first (nineteenth?) page. Nice!

Very good points, and you've corrected a misconception I've had for a while now.

Still think my original point stands - that this UI decision isn't so different from entering a service for the first time.

> To solve that, you need a more stable addressing system instead of just not using addresses at all

I think this is generally solved with wishy-thinking and redirects.

> I think you are confusing discoverability with navigation.

I'm not. I understand why it's hard to swallow though, because I think a valid criticism of the REST architectural style is that it removes bookmark-ability.

> It's good if you can discover all content through hypermedia, but why should you prevent direct access?!

Well, precisely because direct access implies that out-of-band knowledge is driving the interaction rather than hypermedia. I would refer you to Fielding's discussion of the topic[0] where he notes:

> A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types that are appropriate for the intended audience (i.e., expected to be understood by any client that might use the API). From that point on, all application state transitions must be driven by client selection of server-provided choices that are present in the received representations or implied by the user’s manipulation of those representations. The transitions may be determined (or limited by) the client’s knowledge of media types and resource communication mechanisms, both of which may be improved on-the-fly (e.g., code-on-demand).

> It's like saying that there should be an indes in every book (yes!), and therefore you should not ever tell anyone on which page of the book they can find something relevant (wtf?).

Interacting with a web service/site is not like interacting with a book (or a physical address), because there is no permanence as there is with physical objects. Have you never tried to go to an old bookmark to find that the content has been moved (and you get a nice 404)?

Anyway, I wasn't saying that this is all A Good Thing, just that the change in chrome doesn't seem at all at odds with REST (however, as many have pointed out, it can be at odds with usability)

[0]:http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...