Just a note that I want to eventually have a landing page that could have a blog style to it for when article / extensions are added. I feel that with a few of the last "malicious" extension sources (Kaspersky / Great Suspender), those reports are falling in to a gray area of "some ppl may see them as malicious, others may not." My current rubric is to look for multiple source confirmations before adding to the list. But that may not be fast enough for some ppl's liking or purposes. I also really don't like the fact that I'm currently making the decision if something's malicious or not to add to the list and def feel there should be more community engagement at this step in the process. (I'm adding a "Reported Malicious" flag to the source extension list to help administrators / security ppl know when something gets flagged that it may have qualifiers.)
So, could add a project landing page that allows for comments / discussions per source, or open the curating to multiple maintainers, etc. Right now, there's not a whole lot of visibility on this project since I didn't do the SEO too well. (Well, at the time, I gave exactly zero SEO considerations since I didn't think anyone else would find any value to the list.)
So, with a bit of rebranding and linking, and with more Chrome / Chromium base browser adoption into multiple projects, now might be the time to put a more workable maintenance / community model together. (I just saw that Rapid7 uses a local Chrome instance for InsightAppScan. I doubt they're using extensions, tho... :-)
Just a note that I want to eventually have a landing page that could have a blog style to it for when article / extensions are added. I feel that with a few of the last "malicious" extension sources (Kaspersky / Great Suspender), those reports are falling in to a gray area of "some ppl may see them as malicious, others may not." My current rubric is to look for multiple source confirmations before adding to the list. But that may not be fast enough for some ppl's liking or purposes. I also really don't like the fact that I'm currently making the decision if something's malicious or not to add to the list and def feel there should be more community engagement at this step in the process. (I'm adding a "Reported Malicious" flag to the source extension list to help administrators / security ppl know when something gets flagged that it may have qualifiers.)
So, could add a project landing page that allows for comments / discussions per source, or open the curating to multiple maintainers, etc. Right now, there's not a whole lot of visibility on this project since I didn't do the SEO too well. (Well, at the time, I gave exactly zero SEO considerations since I didn't think anyone else would find any value to the list.)
So, with a bit of rebranding and linking, and with more Chrome / Chromium base browser adoption into multiple projects, now might be the time to put a more workable maintenance / community model together. (I just saw that Rapid7 uses a local Chrome instance for InsightAppScan. I doubt they're using extensions, tho... :-)
Yeah... Get on that, Mal... :-)