I checked the link from the archive https://web.archive.org/web/20140701160526/http://resrc.io/ and from what I can see, it looks like the main issue (vetting of the links) wasn't really solved. That's the main issue with the awesome-x, from my perspective. Most of the people don't really need to read 5 books on basic Python, nor have the time to do so (trying to read a few books and dropping some is also time consuming).
Having tons of options sometimes seems cool when just checking or looking around, but when you actually need to use/learn something it's usually much better to have a couple (at most) of vetted resources that you can trust. Especially for the basic things, where there are countless of books, blog series, online courses. The paradox of choice, sort of. That would actually take 'community curated' to the next level.
The way I imagine this format working is having lists and sublists (loosely made of awesome-x repos) and each link having a upvote/downvote/report button. While the voting system would reside outside the github, every link could in github could have a widget next to it, similar to build status widgets. Well, you could implement voting using issues and reactions but that seems like a really messy way to do something. If widgets with score wouldn't exist, it would be extremely hard to convince the users to go to yet another web site.
That might work. What I do with https://github.com/tedyoung/awesome-java8 is require a few sentences for each submission that's describing what makes it useful and/or different from what's already available. Curation is definitely work, and kudos to @vhf for keeping up with it, but setting a higher-bar for entry can help (unless your goal is to just amass a bunch of links).
Having tons of options sometimes seems cool when just checking or looking around, but when you actually need to use/learn something it's usually much better to have a couple (at most) of vetted resources that you can trust. Especially for the basic things, where there are countless of books, blog series, online courses. The paradox of choice, sort of. That would actually take 'community curated' to the next level.
The way I imagine this format working is having lists and sublists (loosely made of awesome-x repos) and each link having a upvote/downvote/report button. While the voting system would reside outside the github, every link could in github could have a widget next to it, similar to build status widgets. Well, you could implement voting using issues and reactions but that seems like a really messy way to do something. If widgets with score wouldn't exist, it would be extremely hard to convince the users to go to yet another web site.