MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20250326154918|217",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 227,
"ns": 14,
"title": "Category:Mediawiki",
"pageid": 199,
"logpage": 199,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-08-27T17:19:49Z",
"comment": "Created page with \"Simply anything that is specific to Mediawiki that I have had to do over time or things I learned.\""
},
{
"logid": 226,
"ns": 0,
"title": "Mediawiki",
"pageid": 198,
"logpage": 198,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-08-27T17:03:48Z",
"comment": "Created page with \"[[Category:mediawiki]] ===Mediawiki Notes=== General tasks done over time to maintain mediawiki. ==Nuke SPAM accounts== Login to the MySQL database to do this work.. * UPDATE account_requests SET acr_deleted = 1, acr_rejected = DATE_FORMAT(NOW(), '%Y%m%d%H%i%s'), acr_comment = 'Mass rejection due to account bot or spammer abuse' WHERE acr_deleted = 0 AND acr_email = acr_notes; ==Attempt indexing== * TBD\""
},
{
"logid": 225,
"ns": 14,
"title": "Category:Fail2ban",
"pageid": 197,
"logpage": 197,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-08-27T16:56:27Z",
"comment": "Created page with \"Anything related to fail2ban can be added to this category\""
},
{
"logid": 224,
"ns": 0,
"title": "Fail2ban",
"pageid": 196,
"logpage": 196,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-08-27T16:56:08Z",
"comment": "Created page with \"===Fail2ban Notes=== There are a whole bunch of options and commands that I forget for fail2ban. This is simply a list of things that can be done.. ==Ban IP== * sudo fail2ban-client set JAIL banip 107.175.27.212 ==Status Jail== * sudo fail2ban-client status ==UnBan IP== * sudo fail2ban-client set JAIL unbanip 192.168.0.1 ==Testing Regex== * fail2ban-regex /var/log/haproxy.log 'haproxy(?:\\[\\d+\\])?: <HOST>:\\d+ \\[.*\\] default_ssl_http_in~ wiki/wiki01 .* \"GET /mediawi...\""
},
{
"logid": 223,
"ns": 0,
"title": "Url encode",
"pageid": 195,
"logpage": 195,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-07-10T17:26:31Z",
"comment": "Created page with \"==URL encoding function== * Simple way to encode URLs for bash scripts.. Brainless but seems to work ok for most use cases.. <pre> urlencode() { local string=\"$1\" local encoded=\"\" local pos c o for (( pos=0 ; pos<${#string} ; pos++ )); do c=${string:$pos:1} case \"$c\" in [a-zA-Z0-9.~_-]) o=\"$c\" ;; *) printf -v o '%%%02X' \"'$c\" esac encoded+=\"$o\" done echo \"$encoded\" } </pre> [[Category:Bash]]\""
},
{
"logid": 222,
"ns": 14,
"title": "Category:Ssh",
"pageid": 194,
"logpage": 194,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-04-15T20:27:11Z",
"comment": "Created page with \"Generic \"anything\" related specifically to ssh and ssh services\""
},
{
"logid": 221,
"ns": 0,
"title": "Ssh",
"pageid": 193,
"logpage": 193,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-04-15T17:37:06Z",
"comment": "Created page with \"== SSH examples for abnormal tasks == Yes, I can never remember exactly how to get the !#$!@# port forwarding done correctly. Bah! ===SSH port forwarding for postgres=== * Accounting for possibility of using abnormal ssh ports and strange ssh keys. * Connect pgadmin to localhost:5432 and set your authentication <pre> export KEY=~/.ssh/some_key export PORT=2345 export JUMPBOX=192.168.15.58 ssh -i ${KEY} -p ${PORT} -L 5432:192.168.15.250:5432 SSH_USER@$${JUMPBOX} -N </p...\""
},
{
"logid": 220,
"ns": 2,
"title": "User:Marcos0409",
"pageid": 0,
"logpage": 0,
"params": {
"userid": 10
},
"type": "newusers",
"action": "byemail",
"user": "Chubbard",
"timestamp": "2025-04-14T01:18:30Z",
"comment": ""
},
{
"logid": 219,
"ns": 0,
"title": "Bash-ps-examples",
"pageid": 192,
"logpage": 192,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-04-10T16:34:59Z",
"comment": "Created page with \"== Generic Page of PS options == === threads from process === See the threads for a given process * [https://serverfault.com/questions/932406/how-to-tell-threads-from-processes-in-top-and-ps-on-linux show threads from process] <pre> ps aux |grep processName ps -fly -T -p PID </pre>\""
},
{
"logid": 218,
"ns": 0,
"title": "Bash rename files",
"pageid": 191,
"logpage": 191,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-04-03T21:43:23Z",
"comment": "Created page with \"==Rename files that have reserved characters== When ls is showing that funny diamond-question value in the output or you see a litteral $ in the filename, here is the fix I was able to use... <pre> ls output via -b N\\343o_Wave via ls -i 213764100 'N'$'\\343''o_Wave' # Use the inode value to move the file to something typable find . -maxdepth 1 -inum 213764100 -exec mv {} N_o_Wave \\; </pre> [[Category:Bash]]\""
}
]
}
}