#mastodonapps — Public Fediverse posts

@Irina I'm pretty certain that there's some Mastodon phone app out there that does this fully automatically, and the users don't know about it.

The best would be to first ask them what app they use and then to ask the app developer(s) to stop this.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #MastodonApp #MastodonApps

@Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow

• only myself
• only certain contacts
• only my contacts
• only my contacts plus those with an unapproved contact request
• anyone on the same Hubzilla hub as me
• anyone on Hubzilla (strangely, this does exclude (streams) channels)
• anyone in the Fediverse
• anyone anywhere on the Web, even without a Fediverse account

to comment on my posts.

In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are

• only myself plus certain contacts
• only my contacts
• anyone in the Fediverse
• anyone anywhere on the Web, even without a Fediverse account

On top of that, I can generally allow comments only for a certain number of days.

Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps

@Arnan It doesn't fit the timelines in the official Mastodon phone app. Which has the only Fediverse user interface out there that cannot fold longer posts in.

The Mastodon Web UI can do that. All third-party Mastodon apps can do that. The Web UIs of just about the whole rest of the Fediverse from Pleroma and Misskey to Friendica and Hubzilla can do that. Phone apps for stuff that isn't Mastodon can do that.

Only the haphazardly developed official Mastodon app can't do that because it's geared towards a Fediverse with only 500 characters, a Fediverse of a kind that has never existed.

Mastodon is not the reference implementation of the Fediverse. And the official Mastodon app is not the reference implementation of Mastodon apps, much less of Fediverse apps. It only exists for there to be something official named "Mastodon" in the Apple App Store and the Google Play Store.

Just because Mastodon tossed out a lack-lustre app in 2022 for those who absolutely need something named "Mastodon" on their phones to access the Fediverse, doesn't mean that Fediverse software that has existed for almost six years longer than Mastodon and twelve years longer than that app must adapt to the existence of that app and cut down its character limit from 16,777,215 to 500 for all those who can't use Mastodon through something with another name on it than "Mastodon".

By the way: Mastodon's way of cutting longer posts up into tiny chunks of no more than 500 characters goes onto the nerves of users of Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, Sharkey, CherryPick, GoToSocial, snac, Hollo, Socialhome, Friendica, Hubzilla, (streams), Forte and others. But they are not allowed to complain about that, much less tell Mastodon users who do that to move someplace that offers them more characters.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonApp #MastodonApps #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters

@Droid Boy :coolified: @Der Achte Schwabe @Sascha Pallenberg 🇹🇼 ♻️ ⚡ Die offizielle Mastodon-App ist so ziemlich die schlechteste und unterausgestattetste Mastodon-App, die es überhaupt gibt.

Viele glauben, die sei die Referenz-App, weil es ja die offizielle App ist und offizielle Apps ja eigentlich immer fully-featured sind. Tatsächlich ist sie aber eine Verlegenheitslösung, damit es im Apple App Store und im Google Play Store überhaupt eine offizielle App namens "Mastodon" gibt, weil 99% der Twitter-Umsteiger erstmal danach suchen werden.

Was die nicht kann?

Beispiel: Beinahe jedes Fediverse-Frontend da draußen rollt lange Inhalte standardmäßig ein, und dann kann man sie händisch wieder ausrollen. Außer superminimalistischen "Damit es überhaupt eine Weboberfläche gibt"-Behelfs-Weboberflächen von superminimalistischen Serveranwendungen ist die offizielle Mastodon-App das einzige Frontend, das das nicht kann. Die ist gebaut worden in der Annahme, daß es im Fediverse nur Inhalte mit maximal 500 Zeichen gibt.

Dieses Manko in der offiziellen Mastodon-App ist wahrscheinlich einer der Hauptgründe, warum viele Mastodon-Nutzer sich über "lange Posts" mit über 500 Zeichen aufregen.

Ich frage mich gerade, ob sie in der Lage ist, Textformatierung anzuzeigen.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonApp #MastodonApps