rehashed

Maybe he just wanted to follow jQuery convention for a jQuery plugin?

http://contribute.jquery.org/style-guide/js/

> Indentation with tabs.

The story thats not being told is how those "hundreds of hours" spent building "snow fall" included direction, videography, 3d and 2d modelling and animation, photography, content-writing, design, coordination, and frontend development.

Scrollkit took just one aspect of that (frontend development) and stated "The NYT spent hundreds of hours hand-coding ‘Snow Fall.’ We made a replica in an hour."

Its outright dishonest, and devalues the great effort that others spent on it. I can understand why they are pissed.

Hopefully there wont be the same issues as with posterous:

https://news.ycombinator.com/item?id=1441997

Socialsync meets the definition of synchronization in the assemblance of a synchronism. I don't see how them failing to meet the authors rather loose choice of definition justifies them being called liars.

Some further clarification:

Henges have a ditch with an outer bank. At Stonehenge it is reversed, with a ditch OUTSIDE the bank - effectively making the world around it the structure for which it is named.

http://en.wikipedia.org/wiki/Henge

Stonehenge is clearly the outside of the asylum.

I have the same issue.

http://AI/ has address 209.59.119.34

http://BO/ has address 166.114.1.28

http://CM/ has address 195.24.205.60

http://DK/ has address 193.163.102.24

http://GG/ has address 87.117.196.80

http://JE/ has address 87.117.196.80

http://KH/ has address 203.223.32.21

http://PN/ has address 80.68.93.100

http://TK/ has address 217.119.57.22

http://TO/ has address 216.74.32.107

http://UZ/ has address 91.212.89.8

http://VI/ has address 193.0.0.198

http://WS/ has address 64.70.19.33

This is exactly one of the concerns I mentioned: https://news.ycombinator.com/item?id=5353171. It is already exhibited by other controllers of TLDs: http://ydal.de/a-records-on-top-level-domains/

I havent received a reply yet to my request to reopen the public discussion on the new gTLDs: https://news.ycombinator.com/item?id=5351335. I'll be chasing up on it today - I would appeal to the rest of you to do the same and help stop these gTLDs ever seeing the light of day.

It sounds to me like you are doing your standups wrong. The job of the facilitator (in your case, the team leader) should be to keep things moving, and ensure that you aren't taking 30 minutes.

The most important thing to get out of the meeting, IMHO, is challenges, as status should be evident by the location of your story tickets. The problem with providing an environment where "Others can skim-read or ignore." is that they often will, and peer challenges can easily go unresolved without adequate feedback.

You are standing for a reason - its uncomfortable (for those of us who sit all day). Your facilitator should be roping in the conversation (and if not you need to replace them - rotating among team members often works). If that doesn't work, then your teams are likely too large.

There are many reasons. That is just one of them.

Please see parent and other posts in the thread, comments on the linked article, and discussions in the forums for others.

UPDATE3: The more I think about this, the more concerned I become. These new gTLDs, given the proliferation of combined search and location bars in modern browsers are tantamount to a direct keyword to those corporations with $185k to spend. Type in 'antivirus', and you will be directed to symantec - not the search results you would likely expect. This has to stop - NOW.

What benefit do these new TLDs bring to the table? If ICANN need additional revenue, why not fractionally increase the cost of the current gTLDs instead of introducing more?

All these new domains can possibly achieve, IMHO, is to confuse the consumer and allow corporations to control access to 'desirable' gTLDs.

If the domain space is so overcrowded, then by all means introduce a new gTLD - but keep it ICANN controlled. Either run a poll to choose, or allow the corporations to 'sponsor' their choice of TLDs incorporation into ICANN - but there is no way they should be commercially controlled!

UPDATE: Im really upset that I missed this - looks like ICANN opened up a discussion for public comment (which has now closed after only a month? Surely such a major change should be open to larger public debate..): http://www.icann.org/en/news/public-comment/closed-generic-0...

UPDATE2: I have sent an email to [email protected] requesting that the discussion be reopened. I believe it is our duty as a community to publicise this discussion amongst web professionals and have a further chance to fight it. I would respectfully request that you do the same!

Does this require that my apps users each have a dropbox account?

I was going to jump on this as soon as it was announced. Sadly, I don't think this is suitable for Android development given the specs. What are your thoughts? My GF is very tempted to take over my macbook pro...

Unroll all the things!

I was also confused at the choice of default. Fortunately you can update your config to support any TLD:

http://pow.cx/manual#section_3.1

Its pretty, but it only handles one rule at a time. Being able to provide feedback on all errors will be considerably less graceful..

Have you seen: https://github.com/makeable/Notificon

A demo would be nice!

> Encyclopedias should not just switch off for political reasons.

I believe this is the point of the demonstration.

1.17MB 24bit PNG with alpha transparency on a flat color background...

I published notificon (an ender compatible library) to the npm registry, but it does not appear on the toolbox. How do I go about submitting packages to the toolbox?

How does this differ from MacClients in apache, or process limits on CGI? I agree with you, but don't see how this problem is specific to node...

Both PNGs and ICOs should definitely work. Unless you specify a favicon in the function call, it will look for the one specified in your head. If one is not specified in your head it will use the default favicon location (/favicon.ico).

It should work in Chrome 6 and above and Firefox 2 and above. There is no support for modifying favicons in other browsers client-side.

It has done the exact same thing for my friends posts for a looooong time. This isn;t specific to his account, its just more prominent because there are more people "liking" it.