Hacker Newsnew | past | comments | ask | show | jobs | submit | clogston's commentslogin

"18 months of credit monitoring? Crap, I've already got two of these."


Only activate one of them at a time and hope that the others don't expire...


Even more sadistic, have an entire batch dedicated to ONE of those ideas and see which company has the least poor execution.


That's what you get from an X prize, usually. It would be interesting to see an X prize that also had some base level of pre-funding for all entrants.


Maybe if YC is their /only/ investor? I'm not familiar with how YC's initial investment is structured. But your scenario won't exist for many (close enough to all?) startups who have investors. What likely happened is the startup either:

1) raised their money in a priced round. It's therefore unlikely they have unilateral control of the board.

or

2) didn't do a priced round but went with convertible notes. Those initial investments are now interest-accruing debt on their balance sheet.

In either of those scenarios there's going to be immense pressure to not let the business get comfortable.


YC's standard deal (at least according to their FAQ) is for 7% equity. So I think it is quite likely that YC startups do hold the majority interest.

As for other scenarios, I can't really speak to that - I personally have never been with a company that accepted any deal that included loss of control. I'm sure it happens, it just doesn't match my experience.


IRS requires you to authenticate yourself via one of two mechanisms if you efile (regardless of who you do your taxes with):

1) Prior year AGI

2) Electronic filing PIN

They can also issue a taxpayer a special Identity Protection PIN. If you're issued one of these you MUST use it.

There are two groups of people that don't need to "authenticate" at all:

1) Anyone who didn't file the previous tax year

2) Anyone filing by mail


The whole image is being stretched vertically in CSS ("background-size: 104% 160%;"). You can see the same distortion on the man's arm, the phone, and the pencil holder.

Definitely a "once seen, can't unsee" type of thing but I'll admit I didn't notice it initially. :)


It looks like the author for Metrics is also the author (one of the authors) of Dropwizard.


Everyone I know big enough to run a load balancer has had this happen.

The next step in evolution is to have your script look for specific text on a page, which will change 24 months later and have all the perfectly good servers pulled out of rotation.


> It would also be nice if you could disable spam filtering entirely and run your own client-side.

It's horribly convoluted but it /is/ possible to do so:

http://webapps.stackexchange.com/questions/69442/how-to-disa...

I've been running it this way for about 18 months now after having a few important emails get gobbled up by their spam filter.


It's as if they intentionally want to force their filter on you. Not that there's anything wrong with a server-side spam filter. One that puts a polite X-Spam-Score header so you can adjust the sensitivity client-side.


> SOFTFAILs should not be used and they will cause problems

Many SPF docs recommend using SOFTFAILs, including Gmail's docs [1]. What's your recommended SPF setup for his use case?

[1] https://support.google.com/a/answer/178723?hl=en


SOFTFAIL is only contributing to the anti-spam score (in theory) as it is supposed to allow the mail pass, but the host is still unauthorized [1].

Using "~all" means that you can only tell which hosts are definitely allowed to send mail for the domain, and you're unsure of anything else.

IMHO that reduces the effectivity of SPF. SOFTFAIL is useful as a debug method when you're testing rules and you don't want mail to be rejected by mistake; but I think it should be transitory and finally replaced by FAIL ("-all").

If you configure SPF to allow mail being delivered by Google's SMTP servers for that domain, you're again reducing its effectivity (Google's SMTP servers are used to send spam); but still better than a "SOFTFAIL all" I think :)

[1] http://www.openspf.org/RFC_4408#op-result-softfail


It's been some time since I ran my own mail server, but from what I recall, some spam filters actually give more negative weight (i.e. message is more likely to be spam) to a SOFTFAIL (~all) than a FAIL (-all), even though this contrary to the spec.

Spamassassin's rationale was that many of the tutorials online never explained the difference, so the majority of mailservers were just using SOFTFAIL everywhere. More paradoxically, messages that had a hard FAIL result were statistically more likely to be due to a misconfiguration, based on an empirical analysis.

Like I said though, it's been quite a while since I've had to deal with this. I'm not sure if it's still true or not.


> The author also doesn't show how the federal income tax is fundamentally different to what an employee would pay

Not disagreeing. For anyone wondering what the fundamental differences are:

1) As an independent contractor you are responsible for 100% of your FICA tax (social security and medicare tax). For most people the tax due is 15% of your income. This is in addition to your income tax. In an employee/employer relationship the employer pays for half of this. It can be a big shock to people who are hit with this for the first time.

2) If you're an employee, your employer is automatically withholding your income tax payments for you and sending them in to the IRS at a regular interval. As an independent contractor you need to be doing this yourself. If you wait until the end of the year and pay as one lump sum you'll likely be penalized.


>If you wait until the end of the year and pay as one lump sum you'll likely be penalized.

In general, you don't have to pay estimated quarterly taxes in your first year of earning self-employment income. And after you file taxes for your first year, the IRS will inform you that you need to start paying estimated taxes. So it's not super-easy to accidentally get a penalty for this.


>As an independent contractor you are responsible for 100% of your FICA tax (social security and medicare tax).

You can deduct half of the self-employment tax from the gross income on your income tax. So, for example, if your income tax rate were 25%, you would effectively pay 87.5% of FICA, not 100%. There may also be deductions on state taxes.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: