We had a discussion a while back about increasing MS reliability/speed/decreasing bus factor, one option raised was to create a new t2 instance with just the DB on it so that we don't run into as many threading issues
@tripleee AFAIK that's mostly waiting on MS additions, and it would probably be the most beneficial thing we could do for the org ATM, so I'd classify it as one of our top priorities
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, blacklisted website in body, +5 more: www.hitslimbody.com/enduraflex/ by Harle1944 on askubuntu.com
@angussidney exactly, and so if somebody with Rails skillz wants to cut their teeth on something reasonably nice and well-defined, that's probably where they should start
@ArtOfCode I'd say that the readme is fairly well defined. This section looks good. Sorry btw that I didn't get around to that summary that I promised, I started but got sidetracked
Anyway, basically MS has a master token of some sort, you'll need to ask Andy/Undo about that.
MS will need to be able to give/revoke etc authentication tokens for users/smokey hosts (sorta like our API keys/Smokey keys, actually these could be granted alongside smokey keys)
There should be some sort of page which displays all blacklist items etc
Ideally it should also allow people to edit the blacklists directly from MS
Same story for notifications - some sort of notifications management page would be nice
This hasn't been added to helios yet, but we'll want similar functionality for blacklisted/whitelisted users
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +2 more: Fixings in enduraflex Max by See mase on drupal.SE
MS will probably want to keep some sort of cache of the blacklists/notifications in its own DB so that we don't have to call the API every time it wants to do something
Really, you don't need to know much about serverless at all (based on what I've seen), unless if you're going to contribute to helios itself of course
I'm thinking this particularly darling of ours should be killed, it's part of the reason I posted the "what do we look like to outsiders" question on Teams
plastic-knives, you will be sorely missed, but our ways shall part
Someone should make a userscript that turns everything in chat into their own windows - with an X to close them - (like toolboxes in Photoshop). Then everyone can customize as they see fit
[ SmokeDetector | MS ] Bad keyword in body, link at end of body, link following arrow in body, pattern-matching website in body, repeated URL at end of long post: How Does Advanced Turmeric Work? by Deet 19 on workplace.SE
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +1 more: mumybear.com/purefit-keto/ by user827850 on askubuntu.com
Source: alize.me/Charcoal-SE (Warning: Should be cached since I just ran it, but if not, it's slow and will probably time out. Just refresh the page when you get the nginx timeout)
@Zoe That pattern looks like it's already caught by Offensive body detected, Toxic body detected, Offensive answer detected, and Toxic answer detected; append -force if you really want to do that.
@ArtOfCode not sure exactly, I'm thinking something more or less like a bug tracker but for outgoing issues rather than incoming... and also let's not reinvent issue tracking
Zendesk is fairly popular for customer support requests, Roundcube and Jira and Bugzilla and Github obviously
Ubuntu has a platform called Launchpad which is pretty nice e.g. for its ability to link to and track remote issues (Debian, Sourceforge, Redhat, Gnome etc)
in more concrete terms, we are currently pretty focused on individual spam domains, but the tagging facility helps group and link them; for a start, maybe a convention for linking a domain to an ... Issue? Ticket? Report? which can be pending, closed, or rejected, and maybe some additional states for "more info requested" and "sent to the wrong place" maybe?
and maybe somehow link (tag? Again?) related issues
