magicseth

You might enjoy my tldr.js [0], you select the text you want to summarize and run the bookmarklet. It could use a little help in the parser department, but it was fun to write.

[0]: https://github.com/bumptech/tl-dr.js/blob/master/tldr.js

Brought to you by the NSA

I've played around with this idea in the past. Here is a demo with three images encrypted in two different images.

use the arrow keys to move the images around or drag them.

If you overlap them perfectly, you see one image. 5 pixels left of that is another image, and 5 pixels right of center is a third image. They were originally photos and end up very high contrast :-)

http://bettermagician.com/topsecret/

Here is a version with only two images though with a better grayscale. due to the method I was trying you can see some information leak through: http://bettermagician.com/topsecret/big.html

I'm afraid I didn't make it clear. I meant a refund for the most recent $99 auto renew charge that had changed the terms of service without notifying the customers.

I don't think it's just for PR purposes, but I understand your concern of an unbounded downside. Even a few free deliveries would be something.

They were caught having made a mistake: unilaterally changing the terms of a renewing contract without written notice.

The bare minimum they can do is to offer a refund.

Mistake or no mistake, if their goal is to "always try to go the extra mile," they are failing to do so here.

This fix seems a little lackluster. It would seem more upstanding to honor the agreement they had made, and collected money for: i.e. let the 71 users continue the delivery-fee-free plan (with no minimum) for the end of the term.

The Junkyard Jumbotron lets you use all sorts of devices, and it's web based. You arrange the screens in the positions you want, and each one displays a QR code. You take a picture of them all together, and the Jumbotron breaks the image up in to the right pieces:

http://jumbotron.media.mit.edu/

Objective C is on the left, C# on the right.

Here is a more modern example of objective-c... Though, this seems more a critique of the APIs?

http://i.imgur.com/XVtUuWH.png

Sorry, it seemed to be some issue with my chrome, not the site.

It seems rather fallacious to suggest that anything legal is moral when it comes to business.

The wood parallax effect seems gratuitous, and strange, and not performant on my browser.

It does actually leak information in the form of ad prices and view rates. Not directly to he public, but it is leaked.

If you click on the commits tab, you can see which files have had the most activity. That should at least put you in the right place so you can ignore configuration files etc...

This short piece of fiction seemed so far off before. Now it seems closer: http://www.ftrain.com/nanolaw.html

The goal of this piece is not to teach people how to use git, but to give a way of thinking about git that will hopefully help new git users understand it better. It ended up being more of a wall of text than I had hoped.

Feel free to fork it:

https://gist.github.com/1951984

To me the more interesting part is how Google has managed to maintain a sense of fun and a corporate attitude that allows fun hacks to make it to the world. I'd love to know what the process was from engineer ideation (I Presume). Past product, and qa. Who said "go" and was it a hard process or one that google is optimized for.

The first part of this article is all about apps doing unnecessarily large network requests. The lack of gzip, optimized images, and redundant requests are more a sign of developers having not enough time or knowledge in the area of bandwidth optimization.

The second half of the article is much more interesting with a discussion of the horrible security practices in apps (or lack thereof). It is an indichtment of Facebook, flurry, and any other app that is leaking data (including passwords) without the user's permission.

Ironicly, this site is unusable on a mobile device thanks to a "fixed" div too large for my screen.

This is the first time I've seen the free tutorial with the option to buy the source and assets. I think this is a very interesting way to solve the problem of monetizing while still allowing uncrippled content.

What is interesting to me is that the concepts in the article are arguably more valuable the sample code itself. But by charging for the shallower of the two assets, you end up charging the people who are more likely to pay in the first place.

I've tried to learn vi for years. The simplicity of this tutorial is the first thing that allowed me to "get it." Maybe I'm just ready at last, but the quick tutorial gave me just enough beyond what I needed to know before (i/r/:wq) to grasp its power. I've tripled my vi knowledge without being intimidated.

As I look around, I see mass, systemic unemployment taking hold.

This ever increasing march of technology may result in more goods being created, but due to the nature of our capitalist society, it tends to pool the capital in those who have capital to begin with.

The huge disparity between the rich and the poor in the US is not due to "technology" but it is not being helped by it either.

Technology creates efficiencies, but there is no natural way for those efficiencies to benefit those whom it puts out of work.

It could simply be Starbucks didn't want to be associated with the project, or they never gave Mobiquity permission to use their name as an endorsement. This stunt could have caused them to notice.

And this could still be the case while a marketing team at Starbucks has decided that this card is a great tool that they can sink a couple thousand dollars into slowly to get people in to Starbucks.

Like you say, it is pretty tempting to assume the worst because nobody wants to be the last person to know they've been duped.

It could be a move to have Starbucks disassociate themselves with Mobiquity. Perhaps Mobiquity didn't have permission to use their logo or name them as a client. If Jonathan's card brought it to Starbucks' attention, that could precipitate this kind of rapid rewriting of the web.

Assuming you've jumped from correlation to causation, trying to guess at the reasoning behind it is just that, a guess.

To read some previous discussion of this article, check here: http://news.ycombinator.com/item?id=2222431

(We're still using Redis :-)

At Bump we cycled through various options: etherpad based self-organizing lunches, burrito factions, followed by 4 or 5 different catering options. Zero Cater was the winner hands down.

We've been using them for a couple of months now.

They have great variety. We had a controversial lunch at the beginning (some people loved it, some people hated it), but overall the quality has been great, the food yummy, and they've been responsive about customizing the menus to our needs.

If you want to eat ZeroCater, but not work there, you should come work with us!

http://bu.mp/openings

Don't forget that you have to deal with existing messages, which may be longer than 140, and may be truncated in your new views/layouts, making history unpredictable.

Don't forget that you're going to want to add attribution to the SMS, so you really have less than 140 characters.

Oh, and don't forget that you are going to drastically decrease the value of a percentage of your reviews, which would have previously been long, detailed, and useful.

The complexity of any modern day advanced system makes even these tiny changes balloon. The worst part isn't even the expanded work, it's the inability to predict how long all the ripples will take to fix.

The subtle bugs that got introduced by a "tiny cosmetic change" are more easily fixed in a web environment, but become pretty devastating when you have a slower release cycle, or someone gating your releases (like Apple).

Hi ajg,

Bump iOS developer here. It's hard to get a feeling of the redesign of an app just from screen shots (i.e. you can't tell what the depressed state is from a screen shot). You also can't tell that in the real app the hands are animated, showing the bumping motion in all its non-linear core animation glory.

The touch "area" on the settings button is actually decent sized, but it is not emphasized, as it is not an area that most users need to go to. We want it to be visible, and easily discoverable if that's what you are looking for, but not a big attractive button. We've found that users like to press anything that looks pressable. The fewer distracting things we put in front of the, the more likely they'll get to the good stuff sooner.

Thanks!

The slides weren't made to stand on their own, and are not entirely self-explanatory.

I'd love to chat about this in person if you're in the valley.

Here are some slides from one of my workshops on using magic to create better technology:

They are very controversial, especially out of context, so please understand that the slide that says the value of learning goes down over time has obvious qualifications, and is not generally true. It does however make a lot of sense in the context of my presentation.

http://magicseth.com/presentations/Imagineering%20InsightOut...