@sun In the JSON-LD playground, a property that is not defined in @context results in a "blank node". I don't know how bad that is, but at least it doesn't throw an error.

@devnull The state property is not necessary. I send regular Follow and Undo activities, that works.

May I ask why this FEP is finalized? There haven’t been any implementors (except for Fedify, above?) who have submitted comments about this.

There were no objections. FEP process doesn't require implementations, a rough consensus is enough for finalization.

@evan @strypey Yes, this idea was discussed, but I guess the interest has subsided because the shutdown of SocialHub was postponed.

I will probably continue using it from time to time, it's not perfect but it works and I have no problem with the current owner.

@strypey I think people could just launch a new forum. Or create groups on an existing Lemmy or NodeBB instance.

Everything is federated so the exact location doesn't matter that much anymore.

@julian @esoteric_programmer It will probably display content without title.

@julian @esoteric_programmer I think this should be reported to GoToSocial devs, because they can use name as content warning for Article objects.

Maybe there is already issue for that, but I couldn't find it

https://codeberg.org/superseriousbusiness/gotosocial/issues

@julian Hopefully nothing, the object is ignored. It may also crash

We use a different kind of identifier to keep portable objects compatible with ef61-unaware implementations:

https://social.example/.well-known/apgateway/did:example:abcd/object

which works like a regular HTTPS URL, but ef61-aware implementations treat it as equivalent to ap://did:example:abcd/object

@mariusor

@mariusor Move is used for migrating actors from one ID to another: FEP-7628. It can be used for migrating objects too, but I don't think it's practical.

FEP-ef61 solves the problem by making identifiers portable.

@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.

@helge

@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 preview property). 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".

@developer @mikedev @jupiter_rowland @feb

@feb @laurenshof I don't even blame Mastodon, they have the right to not implement the feature. What I find baffling is how an entire movement was created to solve a non-existent problem. Everyone talks about long form content like it is some grand challenge, but it is just Mastodon and a one line of code

Long-form articles

I was reading the Fediverse Report – #128 post by @laurenshof and several sentences caught my attention:

Ghost’s connection to the fediverse currently means that following a Ghost blog from your fediverse account results in seeing a post with the article headline and a URL

That's how Mastodon displays Article objects: only a headline and a URL (see issue #24079). However, Mastodon is the only fediverse platform that removes content from articles. According to funfedi.dev data, others don't remove content:

https://funfedi.dev/support_tables/generated/object_types/

GoToSocial, Hollo, Misskey, Mitra, Pleroma. These platforms either have full support for long form content or use graceful degradation. The dataset doesn't include some other popular platforms like Friendica, but I am sure they also display long form content just fine. So this really has nothing to do with Fediverse or #ActivityPub.

Fediverse platform developers (including Mastodon, Ghost, WordPress, WriteFreely and more) are collaborating on creating a space on the fediverse that suites the need of blogging and articles well

I keep seeing this again and again, it increasingly looks like an attempt to take credit for solving the problem with articles in ActivityPub. But the problem doesn't exist, it is literally a flaw in a single implementation that can be fixed with a single line of code.

There are, of course, real problems with rich content. How to prevent tracking when remote media is embedded in the page? What to do with CSS? What about interactive content? Unfortunately, I haven't seen anyone talking about these problems.

This is a long form article, by the way. You can read it from Mastodon.