tonysuper

I'm 18, and my co-founder is just turning 18 in a week.

So we never really expected to get in. We are both completely broke, so we're going to launch a kickstarter campaign to see if we can get the funding for more hosting (and the ability to work full-time over the summer). From there, well, I guess we try to grow and take over the world.

I think you may have the wrong imgur link there, buddy.

Well. Now I'm completely terrified.

I've been working on a project for about 8 months, with about 3 months on-going after a decision to re-write and reign in focus, with YC as a major end goal the entire time. Now that it's actually time to apply I'm extremely nervous—especially since I'm an 18-year-old kid who hasn't even finished high school yet (1 semester left) and I'm competing with people twice my age and with several hundred times more experience. We're quite close to a major beta release so that should help the process along.

Is there anything somebody in my (and my co-founders) circumstances should seek to convey in order to increase our chances of getting accepted? I've read quite a few articles on the best application type, but none of them had a "What to do when you're completely unproven and also extremely young" section.

I really hope this blog is only talking about Tor the community and not Tor the technology. I'm pretty sure it's impossible to ban people who are harassing others without storing some identity information, which completely defeats the purpose of Tor.

So, for those of is trying to start companies, how do you create an effective work-place environment?

It's obvious from articles like this that you can't just dump a bunch of cash on slides and ping-pong tables, but it also isn't fesable (for most companies) to have 4-hour workdays. How can you balance the need for breaks with budget concerns?

I'd really appreciate somebody with experience in the area weighing in.

goto is perfectly acceptable in C code. The most common use case is for cleaning up after errors before returning, although they're also used to break out of nested loops cleanly.

goto is harmful when used improperly but fine everywhere else.

There is a limit on information to area in space. Eventually, bitcoin is going to be impractical to store even if you have a very large storage device at absolute maximum capacity.

Deflationary currencies reward saving over spending. Aka, you can just sit on your money and it increases in value.

That's really bad for an economy.

My ideal cryptocurrency would constantly "leak" money, trying to maintain a 0.1% or so inflation rate a year, to prevent this problem.

Until somebody invents a quantum computer with a sufficiently large number of Qbits. Then they can completely destroy the blockchain.

Alternatively, wait a few hundred years until you need several hundred terabytes to store the blockchain, which is required for transactions. That's going to be a problem.

Or you could switch to Bitcoin before realizing that currencies which deflate in value are a terrible idea.

(For the record, I support cryptocurrency. I just think Bitcoin has too many issues to be viable long-term. Nice proof of concept, but it needs to be refined).

C needs wider adaptation of Apple's "Blocks" extension and MAYBE extremely limited generics and it's perfect.

This is my first major open source project, so any comments or criticism are very welcome!

LibDispatch is actually FOSS, and it kind of works on Linux. Sadly, nobody seems to bother with supporting it in any way, shape, or form.