A special use case is the automated parsing Mastodon Atom feeds for curated content. One way to curate content is to have a special Mastodon account that is used only for content curation, and that account boosts toots that it wants to be auto-curated.
When you examine the Mastodon Atom feed, boosted toots have a
If we can offer a "Request metadata when boosting" checkbox in settings, we could potentially allow the composition of a more useful title for the Atom feed, by entering a metadata value in the optional Boost dialog, and that the metadata would become visible in the Atom feed as a new element. The auto-curation daemon on the content aggregator site could parse out the new metadata value and insert it in the content aggregation DB as the
A special use case is the automated parsing Mastodon Atom feeds for curated content. One way to curate content is to have a special Mastodon account that is used only for content curation, and that account boosts toots that it wants to be auto-curated.
When you examine the Mastodon Atom feed, boosted toots have a <title> element that is unique enough to parse, but presents poorly when that title value is used in a content aggregator's RSS/Atom feed. The unique parseable key string is "shared a status", e.g.
<title>crockwave shared a status by Debradelai</title>
If we can offer a "Request metadata when boosting" checkbox in settings, we could potentially allow the composition of a more useful title for the Atom feed, by entering a metadata value in the optional Boost dialog, and that the metadata would become visible in the Atom feed as a new element. The auto-curation daemon on the content aggregator site could parse out the new metadata value and insert it in the content aggregation DB as the <title> value of the article.
You can see from the attached RSS reader screenshot that the Mastodon Atom feed could be richer if aggregation sites could replace the default title value with custom metadata as the Atom feed is being parsed.
If Mastodon would support it, you could possibly have multiple metadata fields and even name the fields, like the profile table does in Mastodon, so that additional RSS/Atom feed richness could occur, such as use of the <notes> or <description> fields
I don't exactly understand what you want me to do.
There's no setting like that in the official Mastodon webclient so I have no demo what I could copy.
And boosting isn't like a normal compose request.
When boosting a toot,Halcyon sends its ID with /reblog to the Mastodon server.
Everything else happens on the server side.
I don't have the possibility to edit toots of other users using the API and I can't add anything there.
I can only boost them in their current form.
I don't exactly understand what you want me to do.
There's no setting like that in the official Mastodon webclient so I have no demo what I could copy.
And boosting isn't like a normal compose request.
When boosting a toot,Halcyon sends its ID with /reblog to the Mastodon server.
Everything else happens on the server side.
I don't have the possibility to edit toots of other users using the API and I can't add anything there.
I can only boost them in their current form.
Niklas Poslovski
A special use case is the automated parsing Mastodon Atom feeds for curated content. One way to curate content is to have a special Mastodon account that is used only for content curation, and that account boosts toots that it wants to be auto-curated.
When you examine the Mastodon Atom feed, boosted toots have a
If we can offer a "Request metadata when boosting" checkbox in settings, we could potentially allow the composition of a more useful title for the Atom feed, by entering a metadata value in the optional Boost dialog, and that the metadata would become visible in the Atom feed as a new element. The auto-curation daemon on the content aggregator site could parse out the new metadata value and insert it in the content aggregation DB as the
I don't exactly understand what you want me to do. There's no setting like that in the official Mastodon webclient so I have no demo what I could copy. And boosting isn't like a normal compose request. When boosting a toot,Halcyon sends its ID with /reblog to the Mastodon server. Everything else happens on the server side. I don't have the possibility to edit toots of other users using the API and I can't add anything there. I can only boost them in their current form.