Article Interop WG: How to represent titles?

silverpill

Should title be inserted into Article.content as an <h1> tag, or should it go to Article.name?

@article_interop

django

@silverpill @article_interop article.name would be ideal, though I think lemmy expects title

tedu

@silverpill that's interesting because I'd say no, but html pages frequently duplicate title and h1.

Rimu

@django @silverpill @article_interop Lemmy uses 'name' on a Page (not Article).

If you get the URL of any Lemmy post and do a GET with the Accept header set to "application/activity+json" you'll see everything.

[email protected]

That makes sense to me. The <title> is metadata, and often includes context that isn’t necessary in the article body.

silverpill

@tedu @article_interop There might be popular services where name is ignored completely but <h1> in content gracefully degrades. If that's the case, <h1> (or <h1> plus name) would be preferable.

AFAIK Mastodon doesn't have this problem and will display Article.name. I don't know about the others.

silverpill

@tedu @article_interop

Found the answer here: https://funfedi.dev/support_tables/generated/object_types/

Sharkey seems to be ignoring the name, I guess this means Misskey does that as well.

julian

@[email protected] said in Article Interop WG: How to represent titles?:

Sharkey seems to be ignoring the name, I guess this means Misskey does that as well.

I thought I experienced otherwise, but it was Firefish that I saw (it oddly wrapped the title like so 【title】), but I suppose that works.

I'm all for using properties as they were intended to be used. NodeBB serves the title in name, in both the context and OP, when queried.

{
  type: 'OrderedCollection',
  name: 'Title',
  items: [ ... ],
  ...
}

{
  type: 'Note',
  name: 'Title',
  content: 'Lorem ipsum...',
  ...
}

@[email protected]

Edit: Sorry for the repeated mentions, I forgot to tag the lemmy group