We're already talking about reducing the install base by over 95% (in my experience) by having no free option. It's hard to get too picky about who installs your app when you're at that level, IMO.

That's pretty much the only argument I ever see, other than the standard one for cannabis (it's just a plant).

It seems to me the standard argument for legalizing cannabis is tax revenue. It reminds me of when Kansas was considering abolishing capital pinishment. It wasn't due to any ethical or moral reasoning, but because of the economics of housing death row inmates.

It's not that these are the best reasons to change the law. It's that these are the reasons everyone can agree on

I'd be ok with investing in 200mph rail if we went ahead and bought enough ROW to add faster adjacent rail when the funds/will is there.

Neat. Any chance of adding JSON processing where you can pick a key (ala `jq`[0]) and then combine it with RSS or other JSON or what have you?

[0] https://stedolan.github.io/jq/

I've made something[1] that used "jq for everything" in the past.

RequestHub was initially a way to connect webhooks from one service to API calls to another services, using jq scripting for all the customization.

Later I realized it could be used for processing anything (even text!), not only webhooks, but it was too late. Maybe someday I'll do a Yahoo Pipes revival that will just use jq for scripting inside the boxes.

[1]: http://archive.is/nGyH3, https://github.com/fiatjaf/requesthub.xyz

Why did you discontinue requesthub?

I couldn't imagine a way to monetize it, and it was using all my free Heroku hours.

What do you think? Do you think it had a bright future?

I think Zapier and the likes fill this need pretty well. I wonder if there's still a niche for more lower-level hosted service for plumbing webhooks though. It might be a rather small niche unless you figure out a way to offer better value than those guys.

One thing that definitely makes it hard is the chicken&egg situation. I can't imagine many people paying for a service (or even using it for free), unless it has a solid reputation and is highly available. Otherwise, they'll either host something on their own, or use one of the bigger players.

If I understand you correctly, you want to be able to join the results of multiple sources? You can do something like that with a library I wrote, riko [1]. A simple example would look something like this:

    from riko.modules import join, fetch, fetchdata

    rss_url = 'http://site.com/rss'
    json_url = 'http://site.com/json'
    json_path = 'path.to.data'

    fetch_conf = {'url': json_url, 'path': json_path}

    rss = fetch.pipe(conf={'url': rss_url})
    json = fetchdata.pipe(conf=fetch_conf)

    joined = join.pipe(rss, other=json)
    next(joined)

You can see the docs for the `join` pipe here [2].

[1] https://github.com/nerevu/riko

[2] https://github.com/nerevu/riko/blob/master/riko/modules/join...

I plan on enabling filtering via xpath, and in parts jq is like xpath for json. But I'm not sure whether you mean something more with "then combine it with RSS or other JSON or what have you"? Merging generic input into a feed at a chosen element?

Side remark: Pipes uses https://github.com/feedparser/feedparser to normalize atom and rss feeds, and that gem just got support for the jsonfeed format. Untested, but worth a shot if you are looking for json input.

Should you feel like, there's also JMESPath for JSON http://jmespath.org

He or she's talking about backpage.com. They're infamous for hosting prostitution ads.

And (1) is in part because they deliberately put in extraordinary effort to customize and break Android, increasing the costs of merging from upstream.

There's plenty of money in it. Imagine if you could price the house correctly out of the gate, reducing the amount of time the home stays on the market. It is indeed a hard problem to solve using ML.

You'd need a few other things:

8. Floor count

9. Size and location of the bedrooms, bathrooms, kitchen

10. In-unit laundry (mostly for condos)

11. Proximity to neighbors

12. Existing tree coverage and other landscaping

13. Proximity to trails, transit, and other mostly-fixed landmarks

... I'm sure I'm missing many more.

Real estate is not liquid enough that a 'correctly' priced house will sell immediately. You have to wait for a buyer that wants the exact featureset that house is offering.

Real estate has sort of a weird duality where it's viewed as a commodity in aggregate - but it is definitely not a commodity good to the individual buyers looking at houses.

In the Bay Area at least, you really cannot discount the Feng Shui attributes of a home [1] and I don't think there is any MLS type of database that takes this into account.

[1] http://blog.pacificunion.com/proper-home-design-crucial-chin...

Opendoor does exactly this?

It's significantly more complicated, but at Opendoor we act as a market maker for real estate by doing this.

We sell our homes far faster than the market in Phoenix, without sacrificing on price.

I feel exactly the same way about systemd as you seem to feel about docker.

Complaining about downvotes is one of the worst things you'll see on reddit, there's no need to bring it here. Pedantry is also not very useful but I guess it's not worth "downvoting" over.

In addition to contract enforcement and standardization, I'd add reducing and/or internalizing externalities. This is fundamentally a power differential issue but I think it's important enough to highlight independently.

As for the assertion that "regulations are not bad, it's needless regulations that are bad" -- the argument sort of falls flat without specifics. The argument can be boiled down to "good things are good, bad things are bad."