This repository was archived by the owner on Oct 9, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 9, 2020. It is now read-only.
Should we continue this? #53
Description
It seems that a lot of the member lists are being crawled and either used for spam and/or recruitment mail, is it worth while having a list of users rather than just companies/posts etc
eg. #52
Activity
[-]Should we continue this/[/-][+]Should we continue this?[/+]timoxley commentedon Feb 20, 2017
Why not/
SomeoneWeird commentedon Feb 20, 2017
Bar completely removing the user listing, is there anything we can do to prevent this in the future?
kvanbere commentedon Feb 20, 2017
Answer a random non straightforward javascript question to access the list.
kvanbere commentedon Feb 20, 2017
I'm sure there are plenty of completely non straightforward bugs in v8 that could become excellent questions nobody could answer.
timoxley commentedon Feb 20, 2017
Maybe only enable if users list themselves as "available for hire" on github, which is opt-in
MauriceButler commentedon Feb 21, 2017
The other problem is the list is inaccurate...
People are missing who should be there etc.
See polyhack/npm-github-data-collector#3
I do like the opt in approach idea though if we can get the above fixed and get those who want to be represented in the list.
lox commentedon Feb 26, 2017
I guess I just don't really understand the value it provides? It seems like the vast majority of use cases are things that people on the list are unlikely to want.
Are there some counter-points of the really nice things it enables? Might a nodejsau slack (or just the slack channel on View Source) be a better way to accomplish some of these?