Conversation

@julian @Aaron Gray @Rimu Good luck making a standard for something that isn't even all the same all over the Fediverse.

Take replies as an example. Mastodon mimics Twitter. All posts are technically the same, whether they're replies or not. It makes absolutely no sense whatsoever for Mastodon to name replies something else than start/stand-alone posts.

On the other hand, there are many projects that have a concept of conversations. Threads aren't made up of posts and more posts, but of one posts and many of something different. So a reply is something vastly different from a start/stand-alone post and handled differently. Separate entry fields. Fewer features. Replies have a different set of recipients than start/stand-alone posts. Or you don't even own your reply to someone's post because that someone does.

This is the case for nodeBB, at least partially. It has been the case for Friendica since its inception almost 14 years ago when it was still named Mistpark. It has been the case for Hubzilla since its inception almost 12 years ago when it was still Red. It was and is the case for everything that came after Hubzilla, including (streams). It's the case for everything that mimics Reddit, i.e. Lemmy, /kbin, Mbin, PieFed, Sublinks etc. It's the case for Plume as well as the WordPress plug-in. And so forth.

In all these cases, it's counter-productive to use the exact same term for start/stand-alone posts and for replies.

On the other hand, the same term is used for different things on different projects which leads to confusion. On Mastodon, "community" is an unofficial word for loose gatherings of users who have something in common. On Lemmy, it means the same as a subreddit, basically a forum. On (streams), it means a server instance.

Like Hubzilla, (streams) can't use "instance" for server instances because an "instance" refers to an instance of a cloned channel. Speaking of which, for almost 12 years again, Hubzilla has been using "channel" for a kind of identity container that's unique to these two and completely alien to pretty much the whole non-nomadic rest of the Fediverse. So "channel" may refer to other things elsewhere.

If you really aim to create a common language for the whole Fediverse and make it pretty much mandatory, you'll have to get the developers of all projects (or "projects" because (streams) isn't one) on board. Otherwise they'll be overruled by a committee that has no idea what they're even doing.

For example, if both @Mario Vavti (Hubzilla) and @Mike Macgirvin 🖥️ (streams repository) are left out, and nobody in the committee has ever heard of Hubzilla and (streams) and their channel concept and nomadic identity, Hubzilla and (streams) will be forced to rename all kinds of unique features while not even having any words to name them anymore because they're all officially redefined otherwise, because the common Fediverse language was defined with complete disregard for nomadic identity.

Also, I expect two things to happen. One, everyone wants to keep their own language. Some may argue that it sets them apart from others which is the reason for Lemmy communities vs /kbin magazines. Others may argue for how long they've been using certain terms, especially Friendica, and they don't want these terms taken away by "intruders". Others again may just be stubborn and, in turn, try to push their language onto everyone else. The latter I can see happen with Mastodon whose representatives will argue that Mastodon is twice as big as everything else combined, maybe even in combination with fake news propaganda that Mastodon was here first.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Terminology

Public

Notices

Feeds