@peemee @JeremyCherfas Figured it out: Apple decided to review this release. So it has to await the royal assent. Normally takes about a day these days.
Grr, annoying right pinky pain RSI is coming back. I blame Backspace, Return, Shift, and Semicolon.
@nitinkhanna This works:
curl \
-H'Accept: application/json' \
-H"Authorization: $tencauth" \
https://nice.social/api/posts/write \
-XPOST \
-H'Content-Type: application/json' \
--data '{"content": "Hello from curl.", "posttype": "post.note"}'/@matigo
@matigo Do you plan to support the special-case me identity? Right now, I'm getting back a plaintext response that claims it's JSON saying I passed a bogus GUID (which, well, yes, I guess I did).
curl -i -H'Accept: application/json' -H"Authorization: $tenc_auth" https://nice.social/api/account/me/bio
HTTP/2 200
content-type: application/json
Invalid Persona GUID Supplied
that probably should be a 400 or 404, and the response doesn't match the usual {{meta: {code: NUMBER, error: "plaintext string"}}, data: []} style.
In the meantime, what's the best way for me to snag the details for the current token I have stored?
Answering my own question: the /api/auth/status actually has the info. I was just parsing it for "hey you're logged out now", but should actually be using it to refresh my notion of the current user, too.
@matigo Weird. I’ve never seen that - and I’ve got Firefox running all the time. (Beta these days. Aurora back when that existed.) Wonder if there’s a config setting or something?