trianglesphere

They’ve gotten pretty strict if they think your IP is a scraper (i.e. coming from AWS or another cloud provider even inside a full browser environment).

It’s about moving inside a state. I told the DMV of my new address, but my drivers license still has the old one. Maybe I could get it reissued, but that seems like a pain. Many people move more frequently than the license expiration period.

Not in rural areas. Maybe for suburbs. At least in SF ppl Uber a fair bit, but I suspect most trips on a night out are not replacing someone driving their own car.

The other tell is 3 leaves. From memory (so maybe wrong), they aren't hairy, but do have a slightly broken edge (can be smooth, but can have a little but not a lot of variation).

You need way more than one. Trees, storms, and cars take out distribution power lines all the time. Substations, which was got attacked, have less redundancy and way fewer spare parts on hand.

Contract’s don’t (more accurately almost never) pay for gas. Gas estimation is done when sending by the end user.

Some parts of gas estimation can be done statically, but some of the cost of certain operations are dependent on the data being loaded from the state. I’d like a tool to set an upper bound on gas usage (current approach is to execute the tx on pending state and add 10-30%), but solidity does not provide one.

These are also mainly used on fully residential streets and basically codifying existing rules. They behave very similarly to streets without a center line & sidewalk/bike lanes. I also think cost does become an issue when implementing larger streets/bike lanes (let alone the fact that larger streets make people go faster) on every single residential street.

It’s not just federal taxes, but 50 states. I think you could get enough oss manpower for keeping up to date with federal taxes, but not every state.

They do charge for state taxes. It’s like 15 bucks per return with not that much up sell. I’ve used them when I had simpler taxes and liked them over other common preparers

My dad's gas car (20 years ago) caught on fire in the garage while he wasn't there. The house was fine b/c of a a code required fire break between the garage and house. It's probably more rare nowadays, but not impossible.

I think there were also some issues around metering gas, which tracks how much work was be done by uploaded code

One problem I have with plaid is that the most common use for them that I see is a company using them in order to setup direct deposit. It's also really hard to figure out how to manually set it up (I usually have to click deny on plaid and then I can input it myself)

I'm not interested in handing over all my info when I can copy and paste two numbers instead

It needs low latency. There is a huge amount of inherently sequential lookups in the state (~9 leveldb lookups per 1 state acess in a smart contract) and you can't store the state in RAM on most consumer hardware.

Those number's aren't that related to low head dams (most low head dams fatalities are swimmers, not whitewater kayakers or rafters or rec kayakers). While the mechanism behind low head dams (technical term hydrolic, informally called a 'hole') can directly or indirectly kill you, they're typically a natural feature in whitewater fatalities.

I know those numbers b/c it lets me tell my parents that whitewater kayaking isn't as dangerous as they think.

All you need to do is have a webpage that has a meta tag with name="go-import" and a content tag with content="URL src-control-method source-control link"

See xyzc.dev/go/ppgen and inspect the source for an example.