<commit_before># StackWho

####What's the deal?

Ever wanted to discover StackExchange (StackOverflow, Server Fault, Super User etc) users around you that share your interests? StackWho makes it possible to find other StackExchange users near your, sorted by reputation. You can further filter them by tags. ATTENTION: If you are a company and are trying to find new employees, StackExchange offers a paid search that probably match your needs much better. This is not an attempt to compete with them.

####How?

StackExchange does not offer a public search API (they have a paid candidate search though!). That means,
we first have to fetch all their users (actually only the top 20,000) and combine them with their top 30 tags of the answers they have given. We store that information in a CouchDB on heroku. We then use a slim Node.js
backend to serve our client requests.

####Developing

This is more or less an early spike that was built in a very short amount of time.
At this stage it's missing tests, a proper build chain, travis integration etc. pp
Lot's of things are in flux.

However, the code is covered by the MIT license and I'm happy to see people joining forces with me.

####See it in action

http://cburgdorf.github.io/StackWho/src/index.html

--Christoph<commit_msg>fix(readme): updated link to demo<commit_after># StackWho

####What's the deal?

Ever wanted to discover StackExchange (StackOverflow, Server Fault, Super User etc) users around you that share your interests? StackWho makes it possible to find other StackExchange users near your, sorted by reputation. You can further filter them by tags. ATTENTION: If you are a company and are trying to find new employees, StackExchange offers a paid search that probably match your needs much better. This is not an attempt to compete with them.

####How?

StackExchange does not offer a public search API (they have a paid candidate search though!). That means,
we first have to fetch all their users (actually only the top 20,000) and combine them with their top 30 tags of the answers they have given. We store that information in a CouchDB on heroku. We then use a slim Node.js
backend to serve our client requests.

####Developing

This is more or less an early spike that was built in a very short amount of time.
At this stage it's missing tests, a proper build chain, travis integration etc. pp
Lot's of things are in flux.

However, the code is covered by the MIT license and I'm happy to see people joining forces with me.

####See it in action

http://stackwho.herokuapp.com

--Christoph
{'fraction_non_alphanumeric': 0.05246793626117373, 'fraction_numerical': 0.005441119315973571, 'mean_word_length': 4.351351351351352, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1230786', 'n_tokens_mistral': 673, 'n_tokens_neox': 633, 'n_words': 419}