Conversation

Notices

1. Embed this notice
   Harblinger (harblinger@wizard.casa)'s status on Monday, 08-Jun-2026 17:20:37 JST Harblinger

   the chan-fe side project finally at a point where I can post a screenshot

   • lainy, ✙ dcc :pedomustdie: :phear_slackware:, prettygood and pistolero like this.
   • Embed this notice
     lainy (lain@lain.com)'s status on Monday, 08-Jun-2026 17:20:36 JST lainy

     in reply to
     @harblinger cute!
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 09-Jun-2026 05:04:04 JST silverpill

     in reply to

     @harblinger Interesting idea.

   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Wednesday, 10-Jun-2026 06:45:14 JST pistolero

     in reply to

     • Avatar of Chaos
     @MK2boogaloo @harblinger Aw *hell* yeah.
   • Embed this notice
     Avatar of Chaos (mk2boogaloo@freebeerextremist.com)'s status on Wednesday, 10-Jun-2026 06:45:15 JST Avatar of Chaos

     in reply to

     • pistolero
     @harblinger cc @p
     pistolero likes this.
   • Embed this notice
     Harblinger (harblinger@wizard.casa)'s status on Sunday, 14-Jun-2026 09:48:23 JST Harblinger

     in reply to

     • silverpill

     It's been sorta fun wrangling AP into an image board fe

     Have you considered adding the "summary" field on outbound notes? I can parse the leading <h1> from how Mitra handles incoming note summaries into "subjects", but sending notes with that field would be nice for Pleroma interop.

     Blurry Moon likes this.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 14-Jun-2026 20:39:32 JST silverpill

     in reply to

     @harblinger What would be the value of this summary field? Headings are part of the content in Mitra, I can try to extract the first heading from HTML, but this method is not always reliable (we do this for Atom feeds).

     >sending notes with that field would be nice for Pleroma interop.

     How?

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 15-Jun-2026 03:40:50 JST silverpill

     in reply to

     @harblinger

     I have thought a lot about titles and summaries, but haven't yet decided how to proceed. There are too many special cases.

     The top-level heading in a Mitra post is a title, and shouldn't be used as a summary. There is a different attribute for titles in ActivityPub, name. However, If I extract the <h1> and federate it as a name, other Mitra instances will display two titles.

     A summary, ideally, should not be displayed anywhere, because it is a summary of content. It's redundant by design. But Mastodon uses it as a "content warning", so Mitra has to insert it into the post to avoid losing important information.

     If Pleroma uses summary for "subject", that makes things even more complicated.

     There is probably a way to make it all work, but I don't quite understand your use case. What exactly you're trying to implement, a content warning?

   • Embed this notice
     Harblinger (harblinger@wizard.casa)'s status on Monday, 15-Jun-2026 03:40:51 JST Harblinger

     in reply to

     • silverpill

     >What would be the value of this summary field? Headings are part of the content in Mitra, I can try to extract the first heading from HTML, but this method is not always reliable (we do this for Atom feeds).

     I got the <h1> parsing done last night, see 2nd screenshot

     Value is pretty slim for the amount of work needed possibly (another column in the db), but just being able to set it and send it down the wire would allow the front end to use/abuse the field so pleroma-fe can set the "subject" (see first screenshot) and masto to set the "CW", not sure about other cases.

     No big deal, I can just have a subject field in the fe and prepend it in <h1> tags and that should work. I was just wondering if you thought about it much.

   • Embed this notice
     Death (death@dsmc.space)'s status on Monday, 15-Jun-2026 04:08:13 JST Death

     in reply to

     • silverpill
     • di0nysius the patomskyite
     @w0rm @harblinger @silverpill RIP
     di0nysius the patomskyite likes this.
   • Embed this notice
     di0nysius the patomskyite (w0rm@dsmc.space)'s status on Monday, 15-Jun-2026 04:08:14 JST di0nysius the patomskyite

     in reply to

     • silverpill
     @harblinger @silverpill
     
     Assemble the mutated object and face to hellthread.
     
   • Embed this notice
     Harblinger (harblinger@wizard.casa)'s status on Monday, 15-Jun-2026 04:08:15 JST Harblinger

     in reply to

     • silverpill

     Yeah it is a mess out there
     I'm implementing a subject input for notes, similar to pleroma-fe as shown in the previous screenshot

     When researching I ran across this comment in the pleroma docs:

     # Subject / CW is stored as summary instead of `name` like other AS2 objects # because of Mastodon doing it that way.

     https://git.pleroma.social/pleroma/pleroma/src/commit/6f5ea55613a62c6147f6c4bfc6b4213458f02e7d/docs/configuration/mrf.md#writing-your-own-mrf-policy

     So yeah, it's an abused field :( ... another case of "it's always mastodon"

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jun-2026 01:15:57 JST silverpill

     in reply to

     • Phantasm

     @phnt @harblinger If I add a name to my Note, will Pleroma display it as a subject?

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 16-Jun-2026 01:15:58 JST Phantasm

     in reply to

     • silverpill
     @harblinger @silverpill It is called a subject for mostly historical reasons and I would prefer for it to stay that way. Pleroma-FE gives you the option to treat it both ways. By default posts with subjects aren't compacted, but that can be enabled in the settings to treat them like CWs. And posts with subjects made by Pleroma aren't marked as `sensitive` in the ActivityPub Object representation unless an image marked sensitive is attached in FE. (Technically the sensitive field is set by an option in the MastoAPI call.)
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jun-2026 01:25:18 JST silverpill

     in reply to

     @harblinger I am leaning towards introducing an optional title. This would be aligned with how Mitra handles content warnings today (it converts them into titles), and aligned with my plans to make Mitra work better for long-form content (think Substack and Medium).

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 16-Jun-2026 01:54:51 JST Phantasm

     in reply to

     • silverpill

     @silverpill @harblinger It should federate successfully, but I don't think it will show it as subject in MastoAPI responses. If you send me an Object like that and preferably also a link to it, it should be a small change.

     Although issues arise when you then also send summary for compat reasons with other implementations and they aren't the same. At that point, I would probably override name with content of summary or drop it entirely.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jun-2026 01:54:51 JST silverpill

     in reply to

     • Phantasm

     @phnt @harblinger The object will contain only name. Maybe there will be a configuration option to switch between name and summary...

     Here's an example:

     https://lemmy.world/post/48204363

     It has a name and content but no summary.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jun-2026 05:26:29 JST silverpill

     in reply to

     • Phantasm

     @phnt @harblinger Is there a difference between title and subject?

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 16-Jun-2026 05:26:30 JST Phantasm

     in reply to

     • silverpill

     @silverpill @harblinger Now I'm kinda conflicted. The name is put into the content instead which makes more sense as it is the title for the post.

     
     image.png
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 16-Jun-2026 05:28:45 JST silverpill

     in reply to

     • Phantasm

     @harblinger So, here's what I am going to do:

     - POST /api/v1/statuses will accept an additional parameter, title.
     - This value will be exposed as Status.title and also inserted into Status.content (for now).
     - If you want to display post's title, you will need to remove Status.title from Status.content to avoid duplication.
     - The title will be federated as name, and it will not be inserted into Note.content.
     - A name on incoming objects will be treated as title, exposed as Status.title, and inserted into Status.content (same as with locally created posts).

     cc @phnt

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 19-Jun-2026 00:17:55 JST silverpill

     in reply to

     @harblinger It's available in the development branch https://codeberg.org/silverpill/mitra/commit/0c0aaf044f144750d5ddb8c3f2ff8ffb3a46db27

     This field could be used for content warnings too, maybe I will add a configuration option for that in the future.

   • Embed this notice
     Harblinger (harblinger@wizard.casa)'s status on Friday, 19-Jun-2026 00:17:56 JST Harblinger

     in reply to

     • silverpill

     Sounds good to me 👍