Zerglingman,

Absolutely incredible work, pleromer:
[2023-12-12 01:45:27.707798] message t.DEBUG: send internals {'in_reply_to_conversation_id': 890771269, 'in_reply_to_id': 'AchdoqRSPApHFHV2X2', 'to': ['Zergling_man', 'Zerglingman@freespeechextremist.com'], 'visibility': 'direct'}
[2023-12-12 01:45:27.723024] message t.INFO: {'error': 'in_reply_to_conversation_id - Invalid string. Got: integer.', 'errors': [{'message': 'Invalid string. Got: integer', 'source': {'pointer': '/in_reply_to_conversation_id'}, 'title': 'Invalid value'}]}

conversation_id is given to the client as an int and expected back as a string.

Zerglingman,

Actually @lanodan you should probably be made aware of this if you aren't already. This was on sacred.harpy.faith, not FSE. I'll grant SHF is probably not on latest version, but it shouldn't be too far behind. This is an issue that would not exist with formdata, I suppose, since everything is a string.

lanodan,
@lanodan@queer.hacktivis.me avatar

@Zerglingman ⚠ Conversation IDs can be found in direct messages with the pleroma.direct_conversation_id key, do not confuse it with pleroma.conversation_id.

https://docs.pleroma.social/backend/development/API/pleroma_api/#pleroma-conversations

Zerglingman,

@lanodan Ah.
Also: Oh, new docs page.
blob

lanodan,
@lanodan@queer.hacktivis.me avatar

@Zerglingman new? It's been there for absolute years.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • GTA5RPClips
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • osvaldo12
  • ethstaker
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • ngwrru68w68
  • kavyap
  • tester
  • cisconetworking
  • JUstTest
  • InstantRegret
  • khanakhh
  • cubers
  • everett
  • Durango
  • tacticalgear
  • Leos
  • modclub
  • normalnudes
  • megavids
  • anitta
  • provamag3
  • lostlight
  • All magazines