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

You mean all the games that aren't Valve games? How is Valve supposed to create native Linux ports for them?


Like other stores, put them into the contract.


Save $300 on a vasectomy.


Mine was $750 :(


I guess if you only do one testicle, you may get half off.


They're about twice as much where I live!


Most US insurance will cover this at 100% even if you haven't met your deductible. Something about how babies cost more than a 3 digit outpatient procedure....


The titles of both the HN post as well as the original blog post are ambiguous however.


They are better in some regards, not others.

It doesn't get much easier to get quickly into a game with people ready to play than matchmaking usually. However, consistently playing with and against the same people is not as much a thing of course.

The upside of matchmaking hence is no scheduling and waiting, the downside is playing with whoever is online anywhere instead of a familiar group.


Right-click the hamburger icon, toggle Menu bar and/or Bookmark toolbar.


Because they mentioned generating load, not testing pipe performance.


Oh, wait. You mean that this "cat </dev/urandom >/dev/null" was meant to be running in the background and not be the pipeline which is tested? Ok, my bad for not getting the point.


Note that this checklist seems mostly aimed at people that send email professionally. Parts of it surely apply to individuals hosting their own email, volumes likely do not though.


The checklist seems to be for businesses sending newsletters and so on. Ramping up slowly is still a thing, though.


Yes mostly for businesses sending newsletters or cold outreach. But parts of it also important for transactional emails (SPF, DKIM, DMARC, etc)


Transactional mail alone can reach that volume easily.


Exactly, think of all the transactional emails companies like Amazon or Stripe send out on an hourly basis.


I have been using https://domainaware.github.io/parsedmarc/ and throw the DMARC reports into elasticsearch.


I'm not entirely sure if it was Sonarr, but one of the crawlers didnt support multiple media folders. Which is really annoying.


Sonarr supports as many _root folders_ as you want, the only restrictions is that a single show is limited to a single folder, so `tvs1/show1` `tvs2/show2` is completely valid, but `tvs1/show1` `tvs2/show1` is not.


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

Search: