Checklist
Problem Description / Use Case
Right now, allowing users to define any old regular expressions (regexes) on public instances can be a bit risky from a security standpoint. While completely shutting down custom regexes would make things super safe, it also takes away a really useful way for users to customize their experience.
Proposed Solution
My idea is to let public instances use a predefined, hardcoded list of safe regexes, while still offering a way for admins to approve custom ones.
Specifically, I'm suggesting we pull in the regex lists from these two spots as pre-approved, default options:
https://raw.githubusercontent.com/Vidhin05/Releases-Regex/main/merged-regexes.jsonhttps://raw.githubusercontent.com/Vidhin05/Releases-Regex/main/merged-anime-regexes.json
Any regex a user defines that isn't on one of these pre-approved lists would be disabled by default. Thinking something along the lines of a set of checkboxes with uneditable regexes from those lists. Those should be allowed on public instances.
Big plus point is a user doesn’t have to keep track of updating of AIOStreams and then also the regexes. It would be nice to just update AIOStreams and get those for free. Plus those regexes are so neat! Public users will love it.
Checklist
Problem Description / Use Case
Right now, allowing users to define any old regular expressions (regexes) on public instances can be a bit risky from a security standpoint. While completely shutting down custom regexes would make things super safe, it also takes away a really useful way for users to customize their experience.
Proposed Solution
My idea is to let public instances use a predefined, hardcoded list of safe regexes, while still offering a way for admins to approve custom ones.
Specifically, I'm suggesting we pull in the regex lists from these two spots as pre-approved, default options:
https://raw.githubusercontent.com/Vidhin05/Releases-Regex/main/merged-regexes.jsonhttps://raw.githubusercontent.com/Vidhin05/Releases-Regex/main/merged-anime-regexes.jsonAny regex a user defines that isn't on one of these pre-approved lists would be disabled by default. Thinking something along the lines of a set of checkboxes with uneditable regexes from those lists. Those should be allowed on public instances.
Big plus point is a user doesn’t have to keep track of updating of AIOStreams and then also the regexes. It would be nice to just update AIOStreams and get those for free. Plus those regexes are so neat! Public users will love it.