print

As a creative writing of poetry major and computer programmer, I think this is just unbelieveably cool.

My contribution to the hipku craze is a Wolfram Language version of the encoder, running on the Wolfram Cloud:

https://www.wolframcloud.com/objects/902f5a2b-6672-4223-8c47...

A chess board!

Came here to say the same thing. It takes the piss out of his argument.

Fira is based on FF Meta, by Spiekermann. Trebuchet is an imitation of FF Meta.

https://blog.tilton.co/2013-08-01-fira-feura-typeface-from-m...

^this

Don't memorize. Use unp:

http://packages.debian.org/unstable/utils/unp

sounds like you may need lns:

http://interglacial.com/~sburke/pub/lns.html

Hmm... what if user doesn't have javascript enabled in the browser? Head explodes?

The table on the "about" page explains the commonality.

http://legalizecorn.com/2013-07-19-about.html

That's no moon!

Yes, my point is that "the API" as in the interface itself can be the copied, but "the API" (implementation) cannot. Clear? :)

I'm not sure what you're getting at -- copying an API interface is allowed, because API interfaces are not copyrightable see Oracle v. Google.

Moving beyond the multiple typos, broken English, and weird linebreaks, which are extremely distracting and majorly detract from the author's points --

Author's analogy (Prop. APIs == Patents) is completely false.

    These juridical and technical restrictions and 
    business dependance [sic] with specific licensing
    defined by ToS are a new kind of patent.

I call bullshit! If anything, APIs are protected by copyright law, which prevents copying.

Not to mention that a patent is protected by the state (hint: that's why it's called the United States Patent and Trademark Office), whereas Terms of Service are contracts between private parties that are entered into voluntarily.

The basic right of a patent is that of exclusion -- i.e., excluding others from "practicing" your invention (usually defined as producing, offering for sale, or importing).

However, if you don't like some company's API, there are perfectly legal ways to clone the backend service and construct an API that is basically identical.

If there is a monopoly power on behalf of proprietary APIs, it's created by market inertia and NOT by a state-granted artificial legal monopoly.

I'm getting a little sick of non-lawyers getting away with posting stupid analogies with linkbaity titles. If you want to attack the patent system, fine. But please, for the love of God, do 10 minutes of research first.

CyanogenMod 7.0.3 t-mobile Slide 3G (aka HTC Espresso).

* Work: All the Gmail usual suspects (most recently G+). Rom Manager, DroidWall

* Play: SqueezeControl (for squeezebox). Google Navigation rocks. RoboDefense, Solitaire. Wordfeud (better WordsWithFriends)

Security is definitely a hurdle, but I don't think it's insurmountable.

The main benefit to using Attachcache is greater automation. It sounds like you're doing work to get your attachments filed away. All that opening, closing, context switching adds up over time.

With Attachcache, you can either set up a Gmail "has:attachment" filter to be used in conjunction with Forwarding, or just use Sync. After you've done one of those 2 things, it's a totally hands-free solution:

https://mail.google.com/support/bin/answer.py?answer=7190

Also, Attachcache Sync is retroactive -- it can mirror my 2k+ emails and 8k+ attachments going back to 2006 in about 10 minutes. Doing this by hand would take a long time.

Hope that explanation helps, and thanks a lot for your comment!

robert schumann

I agree with your second thought. delicious' general search and multi-tag search (http://delicious.com/tag/term1+term2+term3) is so much more useful because it's essentially edited by humans.