ripperdoc

This looks very nice! I completely agree with the frustration that so few stands/mounts are considered for multipurpose use, which is strange as I feel iPad is really designed for it (TV remote on a stand, photo frame on the wall, charging on the desk, in the kitchen, etc). This looks like a close to perfect way of solving it.

Only thing lacking is charging, but that is a minefield for sure with new cable connector.

Apple should build on their strength, and in this case, it's apps. Presume that in iOS7, they launch a new API that "forces" apps to expose searchable data in a lexical format that Siri understands. Basically, giving apps "intent" and "content", and let Siri play with it. Google has a difficult task, because it searches EVERYTHING - but if Siri (mainly) searches just what you have installed, it is already at a much better hit rate, and the apps can not only serve information but also take actions.

If they don't let Siri interwork with apps, I cannot see how it will ever go beyond setting alarms...

What people are reacting to is the posed threat, or creepiness, of something. And what we should ascertain is whether being filmed is creepy. Being followed by a man not behaving according to social rules is an obvious possible threat that hardly needs to be proven, but how creepy it is to be surveillanced is another and more interesting point to prove.

So the experiment should be redone to factor out the creepy man. That means, either have a trusted and passive person do the filming (police, reflex-vest, etc) or to set up a tripod with a camera. Even if it was made clear that the video would be streamed to public, I think very few people would react as they did above, simply because a film camera is a lot less threatening than an unknown, weird person.

Dressing up the cameraman in different clothes and behavioural patterns would emphasize this point further. If he seem to be a tourist, a store employee, etc he would be judged less of a threat.

It's not double standard to judge creepy cameraman differently than CCTV, it's simply a rational conclusion that the cases are different.

This seems to be a paper from the leader of the study, giving some more details: http://www.mit.edu/~medard/papers2011/Modeling%20Network%20C...

All networks can have packet loss, and the ones we use more and more (the wireless ones) certainly have a higher packet loss rate. Not sure what you are suggesting should be done?

Nice analysis, but only half of the story. As pointed out in the comments, you can make thick or thin clients in both native and HTML5. The issue is rather the one about lowest common denominator. HTML5 aims at working in very varied "runtime environment", where standards are bendable, bugs are rife and feature support a few years behind what native could muster. HTML5 is more difficult, and does not have all the tools, of the native environment. So the question is rather - will HTML5 develop faster than native and thereby be on par with it, or will it always be the straggler?

For what it's worth, one of Sweden's major newspapers recently did an investigative article about the use of Google Analytics in so many websites belonging to banks, government institutions, political parties, etc. It's now being investigated by privacy authorities. http://www.dn.se/ekonomi/webbsidor-avslojar-ditt-besok-for-g...

Why Pyramid instead of Flask or Bottle?

Sorry for going off-topic, but I tried to open this on iPhone and it never finished loading. It's 1.25 MB for one page of 3500 chars of text. Maybe the ratio of polish vs content is a bit too skewed here?

A great interface, but I see one huge omission - a place to discuss or comment the patterns. A pattern doesn't live in vacuum, it is good under certain circumstances and bad in others. So the pattern is only valuable to me if it comes with an explanation of what it's trying to achieve and why it looks the way it does. Link it up to Stackoverflow or at least throw in some basic commenting function and this would be a useful tool.

Not just you. My pet peeve is that their sharing links gadget on the right side covers the scroll bar on at least Chrome. So, the scroll handle can get stuck under the links. Not very smart.

I'm just wondering who thought it was a good idea to put some share links hovering ABOVE the scroll bar. http://imgur.com/xF5UP

I don't know how many times I have lost the scroll handle behind it when this widget is used.

Seems like a good time to switch to Usenet here then - not watertight but much less likely to get into trouble (at least I'm ready to try that theory). Anyone know a good Usenet provider for Japan based connections?

I heard from a source that it's has to do with the extreme space and weight constraints of the iPhone 5, but that Apple wants to put it in eventually. But I am more concerned with the ecosystem - it's not just enough to put it in the phone, Apple needs to make super-easy to sign up for, both as provider and user.

Comparing with laptops isn't really a fair game, as they have stopped adding features for years and simply improve on speed. Smartphones are in the middle of a very strong development curve, where we find ourselves with portable computing platform we haven't yet figured out all possibilities of.

Clearly, other companies are prepared to ship with less preparation than Apple, but Apple would not have been where they are with the iPhone if their only reasoning was to "deliver a faster replacement phone at the end of contract". They innovated on iOS, app-marketplace, Siri (still being worked on...) and Airplay, to mention a few. All of them replacing similar too-early-too-crappy competitor innovations.

That the iPhone 5 did not add "one more thing" either means Apple does not think it's necessary (exposing themselves, like Nokia did, to the risk of the "next Apple" showing up with a great re-innovation), or because they couldn't get it done in time or with the technology available (which means they should invest more in R&D - they can afford it).

I'm very happy Apple both innovates and puts the bar high - I'd rather have good NFC from Apple than ok NFC from Google. It's good for users. For the time being, I will give them the benefit of the doubt that the new stuff - NFC, fingerprint, new batteries, etc - is simply not mature enough yet. But if Apple stops trying, they won't be able to sustain their curve. Android is already grabbing most new users - at which point will they start grabbing iPhone users?

Looks nice, can you set their color and apperance using clases in the same way as normal Bootstrap buttons, e.g .btn .btn-primary, etc?

Take every piece of software and OS, and you will find conflicting views of whether it goes faster or slower with time. You buy a new device, everything feels snappy, but one year down the line, things feel slow. But the problem is, this is based on expectations, based on hardware, based on usage pattern, etc.

What we need is a objective software speed measure based in UI terms (because that is what people in the end notice). Such as "time to start" and "time to get to usable state". This should be measured automatically after each build, and normalized to hardware. Only then can both developers and users see hard evidence that software, e.g. Chrome, is now running slower than before. Because the cost of adding a feature is otherwise invisible to the developer, while the user's keep getting into anecdotal discussions of what is faster or slower, comparing wildly different hardware capabilities.

And to add a few points: - When you don't have network access and the device is at the limit of storage space (so that a major state changing operation couldn't be undone), for the love of god, get the user to connect it first. Let it back up it's state to computer or network. Don't allow situations which cannot be rolled back.

- A lot of apps and iOS features sync with the network. Will need a little work to make sure a restored local state doesn't interfere with the network state. It's solvable.

One of the most user friendly additions to software, ever, is the undo button. (if you want to feel how it is to use software without, try Linux in terminal for a while ;) ). And one of the best attempts to do this on a OS scale, is Time Machine. It should be as easy as bringing up a prompt and step or scroll backwards in time. You are really just stepping between data states. If you restore a state, it will merge with current state and step forward (which of course can be undone). You can decide to restore only one app, and thereby limit impact.

Update, restore, "are you sure you want to do this?", "pick the right destination", etc are user unfriendly concepts, and will make people nervous. Auto-update apps, but let people undo. Make restores undoable. Change "are you really sure?" to "don't worry, you can always undo".

Of course, you could argue, this will waste storage space. Well, with a good diff algorithm to rely on, not really that much. And even if so, you can always merge older states together (e.g. the detail of change is mostly relevant to very recent events - a few weeks back, I only care about major things like when I deleted all my contacts and didn't realize until now).

Well, we don't know enough about this case to really judge it. But my key take away is NOT that this kid is a future murderer, but rather the opposite, that internet harassment is something very different than real harassment, something normal people can get into, somewhere where it's too easy to disconnect emotionally from the target and the suffering of the target. The kid may not have been able to visualize the suffering that he caused, getting de-sensitized to the words and images used in the harassment (you don't need to stay long in 4chan for that to happen). Of course, it doesn't make it more ok, it just means we shouldn't use the same ruler to measure internet harassment as real harassment.

Reminds me of this article by SF Writer Charlie Stross: http://www.antipope.org/charlie/blog-static/2012/08/how-low-...

Optical SPDIF

I have used Google Maps for public transport very actively in multiple cities around the world, and I can't imagine living without it. Stockholm, Singapore, London, Tokyo all have it with Google. And I'd bet that a majority of smartphone users in the world use public transport, not cars, as primary method of getting around.

Wow, this is bad, and an excellent example of how the security machine (in this case FBI) can always be turned on itself. The methods required for FBI to "protect" citizens can be misused (or hacked) to do the opposite. A gun can always be turned around, etc.

He is simply listing the challenges any designer would face to make a simple yet obvious feature that just works. It is NOT describing a reason to "go back to buttons" or do something in the traditional way. This is where home electronics need to go - where you can interact with them directly instead through some button interface. If I direct my phone at the TV, both the phone and the TV should know that this is happening and depending on context, do something or offer a choice. Another example is touching your phone to your computer, etc.

The challenge, apart from making the design intuitive, is for the devices that take part in this form of interaction to understand the intent of the user.

Look here. IP licensing is the tradition in this industry. All big telecom vendors pay each other yearly amounts for IP rights. Normally they simply bulk them together and see who got most. Now and then a court case flares up (it's a negotiation tactic). In this case, what has happened is simply an escalation between two biggest competitors where no one wants to back down, and Apple "got lucky" in this particular court's interpretation. Apple is not a bully among nice guys. Everyone has been suing. Nokia, Microsoft, Motorola, etc. Everyone is gathering patents like crazy. And remember, Android device vendors are already paying large amounts to Microsoft.

Yes, it's not the signs of a healthy industry, as most software patents are silly and things will get sillier as this progresses. Most are being patented simply because they can, to add a number to the total as ammo for next licensing discussion.

I tried using it on Windows Chrome 23, but not going well. I get into creating screens, but can't for the life of me figure out how I can start drawing those screens. I seemingly can only edit the name of the screen or delete it.

Also, the page is too wide for my 1366x768. See http://imgur.com/kzIqN