skysight-inc/HackerNews huggingface dataset:
Everything below refers only to the film version of events.

As nasty as Lawrence Summers comes off in the movie, he's right. The Winklevosses should've been out creating something new, rather than using their privilege to wrangle a meeting with him.

I can't blame them for eventually seeking cash out of Facebook, since their website idea probably helped shape the ideas that would create Facebook in Zuckerberg's head. But there's a limit to that. None of the Harvard Connection's code was used in Facebook; I doubt sincerely that there were any remarkable algorithms or anything like that in their code, either.

I had a Facebook-like idea around the same time that Zuckerberg did, when I was a freshman in college. (We have absolutely nothing to do with each other; I was at Duke University and not much of a coder yet anyway).

Lots of people did. I don't begrudge him for pursuing that idea, while I slept in on Saturday mornings and went to my classes. We both made our choices.
Here is random example i found on cssmania: http://www.hungarianwinesociety.co.uk/

I would like to hear how would you design this kind of site without PS?
WebOS and the TouchPad will absolutely complete well with the iPad on both the hardware and software levels. I'd be very surprised if the iPad2 was released with better hardware than what is in the TouchPad. WebOS is the best mobile operating system out there and it's such a shame that it wasn't handled better until this point. It has had features in it for years that all other mobile OSes are still trying to catch up to. Hopefully HP will do a great job marketing everything because that's the real key to competing with Apple.
Yes, it's per 1000.
On blogging altruistically or narcissistically and why Facebook is simply easier
I'm confused. The image behind the LCD is clearly not from the LCD (there is a parallax effect), but the background image still seems artificial. Is this just two screens stacked on top of each other?
Considering the iPad doesn't come on contract it would probably make more sense to compare it to the $799 contractless Xoom
Jason "will do anything for ink" Calacanis recently gave an about face speech claiming people need to step away from the content farm business model, and in doing so admitted that roughly everything he said about Mahalo over the past couple years was a complete lie. Surprise, surprise. The interesting bit is that the start up community - which used to fawn over his huckster PR driven ploys - no longer buys them. Jason claimed to have "pivoted" his business model again, but once again we see more garbage content. His credibility has been spent. And so have his rankings! Sistrix shows that not only is he ranking for fewer keywords, but that the graph has skewed downward to worse average positions.

Amen
The document is now in the data field of the returned JSON. It's just an extra header/footer, similar to having meta http-equiv tags. Because it helps limited HTTP clients like JSONP, many web APIs already use this form, but they all use different syntax, which is the problem this "standard" is addressing.
Coding for Absolute Beginner
There's more than one way to use GDP. I think that, for describing standard of living, median GDP would be better than average GDP (= GDP per capita).

Averages are sensitive to outlier performance. This is important when the distribution follows a power law, as in the case of wealth distribution.
That is a fairly damning analysis of the farm update.

I think ultimately, sites and pages ought to be ranked based on quality, and not on whether they are a content farm, or even spam and google should be as neutral as possibly in its determination of the algorithm, focusing instead on only ensuring the quality is what prevails, and of course relevance.

What possibly has happened is that google has been forced to act in a rush, under pressure, possibly stress, and so the final product is probably a knee jerk reaction which does not address the underlying problem.

You can not make 100 percent of people 100 percent happy 100 percent of the time. Moreover, if you are such a powerful force as google you ought not to respond to pressure groups, such as a vocal minority, and act in reaction to their specific demands, that only causes problems.

But maybe the question of search has now become so difficult that indeed it has turned into a political self interested game. Youtube is hardly a site I would want to appear in most of searches which are not about videos.
>Isn't regurgitating content from elsewhere and slapping ads on it, is a content farm?

Would that not then make Google the number 1 content farm in the world?
It's pretty good considering that many startups are burning through VC money at this stage in their lives and the competition it is up against. Sure it could be more aggressively monetized, but if is bringing in enough to cover expenses why not focus on building a user base rather than cashing in.
Just out of interest, what would you have been using Redis for in your recent project?

I'm still using MySQL as my primary store, with a Redis denormalised layer on the side for set intersections, random item selection and the like.
http://investor.realnetworks.com/secfiling.cfm?filingID=8910...

"In periods where we achieve profitability, we intend to donate 5% of our net income to charitable organizations, which will reduce our net income for those periods."
HTML5 logo using CSS3
As you probably found out, a while ago, the The World-Wide Web Consortium (W3C) has unveiled the HTML5 Logo. They launched more than a logo as they got also a full branding, including badges, t-shirts and stickers.

So, I suppose that’s a good thing, that HTML5 got some branding, sounds very interesting!

While looking at it and admiring it, as I find it very nice, I thought about how can I do it with CSS3.
Great takeaways Dan! Next time we create a fun app again, we will spend 72hrs awake tending to a whole other set of problems!

Important thing is we'll enjoy the ride and keep learning. Love the post.
Thanks! let us know if you have any feedback (support@bubblegum.me)
The resulting image looked about as unusable as I expected. Besides HUD applications, what is the use case?
Thanks! It's true but I guess it wouldn't be fun if it wasn't difficult. Let's keep this going.
Nice article. I think that first step in getting a start-up is the hardest. I've been trying for some time, but I'm a programmer to the core. Never understood design. Whenever I found someone interested in something will happen for /sure/ and the whole thing goes down. I'm trying to compensate now by learning to do a basic design so I can jump-start something. I can always /pay/ someone for a design later if the website gets traction.

/hat tip for the story
I think many are overlooking the fact that this is already common practice. This spec. is just trying to make the practice less bad, not worse.

http://code.google.com/apis/websearch/docs/#fonje

https://www.dropbox.com/developers/docs
Can you say oops?
An awful lot of systems are still setup to use carbon copies as the method for generating the 'official' copy of a document. If you want to print onto a form that uses carbon paper, you have to use an impact printer.

A market need still exists, it's unsurprising that someone is filling that need.
Thanks for your thoughts. I really think a key to design is to keep track of websites that you like the look of and try to make something similar. Once you've mimicked enough designs you'll be able to do more original things. All it takes is enough time in Photoshop. Good luck!
2.4 or 5 for the current gen express. Airport extreme has simultaneous dual band. Check apple for all the specs.
Have to agree on this one. My startup is in the same space, we're taking a totally different approach. The focus is on creating a compelling presentation / pitch. When you use the product it feels like your interacting with the company.

We're pretty much iPad exclusive as we think the best way to approach the space is to put pitching tools in the hands of the entrepreneur. The idea is that investors and entrepreneurs will share the presentation physically by passing the iPad around. We also have tools to gather information on the spot, if the person wants to look it over later, take their email in the app and it emails them a link to the presentation. Which they can review later.

Use Cases:

In person amongst friends:
Check out this startup, and then pass the iPad to the person. We see this use case more for someone who has been presented to in person and is sharing with others who may also be interested.

Elevator Pitch:
If you get the opportunity for an elevator pitch and generate interest you can pass them a compelling presentation. The buttons are also oversized so that while you're presenting you can still guide the presentation while it's held in the other person's hand.

Multiple People:
With your iPad in hand you'll always be prepared to present, if you find yourself in a board room, or anywhere with a TV simply plug the VGA/TV connector in and display the presentation on the big screen.

The exit / next round:
It's easy for investors to take their portfolio companies presentation and add them to their home screen, that way when they are looking for prospective buyers for the next round / exit they have those great presentations on hand and can easily walk the buyer through.

We'll eventually support recording a presentation so that the app flips through the various parts of the presentation automatically while playing your recorded audio as the app transitions through the pitch.

We have no social media integration other than to login/share with friends, we don't think it's a good idea to encourage a herd mentality and that prospective investors should make up their own mind, rather than relying on the herd for signals. I think over the long term it will build a better understanding between investor and entrepreneur. Rather than investing based on what is in vogue.

We focus on creating a compelling story for the entrepreneur by being rich in imagery, video, and eventually audio. We're helping entrepreneurs create a connection and generate real interest in what sets their company apart from the herd.

Once we have the presentation down and have that working flawlessly we'll move to social media.
Google really should answer to the question why all of these other sites got knocked down but not Demand Media - aren't they the worst offender of all? I'm not sure I agree with the theory that it was their PR that did it. Putting on my tinfoil hat here, but did their recent IPO have anything to do with it? A lot of money is on the line now.

When I saw the Sistrix data I was surprised to see Wisegeek take a big hit, because I usually get some utility out of most of their content (even though it is now plastered with google ads), whereas eHow is almost always useless.
> There are no ASCII characters > 127. ASCII is a 7-bit encoding.

Then there is no reason Python using ASCII to handle 8bit byte and yield error.
I shortened the About-Document, tried to be more concise.

http://substance.io/#substance/substance
I grew up in NY. Not even close.
Tools that fit the task make it simpler. Otherwise, much of your attention is diverted to the tool itself, and not available for the actual task. This can be fun provided the task isn't pressing.

One example is multiplication in the complex roman numeral system vs. (our) simple arabic numeral system.

Another example is PHP (tool) for webapps (task). Worked for YouTube and CDBaby. -- Honestly, I think the concept of embedding commands in HTML is brilliantly simple, because the program is largely isomorphic to the result, making it intuitive to reason about. [disclaimer not a webapp developer]
Honest question: Can someone tell me what's wrong with a business model of putting public domain content on the web (like their "Creole cookbook" example)?

Clearly there's a line that has been crossed by republishing existing content - but wouldn't old content be fair game?

I don't plan on doing this BTW - it seems to me the hosting costs would outweigh the incoming ad dollars.
Thanks Brandon - we appreciate all the support from you guys :).

To be clear, Aarthi (arithmetic on HN) did more than half the work, both in terms of code and in PR. It turns out that being married to someone who can code circles around you has its benefits :).

Separately, I think that helped with some of the press - the fact that we were a married couple (and her being a leading female coder/engineer in an industry which doesn't have that many) added a human interest angle.
I can vouch for the quality of these tutorials. It actually puts emulation within easy reach of novice programmers, as unlikely as that may sound.

Give it a go!
It's similar to a per user log - a user has an entry from time X, time Y and so on and you're likely only interested in the last N entries. Let's say for this case that N = 20.

This is a near perfect use case for Redis lists. I say near perfect as you still have the problem that if you have an incredibly active user (which we have many of) with thousands of log entries (of which they'd only ever likely be looking at the last few hundred) as you still need to keep that entire chunk in memory. It'd be great if you could archive past the last 1000 onto disk - you can do that with client side logic but it's still a bit of a pain and then you need to hope that Redis knows that those "historical" lists don't need to clog up the cache.

MySQL isn't up to the task in that case as if those entries aren't cached (which they likely aren't) then it needs to retrieve 20 rows from disk. Those rows on disk aren't sequential and with a single access on disk being 10ms that's 0.2 seconds per query or a total of 5 queries per second. The project additionally runs on EC2 so disk IO (especially random reads) are temperamental at best. If the data was grouped or contiguous (as in the case of Redis Diskstore, BigTable style DBs etc) then you may be able to get upwards of 100 queries per second if a random read is 10 ms.

Even if we were using Redis or memcache in front of MySQL and requests came in only as we could handle them we'd only be able to serve ~430,000 requests per day. We have more users than that, the queries don't come in consistently (i.e. we still have to worry about peaks) and that's additionally not worrying about cache invalidation. Due to how slow this is it'd be nice to take snapshots to make Redis a persistent cache but then you hit the same initial problems I mentioned before.

The issue with using Redis as the primary datastore is related to the persistence issues I mentioned previously. Saves can end up taking a long time and chew up a lot more memory than I'm comfortable with. This is complicated by the fact that it'd be preferable to have some chunk of the cold dataset stored on disk but the Virtual Memory persistence option is not really suited and additionally makes saves even worse (as now you're reading from a slow disk IO device [the VM files] to save to a different slow disk IO device [the database backup] whilst trying to serve the occasional cold query from the VM).

Diskstore would solve the problems of persistent storage and slow disk IO (as the SAVE wouldn't thrash the VM disk whilst Redis was trying to use the VM disk to serve cold queries) but unfortunately we can't wait for it. I truly am looking forward to it being released however and will look to it for other future projects =]
I think you're right. Tablets are new territory. This should allow some sort creativity to happen. One possible approach is to ask "what apps could exist if we added hardware x?".
1) Ordering data on disk by primary key is irrelevant. You look up the node - one seek. Look up the edges - another seek. Look up the nodes pointed to by the edges - several more seeks.

In fact, looking up the edges is multiple seeks. For an edge (A, B), if the primary key is the row itself, edges are only stored in sequence if you are starting at node A.

Graph DB's usually cheat by store edges on both nodes, if possible within the same page as the node.

2) I'll take your word for it.

3) I generally agree that the query planner is smarter, but I'd be very surprised if that is true for complicated recursive queries. In particular, I really doubt that a query planner can exploit the structure of your data to improve things.

I.e., I really doubt the planner will know whether a DFS or BFS is better, or come up with heuristics to select the optimal path to go down (this is heavily dependent on data). Graph databases tend to provide such functionality.

I absolutely agree with you that better graph support for a SQL DB would be ideal.
At this year's Global Game Jam (a rather fun event where participants create a game in 48 hours), most of the people from our site used Love, despite having no experience with either it or Lua.

You can view what my 5-person team created on GitHub: https://github.com/icco/RainbowDeathSwarm . It's rather horrid, but I suppose it's decent considering our lack of knowledge of either the language or making games.
I totally understand the bit about it being an audit flag in the US. In Japan, it is apparently considered routine practice, in the same fashion that the IRS would never question a business deduction for a subscription to the Wall Street Journal. (I edited out the identity of the person giving the helpful suggestion shortly after posting. Suffice it to say she speaks from a position of authority on the matter.)
DC has one the hottest tech communities around, similar in growth to NYC. Here's how to connect:

* Join the DCTech FB group: http://www.facebook.com/home.php?sk=group_144795392232569...

* You can also get on the waiting list at the DC Tech Meetup
http://www.meetup.com/DC-Tech-Meetup/events/16141752/

* Check the DC Tech Events as well: http://www.dctechevents.com

The members are very active and are looking for ways to embrace startups, hackers, etc.

For example, the startupXLR8R launched today. http://startupxlr8r.eventbrite.com/
First, why wrap your second example in try {} catch {} but not the first? The second example (final example from the article) seems like it was intentionally made more complicated to prove its point, but it could just be unfamiliarity. Node idioms are just different from other environments and it takes time to get a good feel for them.

(Edit: noticed that the article does it this way.)

How about just:

function insertCollection(collection, cb) {
if (collection.length === 0) cb(null);
else db.insert(collection[0], function (err) {
if (err) cb(err)
else insertCollection(collection.slice(1), cb)
}
}

That's hardly much more complex, and as a bonus won't lock up your whole program while db.insert() is working. You could use something like my own library Seq() too:

var Seq = require('seq');
function insertCollection (collection, cb) {
Seq.ap(collection).seqEach(function () {
db.insert(c, this);
}).seq(cb).catch(cb)
}

That is, if you actually want the inserts to go sequentially. Usually you want them to go in parallel with say a maximum of 10 pending requests:

var Seq = require('seq');
function insertCollection (collection, cb) {
Seq.ap(collection).parEach(10, function () {
db.insert(c, this);
}).seq(cb).catch(cb)
}

I don't see any "fundamental issue" with node here. It's just a very new ecosystem and the idioms and libraries are rapidly evolving.
Notice that Kindle apps (iOS etc.) are free. They're not charging for the reader.

To win the ebook market big time they WILL have to win the reader market, which will amortize to giving away free readers.
Actual link: http://www.ifixit.com/Teardown/MacBook-Pro-15-Inch-Unibody-E...
ESA space concepts enter competition
>I can't wait for the persistence issues to be worked out.

Why use an in memory database for persistence instead of for cacheing? Considering that RAM is the scarcest and thus most valuable resource on nearly every server, in memory DBs like Redis are better used for storing already rendered data ready for output rather than every bit of raw data that always needs to be duplicated or logged on disk at the end of the day anyway. Persistence==disk!=memory.

>Redis Diskstore is something I'm eagerly waiting for

If your data can be represented using hashmaps (unordered) and b+trees (ordered), check out TokyoCabinet for on-disk persistance. It has the fastest on-disk hashmaps and b+trees (of non-fixed size) and has been around for a while.
Surely that's not the complaint, here. Holding quality constant, ads will make a site better--for a low-quality site, they'll provide links to people who can actually solve whatever problem the site purports to solve, while for high-quality sites they help pay the bills.
Not true. We had to make changes to how IP was treated. Yes employees can work on non-related-to-MSFT stuff, but profiting from apps would have had troubles without changes to the policy. It was the collective work of a lot of people associated with WP7 that made this happen.
Link to his patch applied to the eog.git repository: http://git.gnome.org/browse/eog/commit/?id=EOG_2_91_6~42
The iPad doesn't have a camera for video chat. I think some competitors already do.

I suppose the iPad will have the bloody camera, but it is not yet available.
I just want solid quality, affordable. I don't want to read web sites standing on my head or by clicking my tongue.
What a Microsoft employment contract looks like
Never underestimate switching costs. For the kind of organisation that plans IT purchasing five years in advance, a $500 dot matrix printer is a bargain.
> so you don't get cases like "0" being true

I meant to say false :(
With a lot of projects these days, I get the feeling that the meaning behind the name is "this domain was available".
I run developer mktg for phone. Sad to hear you think we aren't doing a good job.

Handing out phones to everyone is a bad ROI. Are you building apps? If yes, we have phones for people commited to building on the WP7 platform. Send me an email at brwatson at Microsoft and we'll get you sorted.

Oh, and our tools for WP7 are free.
#1: currently no, but I'm about to change that and have them do a SAVE every few hours or so.

#2: my implementation is pretty far along in my testing but I do need to polish it up, update the docs, and test some edge cases

#3: the idea with the slave reads for stuff that is CPU expensive or could slow down other requests (doing large multi-set operations, for example)