Seeing some push back here on the idea of confusing things with more terms than just "fediverse". I get that. The problem is that that cat is very much out of the bag. Surely, for the vast majority of people that have any awareness of the fediverse, they think it's just Mastodon.

Either way, "Mastodon" is a much larger "brand" than "fediverse" or anything else on the fediverse. So trying to get some conceptual branding going makes sense. It make things more clear, as the idea of the fediverse itself is kinda fuzzy and complex and probably best left out at the beginning. It's a little bit like the matrix, you have to see it with your own eyes, IMO.

So, my lame contribution ... ****Threadiverse!**: "Social media, but woven into threads, like Reddit or Forums, not like the chaos of Twitter, but all on the Fediverse so you can find anyone else doing anything else too."

cross-posted from: https://lemmy.world/post/29836089

This update implements a lot more user requested features. The main one is the addition of the cross-post badge. The cross-post badge will show up whenever a post has been cross-posted elsewhere. Tapping the badge will show you the other places it was posted to.

This update also makes the bottom nav bar more stable, so hopefully it shouldn't jump around as much.

Please take a look below to see the full list of changes.

Full changelog

• Add option to filter posts by URL.
• Add setting to display inline images as links in private messages. Default: on.
• Add support to show a list of communities a post was cross-posted to.
• Add setting to toggle whether cross-post badges should be shown.
• Add setting to configure whether the app delays loading large datasets until the UI is settled. This was always on before. This just adds a setting to turn it off. Default: on.
• Fix a bug where some images fail to share.
• Fix more navigation bar issues.

cross-posted from: https://mitra.social/objects/018f5a57-6019-a5fb-f554-a1b86be0a9e3

Article Interop WG: How to represent titles?

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

!article_interop@lemmy.ml

Here's the reason Article became a second class citizen...

https://github.com/mastodon/mastodon/issues/5022

In this issue I raised against Mastodon in 2017 (on a now defunct github account), Mastodon at the time treated Note and Article identically. In particular, it removed all the HTML except for 'a' tags - even from Article. This made federation with the elephant impossible for us. At this time the ActivityPub fediverse consisted of Hubzilla and Mastodon. Period. The specification wasn't even final yet. Hubzilla provides long-form multi-media content, just like a blog. This content was completely destroyed by Mastodon's HTML sanitizer, especially blockquotes, which displayed everything we quoted as original text and mis-attributed.

My proposal to the Mastodon team (which was basically Eugen) was to relax the input sanitisation on the Article type a bit , and Mastodon could have their plaintext Note and we could have our multi-media and the fediverse be one happy family. Regardless of the fact that HTML is specified as the default content-type for all content in ActivityPub.

The response from Eugen was to turn Article into a link, meaning our content wouldn't be shown inline at all - and closing the issue. I believe this is the last time I ever communicated with Eugen and I will never, ever file another issue against Mastodon.

We started using Note instead, so that our messages would federate at all and knowing that Article would have been the most sensible choice.

We also need to strip all the images out of our perfectly renderable content and add them back in as attachments - otherwise they won't be displayed on Mastodon. As it turns out, Mastodon only adds back 4 images and reverses the order. This is less than satisfactory because the source content lets us position text around each image, and it forces anybody with multi-media content to not only perform this unnecessary step, but also to check every attachment on import and see if it was already included in the HTML - or it will be displayed twice.

As far as I'm concerned, Mastodon should be taken to the mountain-top and cast into the volcano. But it appears we're stuck with the infernal thing.

cross-posted from: https://mediaformat.org/wordress-activitypub/article-working-group/

📣 This is a callout proposing a working group to improve Article interop in Mastodon, and across fediverse servers & apps

📣 This is a callout proposing a working group to improve Article interop in Mastodon, and across fediverse servers & apps

Follow @article_interop@lemmy.ml to join the discussion

🔃 Share for reach cc: @article@a.gup.pe

#Article #ActivityPub #Wordpress #Plume #WriteFreely #Known

#activitypub #Article #Known #Plume #wordpress #WriteFreely

Das Fediverse wächst weiter: Über das zugrundeliegende Protokoll ActivityPub soll in diesem Jahr auch die Blogging- und Newsletter-Plattform Ghost föderieren.

Today, open source publishing platform Ghost announced that it will soon join the Fediverse with ActivityPub integration baked-in to its feature suite. The announcement includes a handy explanation of what ActivityPub is, the benefits that provides to publishers on Ghost, and a deep dive into where these features will be found in the near future

"This idea has been at the top of the list for a long time, so this week we’re starting work to look into the possibility of adding ActivityPub support to Ghost. Because there are lots of different potential ways this could be built, the team is curious to hear more detail about how you imagine this working… If you have a moment spare, could you fill out this 2-minute, 3 question survey to tell us what you’d like to see?" posted by John O’Nolan, CEO and Founder of Ghost

cross-posted from: https://azorius.net/g/azorius/p/G44w3jl9Rv76x4Q3bk-meta-groups

I've implemented basic support for composite groups (groups of groups). (Formerly named meta groups.) There's a lot of redundancy because of the federated nature of the azoriverse, with similar groups duplicated across multiple servers. Composite groups are a solution, by presenting users with a (somewhat transparent) single group that collects all of the posts.

I've created two groups, metaprog and technoscience, for demo and testing.

This is still preliminary, so federation doesn't quite work yet, but eventually the goal would be that you can follow a composite group, and it will forward activities. Instead of having to individually chase down every new programming group that gets created, you could delegate that the metaprog admin (me) to keep the group list updated.

Some basic federation is now working. I think it probably won't work from Lemmy, ironically, but azorius, honk and mastodon, etc. should be able to follow these groups. (Don't follow from azorius until after updating.)

The grandfather of the fediverse @evan@cosocial.ca wants TikTok Notes to join the fediverse