HN user

Stuk

208 karma

My name is Stuart Knightley. I'm currently based in Oslo and work for Opera Software.

Contact: http://stuartk.co.uk/ , stuart@<url>, @Stuidge

Posts9
Comments50
View on HN

This looks to be damn cool. Looking at the docs[1][2] it's now possible to create a Spotify remote control (e.g. control PC from a phone) using the native client. Thinking about it, it's probably also possible to sync two Spotify players on different computers, although they would have to be using different accounts...

It would have been nice if the manifest.json used the Chrome extensions format rather than creating yet another one, but otherwise the developers should be congratulated on using plenty of HTML5 stuff, and what also looks like CommonJS modules.

I'm looking forward to seeing what comes of this!

[1] http://developer.spotify.com/download/spotify-apps-api/tutor... [2] http://developer.spotify.com/download/spotify-apps-api/refer...

How Spotify Works 15 years ago

I guess you're in the US, Canada or Brazil, because Rdio isn't available anywhere else. But Spotify is, and is doing well.

Agree with all of these points, especially the condensed-at-first display.

I would also like it if the search box was in the fixed header, so I don't have to scroll back to the top to re-search.

Otherwise nice tool!

A New Gowalla 15 years ago

I've never used Gowalla, but I've seen a lot of complaints on Twitter that peoples' "stuff" has disappeared. What's happened there?

The Shapes of CSS 15 years ago

It's two squares, each with three rounded corners and one point, rotated +/- 45 degrees to point at each other.

Move.js 15 years ago

So the differences between this and Javascript that I can see are:

    * ^ replacing function
    * default values for arguments, ^(x: 4){...}
    * print instead of console.log
    * array slicing x[1:3], x[:-2]
    * embedded HTML, div = <div/>
Interesting, but this isn't convincing enough for me to use it.

Edit: like beaumartinez says, the Github page explains the differences much better than the site: https://github.com/rsms/move

Yep, before I would even consider paying I want to see the docs for the command line tool, and at least a few screenshots of the web interface!

I does look good from what info is available though.

Well the author says in the conclusion that they don't think that they're particularly readable, but from an artistic point of view they're definitely more interesting.

Even if it isn't a success, I would like to encourage this kind of experimentation with data visualisation.

This isn't a particularly good example as you're doing all the work adding up the word counts in your reduce function.

A better example would count the occurrences of the words in each line in the map, and then add up the totals in reduce.

But completely ignore Fitt's Law. Usually I can speed my mouse to the right of the screen, click, drag. Here I speed to the right of the screen, maybe try clicking and dragging, fail, move in 30 pixels, overshoot, move back and finally can scroll.*

The problem with allowing the customisation of scrollbars is that most people are going to make them worse.

* Personally I use the scroll wheel, but I know a lot of people who don't.

I really like this idea, and have been meaning to code up something similar for a while. A few points:

* I would like to set lengths of time shorter than 15 mins. * If you visit a URL like http://timeslot.me/agendas/#day/2011-4-29 without being logged in then the interface appears, and slightly works. A redirect to the login would be better * As others have mentioned, drag/drop of tasks and length would be great * And a random idea: I would quite like to have a "repository" (todo list) of tasks with the length already set which I could drag onto a day.

With the drag and drop functionality I would happily pay a few dollars per month for something like this.

From "How does it work?" in the Readme:

    Dropbox its deduplication scheme works by breaking files into blocks. 
    Each of these blocks is hashed with the SHA256__
    algorithm and represented by the digest. Only blocks that are not yet
    known are uploaded to the server when syncing.

    By using the same API as the native client, Dropship pretends to sync a
    file to the dropbox folder without actually having the contents. This bluff
    succeeds because the only proof needed server-side is the hash of each 4MB block
    of the file, which is known. The server then adds the file metadata to the folder,
    which is, as usual, propagated to all clients. These will then start downloading
    the file.
It looks like the Github repo was deleted a few hours ago, but the direct download link still works.
I support Gus 15 years ago

Very true, but just because you can't help everyone doesn't mean you shouldn't help someone.