Conversation

Notices

1. Embed this notice
   fedicat (fedicat@pc.cafe)'s status on Sunday, 08-Dec-2024 03:59:22 JST fedicat

   #Fedicat can now create and edit profile fields in #Mitra

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 08-Dec-2024 03:59:21 JST silverpill

     in reply to

     @fedicat Did it require special handling? I should make it compliant with Mastodon specs

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 08-Dec-2024 05:55:09 JST silverpill

     in reply to

     @fedicat

     >It only differs from the other platforms in requiring application/json

     Do they expect multipart/form-data? Mitra can handle form data too, but in that case it ignores fields_attributes because i don't understand what Mastodon developers are trying to say here:

     https://docs.joinmastodon.org/methods/accounts/#200-ok-2

     They provide an example of fields_attributes in JSON format and then talk about URL query parameters... That doesn't make sense to me.

     >Actually I also read it from the pleroma instance metadata, be cool to have that, looks like this

     Sure, I will add that info

   • Embed this notice
     fedicat (fedicat@pc.cafe)'s status on Sunday, 08-Dec-2024 05:55:11 JST fedicat

     in reply to

     • silverpill

     @silverpill It only differs from the other platforms in requiring application/json, and it should have been working on mitra already but I didn't specify the profile field limit in the platform descriptor (defaults 0). Actually I also read it from the pleroma instance metadata, be cool to have that, looks like this

     "fields_limits" : {

     "name_length" : 512,
     "value_length" : 2048,
     "max_fields" : 10,
     "max_remote_fields" : 20
     },

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 09-Dec-2024 04:38:48 JST silverpill

     in reply to

     @fedicat Thank you, I will work on supporting this format.

   • Embed this notice
     fedicat (fedicat@pc.cafe)'s status on Monday, 09-Dec-2024 04:38:49 JST fedicat

     in reply to

     • silverpill

     @silverpill my field update using multipart/form

     'Content-Type': 'multipart/form-data; boundary=6473FE0A-51EE-42C1-8B98-BCF838B4AA4D'
     ➡️ 💿 --6473FE0A-51EE-42C1-8B98-BCF838B4AA4D

     Content-Disposition: form-data; name="fields_attributes[0][name]"

     first

     --6473FE0A-51EE-42C1-8B98-BCF838B4AA4D

     Content-Disposition: form-data; name="fields_attributes[0][value]"

     value 1

     --6473FE0A-51EE-42C1-8B98-BCF838B4AA4D

     Content-Disposition: form-data; name="fields_attributes[1][name]"

     second

   • Embed this notice
     fedicat (fedicat@pc.cafe)'s status on Monday, 09-Dec-2024 04:38:50 JST fedicat

     in reply to

     • silverpill

     @silverpill For a while I used application/json with update_credentials for everything except the avatar/header update and that seemed to work with everything except hollo which doesn't accept application/json with update_credentials, so now I've mostly flipped it around. For fields I think I tried using that json with multipart/form to avoid all that query param construction and it worked but mastodon didn't preserve the field order.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 20-Dec-2024 06:43:31 JST silverpill

     in reply to

     @fedicat I added full support for update_credentials multipart in Mitra v3.12.0: note, locked and fields_attributes. However, the number of fields is currently limited to 4 and they should be numbered 0 1 2 3.

     Field limits were added to instance (pleroma) metadata.

     If you notice any other inconsistencies, let me know.