Long-form articles
-
@Matthias Particularly when this one project is so big that it is "the Fediverse" for half of its users and the beginning, the centre and the gold standard of the Fediverse for many others.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@julian So all this is just an elaborate ploy to convince Mastodon devs to display
summary? It might make sense, but then I don't understand why it is presented as a protocol problem.The FEP won't make any difference. I've spent of lot of time tweaking my software in order to make rich content look good across the Fediverse (including Mastodon), and I can confidently say that Long form text FEP is not helpful at all. It is a mix of obvious requirements (which are already present in AP & AS), some arbitrary recommendations (like the set of allowed tags), and bad ideas (like the
previewproperty). This is because it is not written by a developer: the author simply doesn't know what needs to be done in order to render an article across 10 different implementations.When it comes to long form content, the best resource is @helge 's support tables. For example, there is an analysis of what HTML tags are supported in
Article.content: https://funfedi.dev/support_tables/generated/html_tags_article/No one talks about this project, but it is far more useful than anything done so far by the so called "longformers".
-
@feb @silverpill @julian I also twitch every time I see long-form content described as some kind of gnarly problem. But Julian describes a real change that's happened recently, although I wouldn't phrase it the way he did. Partly it's that Mastodon has become more open to collaboration. But mostly it's that the dev community has realised the need for working groups and formal standards processes, rather than a crowd of developers pursuing ideas individually and then arguing with each other about what's "standard". And that really has made the difference for long-form content. -
@silverpill Who are the longformers anyway?
They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.
They know themselves. They know each other. And they know Mastodon. And that's it.
None of them has ever heard of Pleroma or Akkoma.
None of them has ever heard of Misskey or the Forkeys.
None of them has ever heard of Mitra.
None of them has ever heard of GoToSocial.
None of them has ever heard of Hollo.
None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has @Helge. But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.
Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.
Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Mitra #GoToSocial #Hollo #Friendica #Hubzilla #Streams #(streams) #Forte #LongFormContent #BBcode #Markdown #HTML #TextFormatting -
@jupiter_rowland Between servers, it is almost always HTML (the only exception I know is PeerTube, which for some reason sends markdown).
>But elaborate tables that show what either of them supports how would be very useful.
There is an open issue about Streams: https://codeberg.org/helge/funfedidev/issues/93
Servers that don't support Mastodon API need additional work, and all the work is done by one person who is volunteering, so it's not in the tables yet. -
jupiter_rowland@hub.netzgemeinde.eu said in Long-form articles:
> Who are the longformers anyway?Ghost, WordPress, WriteFreely, myself....
It's not an organization per se, just a couple of us who were present at FOSDEM and want better support for non-Note types.
You know, the drum I've been beating for about a year
But I would caution you against characterizing it in such a negative manner. We're well aware there are other software platforms speaking AP.
-
@jupiter_rowland
Ich gehe davon aus, dass es um diese FEP geht.@julian
@silverpill
fep/fep/b2b8/fep-b2b8.md at main -
@jupiter_rowland
In English. I assume that this is about this FEP.geht.@julian
@silverpill
fep/fep/b2b8/fep-b2b8.md at main -
feb@loma.ml that's the one.
Summary is still used as a content warning field because of prior art, but only for notes now.
Otherwise it is treated as intended, as a summary.
-
@julian
I'm not sure what impact this will have on applications such as Friendica and other macroblog applications. Here, the AP Fediverse is only part of the federation. The Diaspora protocol in the Fediverse expects an article type in order to display correctly. AP claimed to also take this project into account. This was implemented in the AP specification at the time.
The FEP negates longformers in the Fediverse by downgrading them to a blog view across the board. However, blogs are only one variation. The Fediverse would lose rather than gain from this.In my opinion, the changes described in the FEP involve unnecessary overhead. All this just because a project does not want to implement AP in a compliant manner?
Of course, every project has the right to implement things as they see fit. But if that means that everyone revolves around this circle, then it is a monopolised protocol.The social web is not a modern invention. Fifteen years ago, this was already the goal of all projects. This requires consideration beyond protocol boundaries. Diaspora continues to be part of the Federation.
-
@julian That's very good news. -
feb@loma.ml well the great thing is the FEP is still a draft and your opinions are welcome
cc jupiter_rowland@hub.netzgemeinde.eu silverpill@mitra.social
