Vyr Cossont 🏳️🌈🏳️⚧️anyone know how Glitch and Glitch-compatible instances declare which post content types they support, if at all? i know Akkoma uses ad-hoc extensions to both nodeinfo and api/v1/instance, but i suspect Glitch hardcodes it and therefore it's not possible to detect rich text support easily
post authoring specifically
same question for #Hometown #HometownAdmin and #gotosocial #GtS #GtSDev: is it possible to detect what content types are accepted for post contents?
context: i'm trying to add #RichText support to a native client.
from my brief delvings i think that Hometown works like Glitch: it doesn't advertise the list of acceptable MIME types, but supports text/plain, text/markdown, and text/html, and accepts an additional content_type parameter on POST to /api/v1/statuses that contains the desired MIME type…
and GotoSocial doesn't list the available types either, but accepts an additional format parameter on POST to /api/v1/statuses that takes either of the literal strings plain or markdown.
which means (sigh) i'm going to have to propose an API extension for advertising rich text content types, which nobody will use and vanilla Mastodon will never mainline, or sniff the server type and switch client behavior based on what it thinks it's talking to (which means another API call to nodeinfo in the case of GotoSocial, since it doesn't show up as GtS in api/vX/instance). or maybe it's not too late to get GtS to switch to what Glitch, Hometown, and Akkoma are doing?
edit: i have since learned that Hometown doesn't author rich text posts, it just renders them.
Allow optional Markdown and/or ReStructuredText interpolation · Issue #1274 · hometown-fork/hometown
Pitch Web-Interface support for a choice (similar to the choice for post visibility or post federation) to render a post via a Markdown->HTML or ReStructuredText->HTML transformation (support for q...
opened a suggestion for #GtS: https://github.com/superseriousbusiness/gotosocial/issues/1363
i'm going to need a home lab full of instance servers for testing at this rate
[feature] Status content_type param compatible with Glitch, Hometown, Pleroma · Issue #1363 · superseriousbusiness/gotosocial
Is your feature request related to a problem ? As a native client dev, I want to write a native client with rich text support that works with as many instance server implementations as possible, in...
and also opened a suggestion for #GlitchSoc: https://github.com/glitch-soc/mastodon/issues/2091
now time to find or write an iOS Markdown editor control that doesn't need to embed all of WebKit like the first one i found…
Suggestion: instance API should include supported MIME types for statuses · Issue #2091 · glitch-soc/mastodon
Pitch I propose that we add a supported_mime_types list to the .configuration.statuses object in /api/v1/instance and /api/v2/instance, alongside max_characters, analogous to the existing .configur...
Glitch patch got merged, currently setting up GtS so i can patch it myself and do a PR
https://github.com/superseriousbusiness/gotosocial/pull/1370 adds content_type support for post authoring and advertisement of supported content types in the instance API to GtS
TIL the toot command-line client supports content_type already, so it's useful for quick test posts
Advertise rich text formats, support content_type field by VyrCossont · Pull Request #1370 · superseriousbusiness/gotosocial
Description This pull request adds two features: Accepts a content_type field when creating a status (this is the more standard version of format, as used by Glitch, Pleroma, the toot command-line...