Notices by fedicat (fedicat@pc.cafe)

commencing #Bonfire support

#Wrapstodon account interactions

#akkoma changelog

## 2025.12

### REMOVED
- DEPRECATE `/api/v1/timelines/direct`.

I still see people talking about producthunt, maybe we need a fediverse version.

new #Pixelfed content filters working in #Fedicat

hey if you move your #fediverse project to #codeberg you get to be on this list

https://codeberg.org/technicat/fediverse-on-codeberg

added #fedicat (and a bunch of platforms) to #fedidb

special mention to #mitra for having both an openapi spec and a changelog where you can see how it's changed by release version

don’t be surprised if you get a notification in 30 years that a poll has ended #Fedicat #Mitra

in #Mastodon #Akkoma #Pleroma #GotoSocial you can hide your follower and following lists from public view

@silverpill it just does another retrieval of the post by ID, in case there are any changes that weren't immediately returned or for whatever reason the displayed post isn't up to date, so I figured that's a good place to throw in load-replies (first part is just mitra)

public func refresh(_ post: Post) async throws -> Post {
if supportsLoadConversation {
try await loadConversation(of: post)
}
let post = try await client.refresh(post)
addAccounts(post)
return post
}

on #Mitra the post refresh option also runs the load replies feature that you can see in the web ui

I’m caught up in this #Pixelfed frenzy, just got trends to show up in #Fedicat

added bovine

https://codeberg.org/technicat/fediverse-on-codeberg

adding support in #Fedicat for the Conversation post visibility in #Mitra

@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.

@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

@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
},

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

#Mastodon changed their post visibility names so I might as well make up my own in #Fedicat