2026-10-24 23:33 UTC
Now this was actually submitted via a POST request from the Python standard library (`urllib.request.Request` and `urllib.request.urlopen`) to the endpoint `/api/v1/statuses`, with only two added headers (Authorization, and Accept="application/json") and default (if any) user agent.
I've probably made this little mystery a bit too obvious by reducing it down so far, but can *you* guess where the false attribution is coming from?
EDIT: of course, there was also the param `status="Well. I think..."` in the body of the request. If we're trying to be technical and comprehensive here.
Replies (1)
-
@MaddieM4@raphus.social 2026-10-24 23:39
I wanted to let that simmer a minute and give people a chance to think about it. But I think the classroom will be roughly divided into two camps. 1. People who are working it out purely from clues, and learning by logical extrapolation how Modern Webapps delegate client apps the power to act on a user's behalf. These are the students getting the most out of the Socratic method, and taking their time quietly to work it out from scratch. 2. People who already know a bit too much about OAuth2 and need to be told, "yes yes, I see you, put your hand down."