@ArtOfCode If you could include time before, time after, and a delta, that'd be great. Bonus points if the line starts with the delta for easy reading.
A significant part of it is looking at the indexes, which are B trees, which don't really get deep enough to get particularly screwed until you're looking at hundreds of thousands of items
I've been working on it for a while, just because I wanted to see if some ideas that I have would work, and I generally like decoupling stuff/modularification.
metasmoke.abuse_comments
note : Table does not support optimize, doing recreate + analyze instead
status : OK
metasmoke.abuse_contacts
note : Table does not support optimize, doing recreate + analyze instead
status : OK
metasmoke.abuse_report_statuses
note : Table does not support optimize, doing recreate + analyze instead
status : OK
metasmoke.abuse_reports
note : Table does not support optimize, doing recreate + analyze instead
status : OK
metasmoke.announcements
note : Table does not support optimize, doing recreate + analyze instead
So, let's see if we can chop time off of that with these. Less likely, because these tables are orders of magnitiude smaller, but let's see in 24 hours.
metasmoke would then say "flag this with this account" and it does it, without metasmoke (and thus anyone writing code for metasmoke) remotely having access to raw tokens
findspam is the only thing that will be complete rewritten
and I'm already doing that a little bit anyways
The rest, and this is key to understand, is about identifying the implicit interfaces the other modules follow, and turning those into actual interfaces that our SE code is just a child class of
For chatcommunicate + spamhandling which will probably be squished into one, this is really just these: init/parse_room_config, tell_channels, is_privileged, handle_report
Only person who could realistically get their hands on tokens is me. You could, in effect, get the same security gains just by saying "Art might have access to tokens too" on sign up.
@ArtOfCode Actual maliciousness is only the tip of the iceberg (not terribly worried about that, you have other ways to be evil). There's unintentional stuff, too - remember when the new websocket implementation happily spewed out whatever you asked for?
We got lucky and no one tried that for three months, but crap happens.
Wouldn't need to worry about miniprofiler memory-dumping any token secrets, etc.
I could see it spewing encrypted tokens because someone made a boo boo fairly easily, but to spew in plaintext you'd need to make a boo boo in the autoflagging functions; if you're touching those, multiple people are going to be reviewing the code
Your changes to autoflagging last night I pulled down and ran to make sure logging hadn't changed
the age of the laptop is partly involved, though, this is a four year old laptop
in this case, it was excess dust in the fan ventport so
still had to take this thing apart
but in the process, I fixed something that had stopped working, the front-panel lights were not working at one point, after this got a repair, so they work now yay!
and the fan works now too, but yeah literal fireball waiting to happen basically
I'm sure all kinds of fun things happen when GPUs overheat
@Andy @Undo I think we should actualy start with the output/soamhandling part first. Starting with findspam/bodyfetcher requires doing both, whereas we can leave those unmodified while changing chatcommunicate to do whatever
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-11: sattamatka Body - Position 1-11: sattamatka Username - Position 1-11: sattamatka
@NobodyNada You can add patterns that effectively don't start/end on a word boundary in blacklist or watchlist. You just have to take into account that the pattern does get bookended by \b. Thus, you need your pattern to consume all of the \w or \W characters which are before and after it. In this instance, \w*satta ?matka\w* would produce the same results, with the minor difference of including the extra in the matched string, which would look somewhat different in the "why".
I find it kind of amusing to think that if their website really is as simple as they claim in the time they took raging about GDPR they probably could have updated their privacy policy
(assuming yes means the picture changed) did you change it a while ago and it just propagated to chat, or did you somehow get it to sync to chat immediately?
@FreezePhoenix where in God's good earth do you work/use the Internet where they would detect your mobile hotspot and come find you and 'eliminate the problem'?
@ArtOfCode I would, considering that's a full time security and IT force needing to manage and monitor the entire IT network simultaneously and then subsequently finding and torching individuals' devices which are acting as hotspots
@ArtOfCode not to mention the potential for legal hell if they confiscate the device as such
probably should be asking though:
@FreezePhoenix so they don't let you use your own device, then, and force you to use their devices in a school environment?
@ArtOfCode actually? Not really since I know quite a few people who won the fight in court because their phone was taken for "undisclosed reasons" when it wasn't really being used in any rule-breaking way
All you have to do is ban phones, stick a WiFi receiver next to every access point you have to do SSID scans, and when you pick up a new hotspot you go search that classroom
@FreezePhoenix I wasn't saying that schools don't set up filters -- I hear about it all the time --just that they don't usually seem to do a good job at it
@FreezePhoenix that then lends credence to the "How would they find/detect/neutralize a hotspot", but then I could say "This is a problem with where you work sorry you're screwed.
@ArtOfCode so if the phone is in someone's pocket, but off, and the school takes it arbitrarily just because it's on their person, even if it's off, that's not out of line?
two people I know had their phone in their backpacks, off, had the phone taken just because "they saw it", and then their parents took the school to court and won
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, pattern-matching website in body: Keto Power Diet Want by JohnMondy on drupal.SE
