There may or may not be a studio called Legalporno Analvids that absolutely spams scenes everyday, so having a list of regex patterns per alert would help to filter out scenes from studios that release more niches than you would like.
Example
Create new alert, setting studios and whatever
Add patterns
Behind the scenes
Prolapse
Would end up being (roughly)
patterns=[/Behind the scenes/,/Prolapse/]scenes.filter(scene=>!patterns.some(x=>x.test(scene.title)))
You get the idea
Issues
Maybe limit max patterns per alert? 100?
Do case insensitive regex by default? Downsides?
There may or may not be a studio called ~~Legalporno~~ Analvids that absolutely spams scenes everyday, so having a list of regex patterns per alert would help to filter out scenes from studios that release more niches than you would like.
#### Example
Create new alert, setting studios and whatever
Add patterns
```
Behind the scenes
Prolapse
```
Would end up being (roughly)
```javascript
patterns = [/Behind the scenes/, /Prolapse/]
scenes.filter(scene => !patterns.some(x => x.test(scene.title)))
```
You get the idea
#### Issues
- Maybe limit max patterns per alert? 100?
- Do case insensitive regex by default? Downsides?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There may or may not be a studio called
LegalpornoAnalvids that absolutely spams scenes everyday, so having a list of regex patterns per alert would help to filter out scenes from studios that release more niches than you would like.Example
Create new alert, setting studios and whatever
Add patterns
Would end up being (roughly)
You get the idea
Issues