greenleafjacob

I know if I had no health insurance I wouldn't hesitate to go to the emergency room for a snake bite, because I'd rather go bankrupt than die. I wonder if there is a threshold where since the cost of bankruptcy is basically constant (it doesn't matter if you go bankrupt for a $100K bill or a $100M bill unless your assets are >$100K), that the face value of the bill from the hospital can grow without bound beyond that upper boundary, since no one is actually paying it?

I’ve not used it but https://nodesource.com/products/certified-modules

Discord is also a money burning VC funded company...

That is fraud.

You can track the progress of the case through SCOTUSBlog [1] with associated filings like the writ of certiorari [2]. The precise question presented in this case is:

> Whether the Eighth Amendment’s Excessive Fines Clause is incorporated against the States under the Fourteenth Amendment

[1] http://www.scotusblog.com/case-files/cases/timbs-v-indiana/

[2] http://www.supremecourt.gov/DocketPDF/17/17-1091/33939/20180...

Nice. I haven't quite jumped from IFTTT/Zapier to Huginn yet but this is something I plan to do as well. Have you compared it with beehive [1]?

[1] https://github.com/muesli/beehive

Citizen is doing things around this [1]

[1] https://play.google.com/store/apps/details?id=sp0n.citizen&h...

ledger https://ledger-cli.org

I'm using splash [1] for scraping websites for personal automation purposes.

[1] https://splash.readthedocs.io/en/stable/

Also a fan of ledger. See http://plaintextaccounting.org for some more details on its workflow.

What was he doing from end of 2015 to middle of 2016? If I lost access to my bank accounts I’d be contacting the bank, calling emergency board meetings and filing legal motions the next day.

In fact the boilerplate you describe is mostly redundant if you use perl -p since perl -p results in your program running with this wrapper:

    LINE:
    while (<>) {
	...		# your program goes here
    } continue {
	print or die "-p destination: $!\n";
    }

Yes drug dogs need to establish probable cause, that is how they meet the requirements of the fourth amendment.

Here's the proof from Baby Rudin:

> We now show that the equation (1) p^2=2 is not satisfied by any rational p. If there were such a p, we could write p=m/n where m and n are integers that are not both even. Let us assume this is done. Then (1) implies (2) m^2=2n^2. This shows m^2 is even. Hence m is even (if m were odd, m^2 would be odd), and so m^2 is divisible by 4. It follows that the right side of (2) is divisible by 4, so that n^2 is even, which implies that n is even. > The assumption that (1) holds leads to the conclusion that both m and n are even, contrary to our choice of m and n. Hence (1) is impossible for rational p.

Pagerduty is great. Well worth it.

> Consider a Redis-based cache: For future proofing you could introduce a sharding scheme that deterministically allocates keys based on cluster size. That would be operationally pretty complex. Not to mention also introduce complexity in edge case scenarios (e.g. your cluster size is transitioning).

This is implemented in Twemproxy and resizing the cluster is a known edge case for which Twitter developed Nighthawk (centralized shard placement).

Lots of packages are increasingly hosting on their own domain (like go.uber.org/zap) and controlling the mirroring themselves.

Delivery is a cost.

What about a database that would require separate DDL from data commands? Instead of having a single super-user that can do both DDL and INSERT/UPDATE/DELETE, you would instead have a DDL user, and a data user. That would probably prompt people to only use the data user in their application?

> Similar situation to nuclear power.

I think the issue with nuclear power is more the size of the blast radius. For example, the U.S. population within 50 miles of the Indian Point Energy Center is >17,000,000 including New York City [1]. The blast radius of a self-driving car is a few dozen people at best. It's not evident that nuclear technology is uniformly better than solar or wind, but it's probably expected-value positive.

[1] https://en.wikipedia.org/wiki/Limerick_Generating_Station

TVs are monitors that are large, for more distant viewing.

For what it’s worth I think with custom VCL you could add your own shared key / password authentication to fix this by returning a synthetic 403 if the shared key isn’t present in a header.

Yes, the OOM killer activation is on its face evidence of an incident; comments on other threads saying “If your process ran out of RAM, you get to quit. Why offload it on some other random process? This is how your database process runs out of memory, and your web workers get killed (or vice versa).” The scenario depicts a capacity shortage regardless of what the system decides to do in response.

> Backups appear to be the "black hole" in GDPR

To delete backed up data, first encrypt the data with a key. To delete the data, delete the encryption key, leaving your "backed up data" meaningless bits.

> Please note! The displayed arbitrage values ignore any related deposit, withdrawal and trade fees.

What is also not displayed is the logistical possibility of executing some of these trades due to hidden KYC limitations.

For example, it currently shows a 2.02% spread between cex.io and GDAX for BTC/USD. Unfortunately, CEX.io does not provide an option to withdraw using fiat for United States citizens; the only way for United States citizens to get money out of CEX.io is buying crypto and transferring the crypto. This means that the "spread" turns out to be a premium for liquidity; if you bought 1 BTC on GDAX ($7880) and transferred it to CEX to cash out @ $8049 for a profit of $169, you would find that instead you'd have to buy some other similarly inflated crypto on CEX to bring your $8049 out.

This technically means that when CEX.io is the high market and GDAX is the low market, the trade would only work if you could naked short sell on CEX.io; then you could immediately get $8049 for an IOU for 1 BTC which you could satisfy by sending yourself 1 BTC you bought on GDAX. This might be possible using the margin trading facilities on CEX.IO?

Insidiously, CEX.IO accepts USD deposits but not withdrawals, so I found out about this the hard way.