I just wished the Lemmy API docs were better lol.
Finnegans Wake makes more sense than Lemmy API docs. Even calling it "documentation" is a stretch.
I literally had to clone the Lemmy git repo and read the source code to find the implementation of an API endpoint and see how it worked for a script that I was writing.
Fantastic list, thanks.
Is this really that useful though?
It's very useful if you don't use a password manager and/or reuse passwords.
The most useful part about it to me is the API. You can tie it in to Active Directory to blacklist all hashes that appear in any breach, plus expire/force a password change if any user on your domain uses a password that has been in a breach. It completely eliminates that vector from threat actors immediately.
So yeah, I would call this intensely useful.
I've been using nothing but Linux at home and work for 20 years and it's news to me that these words are not equal synonyms.
The only people that get upset over it are those whose entire personality are based on superficial bullshit like this because they don't have a personality, or just want to feel superior to someone else, or both.
I've been using Linux professionally for a couple of decades, and using it period since it was hard to install and Slackware came in the mail on ~50 floppy disks. There is not enough "Get off my lawn" in the world for those people.
I'll call the path container whatever I damned well please.
You wouldn't download a folder
The fuck I wouldn't! I'm gonna do it now out of spite!
This is art.
I still haven't found a replacement for it.
It's a decade later, and I'm still bitter about Google Reader's unceremonious execution.
If it's that old, I'm betting it doesn't use HTTPS for its connections. You could do a network packet capture on the XP machine (or if you can find one, hook it up to a network hub with another computer attached and capture there) while performing the "clear error" action and find out how it works/what you need to send to it to clear the error. You could also set up a SPAN port on a switch and mirror the traffic on the port going to the printer to capture the traffic, if you have a switch capable of doing that. If not, you can get one off Amazon for about $100.
It'd be pretty simple to put together a script that sends the "clear error" action to the printer after seeing how it's done in the packet capture. I've done this numerous times, the latest of which was for a network-connected temperature sensor that I wanted to tie into but didn't (publicly) expose an API of any kind.
Throw in a mysterious comment that says "Don't change anything below this line or everything breaks" and it's complete.
"We don't know why this works, but it does, don't touch it." would also be acceptable.
I think that this line of reasoning becomes less and less tenable when things like Swagger exist.