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": "20250126214903|212",
"continue": "-||"
},
"query": {
"logevents": [
{
"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]]\""
},
{
"logid": 217,
"ns": 14,
"title": "Category:Ansible",
"pageid": 190,
"logpage": 190,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-03-26T15:49:18Z",
"comment": "Created page with \"Just a catchall category for Ansible stuff.\""
},
{
"logid": 216,
"ns": 0,
"title": "Ansible",
"pageid": 189,
"logpage": 189,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-03-26T15:48:19Z",
"comment": "Created page with \"==Ansible Notes== * Find details about ansible collection versions (RHEL) <pre> ~/.local/bin/ansible-galaxy collection list # /home/USER/.local/lib/python3.?/site-packages/ansible_collections Collection Version ----------------------------- ------- amazon.aws 1.5.1 ansible.netcommon 2.5.0 ansible.posix 1.3.0 ***** SNIP ***** # /usr/share/ansible/collections/ansible_collections Collection Versio...\""
},
{
"logid": 215,
"ns": 0,
"title": "Iptables",
"pageid": 188,
"logpage": 188,
"params": {},
"type": "create",
"action": "create",
"user": "Chubbard",
"timestamp": "2025-03-11T18:01:15Z",
"comment": "Created page with \"==iptables notes== Just some generic notes on working with IP tables. Can be a PITA when an issue is happening to remember the details.. REMEMBER: You can block YOURSELF if you do not use your head! Dont block: Internal IP address YOURSELF external IP address (if logging in via public interfaces) Loopbacks... Not sure what would happen but expect it would brick things.. Simple blocks * iptables -A INPUT -s 47.245.124.200 -j DROP Reminders: * This will not persist...\""
},
{
"logid": 214,
"ns": 2,
"title": "User:Pmorris",
"pageid": 89,
"logpage": 89,
"params": {
"duration": "infinity",
"flags": [
"nocreate",
"noautoblock",
"noemail",
"nousertalk"
],
"sitewide": ""
},
"type": "block",
"action": "block",
"user": "Chubbard",
"timestamp": "2025-03-10T23:10:22Z",
"comment": "User is deceased. (miss you)"
},
{
"logid": 213,
"ns": 2,
"title": "User:JefferyGoodin83",
"pageid": 0,
"logpage": 0,
"params": {
"duration": "infinity",
"flags": [
"nocreate"
],
"sitewide": ""
},
"type": "block",
"action": "block",
"user": "Chubbard",
"timestamp": "2025-03-10T23:08:33Z",
"comment": "Spamming links to external sites"
}
]
}
}