A few thoughts here:
If we have a different "path" for articles that are created via bot crawling (desired for poisoning behavior) vs by humans (a potential source of spam, griefing, racist content, etc), we can enable a captcha for the "human" / manual path.
That would mean a new table for "pending links" in the database (I haven't looked at the schema to see if that exists yet - but it could solve lots of other things, like the ability to have "pending links" have references back to their parent / referencing articles for carrying context forward in situations where that might not happen otherwise)
Having a clear "New Article (Manual)" path would allow implementation of e.g. ReCaptcha - as well as potentially allowing for other heavier content-filtering like referenced in #16 and #17
I'm happy to look into implementing some of this, though I have limited experience with JS and TS, but I do have some backend experience, at least (largely Python w/Django, Flask, or FastAPI for web stuff).
A few thoughts here:
If we have a different "path" for articles that are created via bot crawling (desired for poisoning behavior) vs by humans (a potential source of spam, griefing, racist content, etc), we can enable a captcha for the "human" / manual path.
That would mean a new table for "pending links" in the database (I haven't looked at the schema to see if that exists yet - but it could solve lots of other things, like the ability to have "pending links" have references back to their parent / referencing articles for carrying context forward in situations where that might not happen otherwise)
Having a clear "New Article (Manual)" path would allow implementation of e.g. ReCaptcha - as well as potentially allowing for other heavier content-filtering like referenced in #16 and #17
I'm happy to look into implementing some of this, though I have limited experience with JS and TS, but I do have some backend experience, at least (largely Python w/Django, Flask, or FastAPI for web stuff).