I'm often grumpy about how "loose" the #ActivityPub protocol is.

[benpate@mastodon.social]

I'm often grumpy about how "loose" the #ActivityPub protocol is. So it's important that I also point to positive examples of how to do it well.

https://w3id.org/fep/b2b8: "Long-form Text" is a great set of concrete terms and concepts that moves the #Fediverse forward in some really good ways. As we continue growing beyond "microblogging" we need this, and more stuff like it.

Thank you to @evanprodromou for putting your time into this document. It's a solid investment for everyone.

[evan@cosocial.ca]

@benpate @evanprodromou thanks for the kind words!

[julian@community.nodebb.org]

benpate@mastodon.social agreed! It's a great document that is paving the way toward better long form text support on fedi. That it has buy-in from Mastodon is the missing piece that other attempts lack.

[silverpill@mitra.social]

@julian

I still don't understand what is so great about this document.

Many fediverse applications are capable of publishing long-form text and they are interoperating. Mastodon had a couple of issues that prevented it from rendering certain HTML tags and prevented it from showing summaries, but those issues have been fixed. It is not clear what else could be improved.

For the most part, this FEP repeats definitions from ActivityStreams vocabulary. It introduces the useless preview mechanism. It also undermines the efforts to standardize thread backfilling by defining context in a different way. Am I missing something?

@benpate

[julian@community.nodebb.org]

silverpill@mitra.social I wasn't aware that there were sections pertaining to context. I'll have to review more closely.