icook

FWIW, backfilling is on their roadmap[0].

There's also a ticket open about it[1].

[0] https://prometheus.io/docs/introduction/roadmap/#backfill-ti...

[1] https://github.com/prometheus/prometheus/issues/535

I was curious about the cost as well, so I ran some rough numbers.

417.5 BTC/GH/day for equihash if you're renting from nicehash [1]. Block interval 10 minutes [2]. 144 blocks per day target yields 0.0869 BTC/block, so cost of the 22 block reversal was ~1.91 BTC, or roughly $15k.

I'm curious if this was done as one large deposit, or many smaller deposits. I've imagined a system where block confirmations required are based on a computed cost of attack done like I did above, which would be pretty effective for very large single transaction double spends. A bit trickier to handle multiple deposits spread across multiple user accounts.

[1] https://api.nicehash.com/api?method=simplemultialgo.info

[2] https://bitcointalk.org/index.php?topic=2284289.0;all

I would imagine profiting from experimental aircraft is forbidden mostly for safetly concerns, since you probably wouldn't want someone making a fleet of aircraft out of their garage and routinely selling flights with them. Certainly that aspect doesn't apply to drones tho, since there's no inherint safety risk that I can see.

Thanks for the feedback, I'm the other co-founder of Crowdlink. We see our service as more of a complement to Gittip, where the monetary component is more of a way to show the developer you would really like to see a feature and give a small tip, instead of trying to live off of it. I know if I was dragging my feet to fix an annoying bug and a couple people put up a dollar each I would feel motivated because I knew that people genuinely valued the work.

I'm using my nexus 4 to tether my laptop almost daily with no issues in Seattle.

I think this is a cool idea, but it's still missing some required features to make it what it could be.

* Default arguments that accept a start/stop/restart. This is a really standard paradigm for daemons and would be great in a convenient form like this.

* Ability to load config information from an ini file. For instance, while developing a daemon I want to put it's pid files in a different directory then production, since prod values usually can only be written by root. Ini files are fairly standard, although accepting yaml and other config types would be even better.

* Auto-restart. While a little more advanced this is always useful when developing, although a simple tool like Guard would work instead.

Just food for thought. It's still quite useful, but only marginally so over using daemon directly.