The long form content "movement" (of which I'm adjacent to but not fully involved) started up because two big implementors, Ghost and WordPress, were running into the same issues AP devs have been seeing this whole time, that Mastodon reduces articles to a title and link. The difference is devs got together and pushed for changes, and got them done. Mastodon no longer treats articles the way they used to. Now you can send in a summary that is used, and that gets you heaps closer to a better UX than what came before. The long form text FEP aims to provide a way to send an alternative representation for the ubiquitous microblog software on the fediverse, in the form of a note, while still maintaining the use of other objects types (e.g. article)

blenderdumbass@mastodon.online why does this article keep showing up with a newer timestamp?

A reminder that the ForumWG meeting will begin in 15 minutes.

douginamug@mastodon.xyz this entire series right here https://seb.jambor.dev/posts/understanding-activitypub/

> One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.

לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems

Man!!! That screenshot takes me back..

@pfefferle Wow, danke für das super Video! Für mich ist das Fediverse noch ganz neu, hab jetzt mein Blog föderiert und mir einen Account bei Mastodon erstellt. Fühle mich noch etwas verloren, aber bin überzeugt auf dem richtigen Weg zu sein