One of the biggest elephants in the bigtech social media model living room is unnecessary duplication.
Of course, users having to create multiple dead-end accounts to connect to all these closed/monolithic platforms is legacy nonsense, but it gets worse. The systems have people posting the exact same things over and over again.
A particular example I observed on Truth Social reminded me of just how ridiculous this situation is.
Some creator (a music artist) had posted something... I checked out their profile/main page and the same post is repeated several times - apparently posted to multiple groups in addition to their general posting. I'm sure the same thing was also copy/pasted to all the other platforms they are on.
Creator-types have accepted this copy pasta salad serving method as normal. To reach/expand their audience among the various legacy bigtech platforms, it is the most obvious option. [I believe posting links to their own platform and encouraging fans/followers to connect directly (from any compatible decentralized platform) is a better idea.]
More on that here.
Since the 90's, I've advocated the use of open source software for many reasons. One of those reasons is self-reliance, or independence from [insert BigTechMegaCorp here]. Related to that is security, which I mean in a broad sense to include personal data privacy, online safety, fully auditable...
Groups, in general, exacerbate the duplicate/repetitive issues. Browse any platform with a "groups" feature and you'll find dozens of the same "group". Often with a number of users that are in several, if not all, the duplicate groups; and that make copy/pasted posts to every one of them.
Does there really need to be a dozen groups for "residents of [your town/city/county here]" or whatever category?
Is using more granular permissions and filter controls in a single larger group a better option than creating another copy group because some people can't get along, etc.?
The stupid way that TS (based on Mastodon) handles posting to groups takes the bigtech monolithic model idiocy to new heights. I'm sure there are other platforms with the same issue. But it's really quite ironic in this case; as Mastodon (which TS is derived from) is a decentralized/Fediverse platform. However, TS does not connect with any other Fediverse systems - they took a decentralized capable software and made it run like any other centralized bigtech system. The same situation with Gab [Mastodon de-federated], AFAIK.
Considering that decentralized cross-platform protocols/softwares for social media* have been in use for over a decade, all this duplication and repetition is just absurd to me.
- - Decentralized cross-platform systems (aka the Fediverse) allow users on many different systems to connect/communicate. Imagine commenting on some youtube channel or having a conversation with a friend on Fecesbook from your twitter/X acct
Here, if I wanted to post to multiple groups (and/or individuals) it's a matter of setting the permissions on the post - selecting those groups. One post, rather than multiple duplicates. The appropriate situations in which a generic identical post really should go to multiple groups is another matter though.
The use of sharing/re-posting (eg. here it's
Share This or Repeat This) and/or embedded content/links features should reduce a significant amount of unnecessary duplication. However, the implementation of these options vary so much across platforms that they end up being used improperly or simply ignored.
I recall, once upon a time on a social media platform far away, going through a process of downloading memes to upload and attach to posts because the embed or share features either didn't work or were so badly done they were useless. This platform features cloud storage with social media sharing permissions, so anything with proper permissions which I (or another user) have stored could be included within a post.
So the answer to this scourge of stupid social media software that promotes the very definition of insanity is; run your own social media platform which I'll gladly setup and provide the managed hosting for.
This message brought to you by the department of redundancy department.
PS - It does seem like I mentioned some topical technical details and left them hanging out on a limb... Maybe I'll complete those thoughts and give them closure in a future edit. Or maybe they'll just be reiterated in new posts for old times of redundant postings' sake. 
The Department of Redundancy Dept. approves this message.
