@SmokeDetector Exact copy of this answer posted at roughly the same time, both from recent accounts with no other contributions. Also, these are the only instances of the domain across the network. I've custom flagged both.
@cigien That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@Xnero Nope, I didn't forget. I was just doing other things yesterday. I'll get to it, but you're also welcome to submit a PR which makes the change.
!!/unblacklist Deepak\W?Ahirwar
The blacklist, particularly as a keyword, doesn't appear justified. At the time, it would have been OK as a username watch, maybe a username blacklist, but it's old at this point and generating FP on users for just their name.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching website in body, potentially bad ip for hostname in body, +3 more (391): Keto Advanced 1500 Canada Where to Buy? by Kurt Brown on apple.SE
@Undo / @ArtOfCode Got a rails 6.0.0 migration done and working locally -- while I'm upgrading things, some questions for y'all: Any objections to migrating to ruby >= 3.0.0? Any objections to removing our version lock on devise (also version locks in general -- we seem to have a lot of gems locked to old versions)?
(contd.) Do we have any particular procedure that we've used to switch ruby versions historically? (This one's Art specific:) Could you boost SensibleRoutes to work with rails 6 as well? It works well enough in my very limited tests.
@thesecretmaster @Undo If you are going to migrate the MS deploy to travis.com, then you may need to separately go to travis-ci.com and manually log in/auth (again) with GitHub. I was attempting to migrate Charcoal and the travis-ci.org built repositories in my account (mainly forks of ChatExchange), but travis-ci.com wouldn't let me actually do so (and would hang without feedback when "syncing with GitHub").
The UI had the definite appearance that I was logged in after getting there from links on travis.org, but actually migrating appeared to be disabled, without any significant cues in the UI as to what the problem was.
While it's probably better to move away from Travis, as a short/mid-term solution it's probably easier to migrate.
@Xnero Because it's already configured and already works (more or less). Exploring if the same thing is possible and setting up GitHub Actions takes time and effort, which is something that's usually in short supply. We have done it for everything, except the MS deploy build (which is private), ChatExchange (which is not really ours), and a few legacy repositories which haven't been built in a long time (and may never be built again).
In general, there's been a desire for Charcoal (and most projects I'm aware of) to move off of Travis CI since last Summer/Fall, due to Travis announcing that they were changing their pricing structures and making it harder for Travis CI to be used by open source projects. IIRC, Travis changing their pricing was done due to people abusing the service to get considerable free compute resources.
