It does remind me of the XKEYSCORE (Snowden leaks) that used keywords to bubble up potential threats from emails etc https://www.businessinsider.com/nsa-prism-keywords-for-domes... .
It does remind me of the XKEYSCORE (Snowden leaks) that used keywords to bubble up potential threats from emails etc https://www.businessinsider.com/nsa-prism-keywords-for-domes... .
https://www.youtube.com/watch?v=bJ5ppf0po3k
He made a filter that did analysis of the pronunciation of the messages that were being sent. His breakdown of it starts at around 13:30
I see the same here. It's not clever, but no one has any doubt what words are being checked.
The engineer would write something for every test case the product manager complained about, anything else computationally easy, and call it a day.
I once had to implement an audit logging system. What was supposed to be logged? "Important actions." Nobody on the team could define it. We just logged every database write along with the username responsible and called it a day. Nobody ever followed up or inspected it.
Same deal. Both exist mostly for compliance.
Tracking down "why is the antique system suddenly slow". Power went out, system came back up fine, everything but the one ancient but vital app is fine. Dig, dig dig, there's this old dot matrix printer in another room (because it used to be loud and annoying) that no on has fed or looked at in years.
It finally died with that outage, and it not accepting data was the problem. It had cheerfully printed the ribbon through, then fed out the rest of the box of paper it had, and that might've been several years before i saw it.
The roller the paper was supposed to ride had been eroded. The metal rods the print head rode on had a perceptible bump at the ends of the normal stroke.
The fix was a little dongle for the printer port that held the appropriate "i'm alive" lines up. hardware /dev/null. I'm thinking it was 25 pin rs232 because I remember a lot of cussing over it.
That kind of thing is probably fairly common in the industry.
I'm pretty sure it was the only dot matrix printer with a serial port i ever saw. Even daisy wheels were parallel port by the time this went in; but they had a like 50ft cable to move it to the other room. Someone worked hard and paid large to set that up originally.
It used to be "if I search for this term, am I accidentally going to wind up getting goatse or something?" The good old days.
Now it's "if I search for this term, is the FBI going to kick my door in?"
you need the domain to make the goat-sex joke work
That's what the linked page says (I'm not familiar with Dutch Wikipedia specifics), but that seems like such a strange statistic to track instead of minimum edit count.
So weird that I looked up how to configure MediaWiki autoconfirm requirements. They probably mean a minimum of one edit. Auto-confirmation considers only age and edit count, and I don't see why clicking 'Edit' is so meaningful a condition to warrant developing an extension.
https://www.mediawiki.org/wiki/Manual:Autoconfirmed_users
Searching about extensions did lead to discovering an obscure feature: there's now a built-in URL shortener: https://w.wiki/Q8
Edit: interestingly, the single-character ones seem to have been pre-planned: https://w.wiki/e, https://w.wiki/E, https://w.wiki/4
In the Dutch WP? Because otherwise I should qualify.
https://meta.wikimedia.org/wiki/Help:Unified_login
You can list your local accounts at
It's not a list of words used by the NSA or any spies. https://attrition.org/misc/keywords.html
$Username=<username>
$Password=<password>
Connection.string=($Username, $Password)
The parser would flag this - Password was being stored to a variable! So we just changed our code:
$pw=<Password>. Problem solved!
This must be more nuanced. Maybe, it's "additional algo processing when a word is hit", eg another layer before "involve human".