Zum Inhalt der Seite gehen


Maybe posting to Mastodon requires an extensive preamble


Als Antwort auf Jupiter Rowland

@Jupiter Rowland Ah well.... That's the core problem of ActivityPub and the Fediverse, again, in my opinion. There's no interoperability above a very simple protocol level. At all. In the end, it all boils down to "this is how _we_use it and _we_ don't care how it works for _you_ so that's _your_ problem". Experiencing, at the moment and again and again, similar things while trying to interact with other ActivityPub-enabled platforms (including those that, in example, throw away "likes" or even "comments" because, hey, no need to implement or support any of these - who cares about usability or somewhat consistent user experience anyway...). Quite disappointing in many many ways. 😔
Als Antwort auf Kristian

@Kristian @Jupiter Rowland This is not so easy. Many of the newer projects are still working on their basic functionality.

With Lemmy, the code for federating had to be completely rewritten because the first version was only compatible with itself.

The Fediverse ecosystem is now very complex, so many iterations are necessary.

Dieser Beitrag wurde bearbeitet. (5 Monate her)
Als Antwort auf Hamiller Friendica

@Hamiller Friendica Yes, but point being: In a complex distributed environment, fuzzy protocol specs are a sure way to cause havoc. For a broad range of different implementations, you'll get more than enough problems even having strict specs (because there will be bugs or people will fail to fully implement _everything_ the way it has been standardized). The more "open", "flexible", "extensible" the standards are, the worse it will get (and this without even assuming there are implementations that are buggy and incomplete because they're in its infancy). And, in some ways, it feels like "Postels Law turned by 180 degrees". Not like "be liberal in what you accept and strict in what you send" - it's, now, more like "send whatevery _you_ see fit and leave the problem of understanding and handling it right to others". 😔

@Jupiter Rowland

Als Antwort auf Kristian

@Kristian well, the choice of ActivityPub was a bad choice from the beginning.

the W3C editors haven’t provided a level playing field and I truly believe the specification is now worthless as a unifying force for the free web. We’re probably stuck with supporting multiple competing protocols for some time (years) into the future. This is OK — it is what it is, but any opportunity for free web unification using a common stack has probably been lost. Ironically, I believe this was ActivityPub’s primary goal, and that makes the specifications which restrict the ability to federate seamlessly with other services flawed — critically.


Mike MacGirvin in 2017

Als Antwort auf Kristian

Als Antwort auf Jupiter Rowland

Als Antwort auf Jupiter Rowland

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Als Antwort auf Jupiter Rowland

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Als Antwort auf Danie van der Merwe

@Danie van der Merwe said:

"I can disprove your point right there - although I am on #Hubzilla, #Friendica and #Matstodon, I saw your post on my Mastodon account, and read it. Shows up in full length."

It's more of a cultural issue than a technical issue. Mastodon is fully capable of accepting posts from other systems. For example, I quoted you, which is not a feature on Mastodon. The issue is that some people don't like it when others deviate from what they expect or prefer.

Als Antwort auf Danie van der Merwe

@Danie van der Merwe I never said it doesn't show up.

I said that Mastodon users see that this post is longer than 500 characters, and they can't be bothered to read it because it's so long.

And that's even harmless.

Some users block you right away if you write more than 500 characters.

That's still harmless.

Other users attack you for having the audacity to disturb them with an unnecessarily long "toot". Couldn't you have written that as a thread like "everyone else in the Fediverse"?!

I'm not kidding when I say that there are Mastodon users who want posts over 500 characters banned from the whole Fediverse.

Same with everything else that you can't do on Mastodon. Text formatting, quotes etc.

Als Antwort auf Jupiter Rowland

I think it's a fear of change... more options are better than fewer options.

They need to realise Mastodon is just one of very many social networks all connected together. Anyone can have 5,000 characters available and choose to only use 500. But having 500 only means you can never go over 500.

Because it's under 500 means only posts on Hubzilla and Friendica appear in full. Mastodon users need to go to my blog for the rest.

Als Antwort auf Jupiter Rowland

Als Antwort auf Jupiter Rowland

@Ema エマ

well, the choice of ActivityPub was a bad choice from the beginning.


The core issue is that ActivityPub is primarily a broadcast protocol and Zot & Nomad are communications protocols. As such, ActivityPub will be great at distributing posts to lots of people but is lacking in the areas of moderation, privacy, and nomadic identity. That's one of the reasons why Hubzilla uses Zot and Streams uses Nomad to talk to themselves. ActivityPub just doesn't have the feature set.

Dieser Beitrag wurde bearbeitet. (5 Monate her)
Als Antwort auf Jupiter Rowland

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Dieser Beitrag wurde bearbeitet. (5 Monate her)
Als Antwort auf Sylkeweb Testing The Fediverse

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Dieser Beitrag wurde bearbeitet. (5 Monate her)
Als Antwort auf Sylkeweb Testing The Fediverse

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Als Antwort auf Sylkeweb Testing The Fediverse

@Sylkeweb on Mastodon I don't deny that.

But the vast majority of Mastodon instances is vanilla with a 500-character limit. This includes the typical newbie instances, especially mastodon.social.

So your typical Twitter-to-Fediverse convert will spend several months believing that the Fediverse is only vanilla Mastodon. Instances with modified character limits don't exist. Forks like Glitch don't exist. And stuff that has never been Mastodon in the first place doesn't exist either.

Als Antwort auf Jupiter Rowland

I think most people just want something that works the way they are used to it - the same experience for all. Not everybody is inclined to learn everything there is to learn about the Fediverse, and some people simply don’t have the time. That’s fine by me. As I said, they can mute or block me if they can’t cope with that. And I‘ll ignore/mute/block them if they keep badgering me for any reason. I don’t have to engage.
Als Antwort auf Jupiter Rowland

Inhaltswarnung: Draft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Als Antwort auf Netux

@Netux Well, that's one of Hubzilla's limitations: You can only pin one post. And I've already pinned one.

Besides, I've got my doubts that someone with a Mastodon mobile app can check my channel and my posts just like they can check a Mastodon account and the posts on it.

And a lot of Mastodon users can't be bothered to check someone's profile before following them. Why should they check someone before replying to them?

Als Antwort auf Jupiter Rowland

Just fyi, checking your bio on your profile page works fine from my mobile Mastodon app.
Als Antwort auf Jupiter Rowland

Als Antwort auf Jupiter Rowland

@Jupiter Rowland A bit unrelated: Are titled posts from Hubzilla supported on Mastodon? Or are they also shown as a backlink to the original post on your server?
Als Antwort auf Cătă

@Cătă No problem. Mastodon doesn't know what to do with the title, so it ignores it. I put titles on almost all my posts, Mastodon removes them, and that's it.
Als Antwort auf Jupiter Rowland

@Jupiter Rowland It also doesn't know what to do with the title on Friendica. But it doesn't ignore it, instead it turns it into a caption and links back to the post. Example (paste this link in the URL bar of your browser if it shows "restricted account"): https://ieji.de/@petrescatraian@libranet.de/111331875310742745.
Dieser Beitrag wurde bearbeitet. (5 Monate her)
Als Antwort auf Cătă

@Cătă Still doesn't work... Pity that Friendica only offers client-side OpenWebAuth.
Als Antwort auf Jupiter Rowland

@Jupiter Rowland oh, right. I can no longer see it either. The idea is, here's how my post looks

图像/照片

And here it is on Mastodon:

图像/照片

Als Antwort auf Cătă

@Cătă Could be that Friendica is sending out something weird to Mastodoon then.
Als Antwort auf Cătă

@Cătă In WriteFreely's case, it makes sense. I've got my own WriteFreely blog, and I'm not too keen on dumping tens of thousands of un-content-warned characters into people's Mastodon timelines. I mean, many Mastodon users already freak out and wish for a Fediblock when they see someone having the audacity to put 1,200 characters into one post instead of making it a thread.

In Friendica's case, it could be deliberate, but with no communication towards Hubzilla and (streams) which don't do that. So either Friendica is the odd one out, or Hubzilla and (streams) are.

Als Antwort auf Jupiter Rowland

@Jupiter Rowland On Friendica, writefreely posts/articles are rendered as posts with titles. That's what I find odd. How is it possible for Friendica to render the entire content of what is basically a post, while on Mastodon it has to backlink?

many Mastodon users already freak out and wish for a Fediblock when they see someone having the audacity to put 1,200 characters into one post instead of making it a thread

oh, gosh 👀

Can't people just scroll past that without reading at all?

Als Antwort auf Cătă

Als Antwort auf Jupiter Rowland

@Jupiter Rowland Fascinating. Yea, that makes a whole lot of sense if it's true. Thanks for the explanation
Als Antwort auf Jupiter Rowland

Maybe what is needed is an article addon that federates. That way longer posts from Hubzilla and Streams are treated as articles on Mastodon and other platforms.
Als Antwort auf Scott M. Stolz

@Scott M. Stolz Instead of creating yet another add-on, there could be two other ways of achieving that.

One, introduce a channel-wide setting for whether posts with a title should go out as Article objects or as Post objects, and a post-specific override switch just in case. That way, you can switch between Hubzilla's/(streams)' current behaviour and Friendica's behaviour.

Two, make Hubzilla's Articles app federate (optionally). It has comments already. Also, once that's done, have someone hard-fork it, port it to (streams) and offer it on a third-party git repository.

Als Antwort auf Scott M. Stolz

Yeah we did that originally. Article seemed like the best choice for long-form content. But Mastodon still filtered the HTML. I opened an issue to perhaps relax the HTML filtering on Article content, and Eugen responded by removing the Article content completely and forcing you to go through a link to see the post - and closing the bug as fixed. I believe that is the last time he and I ever corresponded.
Als Antwort auf Jupiter Rowland

Truth be told, it isn't too bad.

It's better to read a nicely formatted long-form article at its original source where it looks the way it's intended to look than to see its mangled remains on Mastodon. Even though it has been a bit less mangled since Mastodon 4.0.

Als Antwort auf Jupiter Rowland

In a way, it's similar to how in WordPress, you can choose to publish an excerpt or the whole article via RSS.

I don't mind Mastodon linking back to my website for an article. In fact, I prefer that. I WANT them to come to my website to read an article.

That is why I suggested that articles and social media posts be separate.

Personally, I would prefer:

* Articles - excerpt and link back to my website.
* Posts - send the whole post to the recipients.
* DMs - send the whole message to the recipient(s).