Github has gone through great lengths to begin supporting diffs on all sorts of files, 3d volumes, images, and all sorts of assets. I'd be willing to bet that some sort of bundled asset management is someone's dream project at Github.
"To the moon" is a great example of the game you are looking for -- old school pixel art graphics, but it has a beautiful touching story. And the music... just listen to it: https://www.youtube.com/watch?v=9QfPDmzpC2Q
You don't have to justify low salaries to the IRS conceptually, you just can't use them to avoid paying payroll taxes.
I would assume that companies like Apple and Facebook have competent tax teams that make sure their obligations are fulfilled, even if that means paying payroll taxes on a portion of the stock-based compensation to their executives.
New product announcements from large tech companies make it to #1 before getting any comments on a regular basis. Submitting a duplicate URL counts as an upvote for the original submission, so it's pretty easy for something like this to make it to #1 just from people racing to be the first one to submit it.
Ah, I didn't know about the duplicate URL rule. That makes more sense. I've been here for quite a while and I haven't noticed such an aggressive advance before. So it triggered an alarm. Maybe I'll start seeing it more often
They will gladly shut the service down once someone offers them enough money in aqui-hire.
It's a bummer this is the status quo with startups. To me, it's the most disappointing thing about the tech world. I actually interviewed at other companies first, and only cofounded Inbox when I couldn't find anywhere else to solve this problem.
Probably the only convincing thing I can say is that if you wanted to build a company to flip quickly, an email infrastructure startup is certainly the most painful, masochistic way you could go about it. We spent the better part of last year reading RFCs and fixing tons of obscure bugs to get this far.
I don't know their implementation but I can think of two workarounds for the firehose issue:
1. Paid approach: use some authorized firehose data resellers. That's expensive, but if there are already thousands of users, that will pay off.
2. Free approach: use poll-based solution to search for the keyword every X seconds/minutes. When new tweet appears in the search results after the last recorded tweet - that's your new tweet. This way it shouldn't miss anything and you don't need firehose. Of course, to overcome request throttling limits, you'll need to use multiple different credentials.
I would love to hear why as well! Our quality and stability have significantly improved over the last year and as a co-founder of DO, I would like to understand what specific issues you faced. Feel free to shoot me an email directly (firstname.lastname@example.org) to take this conversation offline.