I wrote a short piece on my issues with projects that label themselves For Humans . You can find the full version here.

Your awesome project did a good job summarizing, though, so I'll just paste the summary:

When Kenneth Reitz created the requests library, the Python community rushed to embrace the project, as it provided (finally) a clean, sane API for making HTTP requests.

He subtitled his project "Python HTTP Requests for Humans", referring, I suppose, to the fact that his API provided developer-friendly APIs.

If naming things "for humans" had stopped there, that would have been fine with me, but instead there's been a steady stream of new projects describing themselves as being "For Humans" and I have issues with that.

When a new project comes out describing itself as X for humans , it somehow implies that any other libraries existing in the X space before were somehow not for humans.

To call your project For Humans is just a pretentious way of saying that you see your project as having a superior API to other projects in the same space.

So many projects have taken up the for humans mantle that can it really be said to mean anything anymore?

records , "SQL for Humans" legit , "Git for Humans" pep8 , "pep8 for Humans" hypermark , "markdown for Humans"

If your project has an awesome API, then say that instead.

If your project is an improvement over other projects in the space, then tell us why.

But just labeling your project for humans is both disrespectful and honestly a bit cringe-worthy.

Fantastic work on the project :)

Be able to access extraction using either RESTful HTTP or gRPC Protocol Buffers.

Hosted App will not be scalable solution and utilizing caches is the wrong direction.

REST is likely easiest to build, mostly supported by Flask but gRPC/HTTP 2.0 has many attractive features that make it appealing. Do not want to fight in the concurrency mud as much as I can. Go or Node are more fun for those apps.

Scrape and RSS/Atom Feeds

Other structured site content like

• OpenGraph
• HTML Element/Attribute data
• Sitemap.xml

Current Content Extraction extracts using DOM parsing (Frequency based) and text heuristics (Goose).

Data can be used to generate entire feed info be used as context to direct algorithm selection in a command a pattern.

For example:

curl -X POST "https://explaintome.herokuapp.com/api/v1.0/summary" -H "accept: application/json" -H "Content-Type: application/json" -d "{ "url": "https://www.technologyreview.com/s/513696/deep-learning/\", "max_sent": 0}"

Actually returns the default Wall Street Journal article defined in the code.

https://explaintome.herokuapp.com

Hi Sir,

I tried installing the project according to the readme steps, But i am getting ImportError when I run the command "python manage.py runserver", I tried using docker installation but I am getting the same ImportError, the stack trace is as given below:

ExplainToMe$ python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 6, in
app = create_app()
File "/home/swathimithran/ExplainToMe/ExplainToMe/app.py", line 46, in create_app
f(app)
File "/home/swathimithran/ExplainToMe/ExplainToMe/app.py", line 27, in register_blueprints
from . views import root, api
File "/home/swathimithran/ExplainToMe/ExplainToMe/views/init.py", line 2, in
from . root import root
File "/home/swathimithran/ExplainToMe/ExplainToMe/views/root.py", line 4, in
from collections import ChainMap
ImportError: cannot import name ChainMap

Hi there, thanks for the cool project. The bottom of the README says the support for other languages is a thing to look forward to -- could you elaborate on it a bit? Any particular plans? Let me know if you're looking for contributors that could handle different languages.