Well, I’m impressed.
That PERFECTLY explains WebAPI technology, especially the authorization using OAUTH and JWS tokens.
It’s writes like I would write. In other words, tedious, prolix and pretentious. I like it!
Well, that confirms that behind ChatGPT are all the unemployed Chinese tech manual writers.
It used to be that one could place a hundred monkeys at 100 typewriters for 100 years, and they’d come up with a work of Shakespeare.
Now, that can happen with one ChatAPI with one super computer, and it’d come up with a work of Shakespeare in 100 nanoseconds (if that much).
Whoop de do.
About the best definition of WebAPI that I’ve seen so far.
I agree with your befuddlement, the use of “Magic Man” to emphasize the grandeur of contemplating the universe was an amateurishly obvious choice that I’d have expected the AI to be good enough to avoid. Other than that though, a perfect description of how the protocol works. What didn’t you get?
Now ask it to write a bodice-ripper & post the results. ;-)
Ask it about ‘creatring’.
Got to be better than most of the Marxist State Media today. Most could not pass middle school exams.
The Story About Ping
PING! The magic duck!
Using deft allegory, the authors have provided an insightful and intuitive explanation of one of Unix’s most venerable networking utilities.
Even more stunning is that they were clearly working with a very early beta of the program, as their book first appeared in 1933, years (decades!) before the operating system and network infrastructure were finalized.
The book describes networking in terms even a child could understand, choosing to anthropomorphize the underlying packet structure.
The ping packet is described as a duck, who, with other packets (more ducks), spends a certain period of time on the host machine (the wise-eyed boat).
At the same time each day (I suspect this is scheduled under cron), the little packets (ducks) exit the host (boat) by way of a bridge (a bridge). From the bridge, the packets travel onto the internet (here embodied by the Yangtze River).
The title character — er, packet, is called Ping. Ping meanders around the river before being received by another host (another boat).
He spends a brief time on the other boat, but eventually returns to his original host machine (the wise-eyed boat) somewhat the worse for wear.
If you need a good, high-level overview of the ping utility, this is the book. I can’t recommend it for most managers, as the technical aspects may be too overwhelming and the basic concepts too daunting.
As good as it is, The Story About Ping is not without its faults. There is no index, and though the ping(8) man pages cover the command line options well enough, some review of them seems to be in order.
Likewise, in a book solely about Ping, I would have expected a more detailed overview of the ICMP packet structure.
But even with these problems, The Story About Ping has earned a place on my bookshelf, right between Stevens’ Advanced Programming in the Unix Environment, and my dog-eared copy of Dante’s seminal work on MS Windows, Inferno.
Who can read that passage on the Windows API (”Obscure, profound it was, and nebulous, So that by fixing on its depths my sight — Nothing whatever I discerned therein.”), without shaking their head with deep understanding. But I digress
Prove me wrong.
Laz: What ever became of Humblegunner?
i think you got the default paragraph. congratulations. next up for you: the Hal 9000. good luck, sir.
AI should produce some new classical music.
What….no hit?
I am stealing that.
What is, writing AI prompts for homosexual romance novel scenes where the character hails a gay UberEats driver in a Ford SUV, for $500 Alex?