I don't know what constitutes a "good" example in your opinion, but I've got two examples of how bad AI is at describing images with extremely obscure niche content, much less explaining them.
In both cases, I had the describe one of my images, always a rendering from within a 3-D virtual world. And then I compared it with a description of the same image of my own.
That said, I didn't compare the AI description with my short description in the alt-text. I went all the way and compared it with my long description in the post, tens of thousands of characters long, which includes extensive explanations of things that the average viewer is unlikely to be familiar with. This is what I consider the benchmark.
Also, I fed the image at the resolution at which I posted it, 800x533 pixels, to the AI. But I myself didn't describe the image by looking at the image. I described it by looking around in-world. If an AI can't zoom in indefinitely and look around obstacles, and it can't, it's actually a disadvantage on the side of the AI and not an unfair advantage on my side.
So without further ado,
exhibit A: contains
- an image with an alt-text that I've written myself (1,064 characters, including only 382 characters of description and 681 characters of explanation where the long description can be found),
- the image description that I had LLaVA generate for me (558 characters)
- my own long and detailed description (25,271 characters)
The immediate follow-up comment dissects and reviews LLaVA's description and reveals where LLaVA was too vague, where LLaVA was outright wrong and what LLaVA didn't mention although it should have.
If you've got some more time,
exhibit B:Technically, all this is in one thread. But for your convenience, I'll link to the individual messages.
with
- an image with precisely 1,500 characters of alt-text, including 1,402 characters of visual description and 997 characters mentioning the long description in the post, all written by myself
- my own long and detailed image description (60,553 characters)
(1,120 characters I've asked for a detailed description).
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
AI #
LLaVA #
AIVsHuman #
HumanVsAIDamn I want to find out what that long, thin cock feels like when it hits my second hole.
Aside note:
As far as I know, you can only send
posts to a Friendica forum with an exclamation mark to have them forwarded to all members. But you cannot do that with
comments, not in a conversation whose (start) post did not go to that forum.
On Friendica and all its descendants, a reply is never a stand-alone post. It's always a comment on another post.
Thus, mentioning a Friendica forum in a comment with an exclamation mark is futile.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
FediTips From what I've read, a digital photograph is considered the default. So for brevity reasons, it
must not be mentioned.
Any other media
must be mentioned, whether it's a painting, a screenshot from a social media app, a scanned analogue photograph, a flowchart, a CAD blueprint, a 3-D rendering or whatever.
But an alt-text must
never start with "Image of", "Picture of" or "Photo of". That's considered bad style and a waste of characters and screen-reading time. If the medium is not mentioned, digital photograph falls into its place as a default.
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta How conversations work is not unified all across the Fediverse. Even how
connections work is not unified.
Mastodon has taken over the follower/followed principle from Twitter which is always illustrated with arrows with one point. A following B is illustrated with an arrow from A to B. A being followed by B is illustrated with an arrow from B to A. A and B following each other mutually is illustrated with one arrow from A to B and one arrow from B to A.
It appears to me that Friendica has adopted this to become more compatible with Mastodon. But its several descendants, created by Friendica's own creator, starting with Hubzilla, haven't.
Hubzilla, (streams) and Forte still have the bidirectional "connection" or "contact" as the default. It's illustrated with one arrow, but with one point on each end.
Also, all three understand a threaded conversation as an enclosed contruct entirely owned by the conversation starter. Everyone on these three who has the start post on their stream always actually has the whole thread on their stream.
In fact, all three have Conversation Containers implemented. This feature was in 2022. Forte has had it from the get-go as it started out as a fork of (streams). It was eventually turned into and backported to Hubzilla last year.
All three make sure that everyone who has a post on their stream also always has all comments on that post, at least those that are made after they have received the post.
This works on two basic principles:
- All comments go directly to the original poster because the original poster owns the thread.
- Those who have the post automatically receive all comments from the original poster.
In a pure Hubzilla/(streams)/Forte system, your above example would look like this:
- User 1 and User 2 are connected.
- User 1 and User 3 are connected. (This doesn't even matter.)
- User 2 and User 3 are connected.
- User 2 and User 4 are connected.
Much simpler than explaining everything with "following" and "being followed", isn't it
Now, the conversation works like this.
- User 2 sends a public post, thus creating a Conversation Container of which they are the owner.
User 1, User 3 and User 4 receive the post. - User 3 comments on User 2's post.
The comment goes from User 3 to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 4 who already have User 2's post on their streams. - User 4 comments on User 3's comment.
The comment goes from User 4 past User 3 straight to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 3 who already have User 2's post on their streams.
The only mentioning that occurs here, if any, is User 4 mentioning User 3. This is not necessary for User 4's post to reach anyone. This is only necessary to make sure on Hubzilla (which doesn't have a tree view) that User 4 is replying to User 3's comment and not to User 2's post.
On Mastodon, for comparison, everything depends on who follows whom, who mentions whom and whose instance knows whose instance.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
Conversations #
FEP171b #
ConversationContainersIn general, you've got two options.
If you don't add a title, Friendica sends the post as a Note-type object. Mastodon will show it with only basic text formatting, i.e. no tables, no horizontal lines, no custom typeface, no text size, no colour, numbered lists converted to bullet-point lists.
As for the images, Mastodon will not show any images within the post. It will show the first four as file attachments below the post, and it will completely ignore the rest because it can't handle more then four file attachments. Even this only works because Friendica, like its descendants, sends images both embedded in the the post and as file attachments. Still, Mastodon throws away all attached images except for four.
If you do add a title, Friendica sends the post as an Article-type object by default. (You can configure Friendica to send posts with titles as Note-type objects as well.) But Mastodon currently still refuses to render Article-type objects. Instead, it just shows the title and a link to the original. The reason for this is a somewhat longer story that involves Mastodon, and some headbutting between their creators and then-developers over full HTML rendering.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
Friendica #
Hubzilla #
ActivityPub neck. book of hours, England ca. 1300. Baltimore, Walters Art Museum, W.102, fol. 93r.
Find the latitdue and longitude of any place Since you're obviously new in the Fediverse, here's a bit of information that you may not know yet.
You cannot only follow Friendica accounts from Friendica. Neither can you only follow Mastodon accounts from Mastodon.
You can actually follow Mastodon accounts from Friendica. And vice versa, you can follow Friendica accounts from Mastodon.
In fact, you can follow just about
anyone anywhere in the Fediverse from both Mastodon and Friendica. For .
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FediverseFinal Fantasy IX:
. - , -, -- . , , .
My definition of "living under a rock":
is rapidly growing from people who escape from Facebook.
is outright
exploding from people who escape from Instagram.
But you still believe that is only Mastodon because even
the mere existence of Friendica or Pixelfed or still hasn't made it into your little Mastodon bubble yet.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Pixelfed #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverse Because if you want full-blown user rights and all the same features as a local user on
all over 30,000 Fediverse instances, you need a local user account on each one of them.
This means two things:
- If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.
- If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.
For one, this is utter overkill.
Besides, this is technologically impossible. This would require
all Fediverse instances to know
all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse.
And, of course, it would require a newly-launched instance to know
all Fediverse users. Again, with no exception.
How and from which source are they supposed to know
That said, there is a single sign-on system for the Fediverse. It's called . It was created by
Mike Macgirvin (creator of Friendica and all its descendants) in the late 2010s already for now-defunct , a fork (of a fork) of which, in turn, is a fork of the currently hyped Facebook alternative . It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing , got it, too.
However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere.
As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop.
Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so.
OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything.
For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile.
If you're logged out, and you go to my profile page, you see nothing.
But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile.
And all of a sudden, you see my profile.
That, for example, is what OpenWebAuth is for.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Friendica #
Hubzilla #
Zap #
Streams #
(streams) #
Forte #
SingleSignOn #
OpenWebAuth Friendica has only got client-side support, i.e. Hubzilla, (streams) and Forte recognise Friendica logins, but Friendica doesn't recognise
any logins.
Also, the instance that you visit while logged in must accept cookies. And if you're using Firefox and containers, the instance that you're logged in on and the instance that you visit must be in the same container.
But in general, this is technology from the late 2010s. Zap was declared stable with it in 2019. It was backported to Hubzilla in 2020, and it was immediately made available on everything that came after Zap.
At least for me, it generally works like a charm. Both Hubzilla and (streams) instances recognise my Hubzilla login if all precautions are met.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
OpenWebAuthNew entry of AI-generated and added to our :
The 's
And "part of the Fediverse" means that
everything is connected with everything else.You can follow Friendica accounts from Mastodon.
You can follow Instagram accounts from Mastodon.
You can follow PeerTube channels from Mastodon.
You can follow Mastodon accounts from Friendica.
You can follow Instagram accounts from Friendica.
You can follow PeerTube channels from Friendica.
And so forth.
. And it's all connected with each other just the same. I mean, what if I told you that this comment comes to you, to Mastodon, not from Mastodon, but from something called that has got absolutely nothing to do with Mastodon
What's absolutely unthinkable outside the Fediverse (being on Twitter and following Facebook users or YouTube channels from there, and Facebook users replying to your tweets from Facebook) is totally normal in the Fediverse. It's part of what makes the Fediverse the Fediverse.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Pixelfed #
PeerTube #
Friendica #
Hubzillahat tip John Oliver, Last Week Tonight. He's praising the resignation letter where she wrote "I expect you will find someone who is enough of a fool or enough of a coward to file your motion, but it was never going to be me" & he says she may as well have added "bitch" to the end. Clippy was twisted in a good way!
is Clippy
Here's another thing that you may not know about and yet: Not only do they have quote-posts, but they also have pretty effective anti-quote-post defences.
Hubzilla
Hubzilla has a permission setting named "Can source/mirror my public posts in derived channels". It has been there since 2012 when Hubzilla was still a fledgling project named Red, that's 13 years now.
Whether someone may quote-post ("share") your public posts depends on the setting in the channel role. If your channel is set to "Public", I think everyone is allowed to share your public posts. If it's set to "Private", you can (and have to) grant that permission to your connections individually by contact role. Those whom you aren't connected to are not allowed to share any of your posts.
The "Custom" channel role lets you choose between granting that permission, one out of 17 permissions, to:
- everyone in the Fediverse
- everyone on Hubzilla and (streams)
- everyone on your home hub
- unconfirmed and confirmed connections
- confirmed connections
- only those whom you individually grant that permission
- nobody but you
(streams)
(streams) goes even further. As far as I know, it doesn't give you the option to let everyone quote-post any of your posts in the first place. Not only are you always opted out to the point that only you yourself may quote-post your posts, but you can't even fully opt in.
No matter if your channel type is "Social - Public" or "Social - Restricted", the only ones who are allowed to quote-post even only your public posts are those of your connections who get the permission from you. Unlike on Hubzilla, however, you don't have to fumble around with permission roles, although you may do so to speed things up. You've also got a dedicated switch for this permission on each connection labelled "Grant permission to republish/mirror your posts".
The effect
This permission has its strongest effect on Hubzilla, (streams) and Forte: If one of their users is not allowed to share one of your posts, the Share button is missing altogether. And there's no real way around the Share button.
In fact, the Repeat button is missing, too. If you aren't allowed to quote-post it, you aren't allowed to boost it either. This permission is not about
how you may forward someone's content, but
whether you may forward it.
Unfortunately, Fediverse users probably everywhere else are not affected by this permission. Users of Pleroma, Misskey and their respective forks can still quote-post you to their heart's content. And I've got my doubts that Mastodon will understand this permission when it introduces quote-posts.
Then again, it's highly likely that Mastodon's quote-post opt-in or opt-out won't work outside of Mastodon either.
Privacy as an extra line of defence
If you
really want to be safe, you've additionally got the option to not post in public. Any post that isn't public can neither be repeated (boosted) nor shared (quote-posted).
Both Hubzilla and (streams) give you the option to send a post to the members of a privacy group/access list (think Mastodon list on coke and 'roids), to a specific group/forum or to any individual selection of connections of yours. (streams) also has Mastodon's option to send a post to all your connections Hubzilla can emulate that with a privacy group with all your connections in it.
Okay, your post will lose a whole lot of reach. But this is a trick that even Mastodon understands in a certain way: If a post from Hubzilla or (streams) has a restricted audience, Mastodon takes it for a PM. And you can't boost PMs, can you
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Hubzilla #
Streams #
(streams) #
PermissionsEchoes of Language
"A Long Way Home"
"Good! Go home, vamoose! And don't come back!"
These are all thats left of ours, the ones I came in with. , , from the 810th brigade got caught in the grinder, were in piss, sh*t, crap, and blood, Now were getting out of hell.
The surviving soldier shows those who survived.
Depends on the effort per post. It's one thing if it takes you no more than two minutes to describe one image,
any image.
But my own current standards for myself require me to invest several hours into description and explanation for a meme post based on a standard template. For one of my original images, I would need two days now. I would because I can't properly describe at least some of my old images. They're pictures of the past. What they show is no longer there. This means that I can no longer source all the detail informations necessary for an image description on my current level.
In fact, my current level, my current standard isn't even really defined. I'm working on a new series of image posts, I have been since last year. And I may or may not try something new, namely long image descriptions (not to be confused with the short image descriptions in the alt-texts) in little HTML files linked into the post. As long as I don't know if that's actually better than putting the long descriptions directly into the post, inflating it to a titanic size, I can't touch older posts anyway.
That is, if I added a full set of image descriptions to each one of my oldest images, I would also have to go and
upgrade my more recent image descriptions to my current standard. I don't want the quality of my image descriptions to tank at some point two years ago.
While I'm at it, I'd generally have to upgrade all my old posts in several ways. Placement of hashtags. Choice of hashtags, especially filter-triggering hashtags. Mastodon-style content warnings in the summary field, along with summaries, especially for any and all posts and comments that exceed 500 characters.
Trouble is, Mastodon doesn't understand edits from Hubzilla. All posts would go out to my hundreds of Mastodon connections on countless instances once more as brand-new. This would be extra awkward for posts about events that were years ago.
#
Long #
LongPost #
CWLong #
CWLongPost #
Fediverse #
Mastodon #
Hubzilla #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Hashtag #
Hashtags #
HashtagMeta #
CWHashtagMeta #
CW #
CWs #
CWMeta #
ContentWarning #
ContentWarnings #
ContentWarningMeta Truth be told, what we could need is a feature comparison between the various mobile apps and Friendica's Web frontend to see what covers what.
I'm not quite sure if any Friendica app actually covers exactly 100% of Friendica's functionality. What they
should cover is what's needed for daily driving. But I'm not sure if all of them cover, for example, all features of the built-in file manager and every last one of .
An actually, absoutely fully-featured Friendica app would be voluminous. Not as huge as a (streams) app and not as massive as a Hubzilla app, but big.
In the cases of some features, I'm not even sure how much sense they make in a mobile app. Would a
mobile app need all configuration controls for the Web interface And does it make sense for an iPhone app to brandish the full set of Friendica admin controls if it detects the logged-in account to be an admin account
Besides, in spite of its old age, Friendica is constantly changing and sometimes introducing new features. Third-party apps will have to keep up with core and add-on development.
And once the now-growing Friendica community has settled in and attracted a few devs, and they discover that Friendica is so modular that it can attach third-party add-ons server-side, and they start developing third-party add-ons, mobile apps won't cover 100% of Friendica anymore anyway.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
FriendicaApp #
FriendicaAppsA festival against the growing right wing has commenced in Dorenas World. It will continue over the weekend.
Line-up (all times PST/grid time)
Saturday, February 15th09:30-10:00 - Lead-in with Klarabella Karamell
10:00-12:00 - Wolem Wobbit live (on-going)
12:00-13:00 - live
13:00-open end - DJ Xenos Yifu
Sunday, February 16th07:30-09:00 - DJ Bogus Curry (ask me for his Fediverse ID)
09:00-11:00 - JohnWinston Vandyke live
11:00-12:00 - Reading with Kueperpunk Korhonen
12:00-13:00 - Rubeus Helgerud reads Wolfgang Borchert
13:00-open end - DJ battle between Klarabella Karamell and
Event location is the festival ground at .
#
Long #
LongPost #
CWLong #
CWLongPost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
VirtualEvent #
DorenasWorld #
Politics #
DEPol #
AntiRightWing #
AntiFascism Besides, Friendica has had quote-posts for almost 15 years as its primary method of sharing posts. It has continuously been federated with Mastodon for as long as Mastodon has been around. And stilll, there isn't a single known case of a Friendica user harassing a Mastodon user, or anyone else, by means of quote-post.
Just one example, the oldest one.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebateTodays NAPs Table of racing tips in UK & Ireland
with and exploring in on Den kann ich sogar noch ber.
Yes, it's that bad
I've read an interesting comparison the other day:
Mastodon is the Internet Explorer 6 of the Fediverse.It's underwhelming. It's underequipped. It lacks features that are standard just about everywhere else. It's actually hopelessly outdated. In fact, it's even
insecure, also due to how it lacks security features that competitors have readily available. And it ignores officially defined standards and tries hard to force the whole FediverseWeb to adopt its own non-standard solutions instead.
At the same time, however, for many many users, it
is the FediverseInternet, full stop.
For the vast majority of FediverseInternet users, it was the first Fediverse projectWeb browser they came across because that's what they were mouth-fed when they started with the FediverseInternet. For quite a long time, it was the only Fediverse projectWeb browser they even knew existed, and for many, it still is. Alternatives are only known to and used by the tech-savvy, and they're also the only ones who are aware of how dangerously lacking it is.
Thus, it has vastly more users than all its alternatives combined. Its market share is such that its developers don't even have to care for standards compatibility or what advantages the competition has. They can force their way upon everyone and everything.
Even many websites are built hard against only Mastodonthe Internet Explorer and malfunction or completely refuse to work with any of its alternatives, not seldomly because their developers don't even know that alternatives exist. And few developers dare to build websitesFediverse projects only according to HTMLActivityPub standards, even if that means breaking compatibility with Mastodonthe IE6.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Comparison #
Fediverse #
Mastodon #
NotOnlyMastodon #
MastodonIsNotTheFediverse #
FediverseIsNotMastodon #
InternetExplorer #
InternetExplorer6 #
IE6 (Selbst-Quote-Posten FTW! Man ist ja schreibfaul.)#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost #
Fediverse #
Mastodon #
NichtNurMastodon #
InternetExplorer #
InternetExplorer6 #
IE6 Und genau das wurde auf Twitter eingesetzt als Waffe gegen Angehrige von Minderheiten (BIPoC, 2SLGBTQQIA+ etc.). Im Grunde kennt man das als Twitter-User nur dafr.
Noch ein Grund, warum so viele von da nach Mastodon geflohen sind: weil Mastodon keine Quote-Posts/Drkos/Drukos hat.
Was aber kaum jemand auf Mastodon wei:
Das Fediverse hat sehr wohl Quote-Posts. Praktisch alles, was Mikro- oder Makroblogging macht und nicht "Mastodon" heit, kann quote-posten. Und kann auch Mastodon-Trts quote-posten.
Aussage, die ich gerade bekommen habe: Hubzilla und (streams) htten nie die Mglichkeit haben drfen, Mastodon-Trts zu quote-posten, weil Mastodon sich gegen Quote-Posts entschieden hat.
Nur: Zum einen war 2016 das Nichtimplementieren von Quote-Posts keine Entscheidung zum Schutz von Twitter-Flchtlingen, sondern zum Vereinfachen von Mastodon. Zum anderen mten wahrscheinlich mehr als 60 Fediverse-Serveranwendungen fr Mastodon eine Ausnahme einbauen.
Was fr Twitter-Flchtlinge auf Mastodon auch vllig unvorstellbar ist: Quote-Posts sind in fast 15 Jahren Friendica nie mibruchlich genutzt worden. Und berall sonst, was Quote-Posts kann, auch nicht.
brigens ist auch das wieder so ein Fall, wo Mastodon-Nutzer versuchen, dem gesamten Fediverse die Mastodon-Kultur aufzuzwingen und Features, die Mastodon nicht hat, wegzunehmen.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares Mastodon decided against quote posts so far, so Hubzilla and (streams) should not allow quoting Mastodon posts.
I mean, I could propose to Mike, Mario and Harald to automatically remove the Share button under any and all posts and comments from Mastodon, just to see their reactions.
But as a matter of fact, Pleroma and Akkoma can quote-post Mastodon toots just the same. The same goes for Misskey and its over 50 forks, including but not limited to JavaScript-based Iceshrimp which won't get any new features, Iceshrimp.NET which isn't officially released yet, Sharkey, CherryPick and Catodon. And Friendica can quote-post Mastodon toots, too.
Several dozen Fediverse server projects can quote-post Mastodon toots. They all would have to change. Or they all would have had to change the moment that it was decided that Mastodon lacks quote-posts to protect its users rather than to stay simple.
And where are you reading that Mastodon will reinvent the wheel To me it reads like they are working on Fediverse-wide interoperability for these features.
That has been Mastodon's track record since its very inception. I won't believe that anything has changed about this until Mastodon actually implements technology introduced by another Fediverse server project.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate It isn't just a matter of consent. Besides, for example, I do have quote-post control here on Hubzilla.
I can give permission to quote-post my posts to
- everyone in the Fediverse
- everyone on Hubzilla and (streams)
- everyone on this hub
- approved and unapproved connections
- only approved connections
- only those of my connections whom I explicitly give permission by contact role
- nobody but myself
Over on (streams), I can still give that permission to
- everyone in the Fediverse
- all my connections
- only myself + specific connections whom I grant that permission either by permission role or by individual connection settings
It's much more a matter of technology.
Mastodon is about to completely re-invent the wheel with a non-standard, Mastodon-only setting. This setting will only work within Mastodon simply because it probably won't even be documented anywhere, especially not before it's officially rolled out.
There simply is no way that every last instance of Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, CherryPick, Catodon, Meisskey, Tanukey, Neko, dozens of other Misskey forks, Friendica, Hubzilla, (streams), Forte etc. etc. will have that setting implemented
before Mastodon rolls it out so that even the users on mastodon.social are perfectly safe from the first second on.
Besides,
Mike Macgirvin , creator of Friendica, Hubzilla, (streams) and Forte and still the only maintainer of the latter two, will
never introduce proprietary Mastodon features to them. He'd rather risk (streams) and Forte becoming incompatible with Mastodon. The same goes for
Mario Vavti and
Harald Eilertsen, Hubzilla's main maintainers.
If Mastodon wants to become a perfectly safe haven against unallowed quote-posting, it has only got one choice: It must introduce something like (streams)' and Forte's user agent filter and use it to block just everything that isn't Mastodon. Like, include a hard-coded allowlist that only includes Mastodon plus what little can't quote or quote-post anyway.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Calckey #
Firefish #
Iceshrimp #
CherryPick #
Sharkey #
Catodon #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate And yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment,
you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:
- channel-wide (who is generally allowed to reply Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Hubzilla #
Streams #
(streams) #
Forte #
ReplyControls Keep one thing in mind:
Mastodon may not have quote-posts yet. But
the Fediverse has quote-posts right now. And it has had them since before Mastodon was made.
Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, CherryPick, Catodon, Meisskey, Tanukey, Neko, dozens of other Misskey forks, Friendica, Hubzilla, (streams), Forte etc. etc., they all have quote-posts. They're all fully capable of quote-posting any Mastodon toot.
None of them has introduced quote-posts to harass Twitter refugees on Mastodon. At least Friendica and Hubzilla have had quote-posts since long before Mastodon was even made.
You will be able to choose whether your posts can be quoted at all.
At least by Mastodon users.
But since this will be Mastodon re-inventing the wheel with brand-new, proprietary, Mastodon-only technology, everything I've listed above will still be able to quote-post anyone and anything on Mastodon with zero resistance.
To quote-post myself and the guy who invented Friendica, Hubzilla, (streams) and Forte:
I think I've just chased someone out of the Fediverse.
That someone was afraid of Mastodon being "screwed over" by becoming quote-post-able.
I've told him the truth: Mastodon has been quote-post-able for as long as it has been around. Mastodon became quote-post-able the very moment it was launched.
That's because when Mastodon was launched, it immediately federated with Friendica which is from 2010, which had been around for almost six years at that point, and which has had quote-posts from its own inception AFAIK. Mastodon also immediately federated with Hubzilla which has had quote-posts since its own inception, since it had been forked from Friendica, and that was in 2012.
Mastodon has never been un-quote-post-able.Right now, there are
dozens of Fediverse server apps whose users can quote-post Mastodon toots with no resistance.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate The closest you'll ever get to making Mastodon un-quote-postable is to post privately. Not unlisted. Private. Most fediverse software will honour this today and it doesn't require yet another "pretend permission". Like unlisted.
And Mike should know. He brought things to the Fediverse like actually working permissions. Including permissions on two levels to quote-post any content on a channel. Readily available right now at least on Hubzilla, (streams) and Forte.
Also,
this is what people on Friendica and its descendants have been using quote-posts for since 2010.
You will be notified when someone quotes you.
You already are when someone on Friendica, Hubzilla, (streams) or Forte quote-posts one of your posts.
As for Pleroma, Misskey and their forks, you aren't notified right now, and I've got my doubts that you will be after this change.
Also, "quote" and "quote-post" are two different things. Friendica, Hubzilla, (streams) and Forte can do both. "Quote" is what I'm doing right here. Whether or not you're notified depends on whether or not you're mentioned.
And blocking quotes is even less possible. A quote only consists of a pair of BBcode tags plus the quoted text in-between. And on Friendica and all its descendants, you don't work with a WYSIWYG editor by default, but you have to get your hands dirty on raw markup code.
You will be able to withdraw your post from the quoted context at any time.
Again, probably not if someone on Pleroma, Misskey or one of their forks quote-posts you.
And
definitely not if someone on Friendica or one of its descendants quote-posts you.
The difference is that a quote-post on Pleroma, Misskey or one of their forks is actually a reference to the original. On Friendica and its descendants, a quote-post is an automatically generated dumb copy of the original.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Calckey #
Firefish #
Iceshrimp #
CherryPick #
Sharkey #
Catodon #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate Eigentlich lt sich das Phnomen einfach erklren.
- 50% der Leute hinter den Kampagnen glauben, das Fediverse ist nur Mastodon. Die leben in ihrer reinen Mastodon-"Blo kein Tech-Nerd-Kram"-Blase komplett hinterm Mond.
- 20% glauben, das Fediverse ist nur Mastodon, Pixelfed und PeerTube und vielleicht noch Loops, weil sie von etwas anderem noch nicht gehrt haben.
- 10% haben von Alternativen zu Mastodon schon namentlich gehrt, aber eben nur das. Sie knnen sich nicht vorstellen, da irgendwas besser ist als Mastodon.
- 10% haben vielleicht auch davon gehrt, da z. B. Misskey oder Friendica Mastodon in Sachen Features berlegen sind. Es ist fr sie aber immer noch komplett unvorstellbar, da die einzelnen Fediverse-Serveranwendungen untereinander verbunden sind. Sie glauben, von Mastodon aus kann man nur Mastodon-Konten folgen, von Pixelfed-Konten aus nur Pixelfed-Konten, von Friendica-Konten aus nur Friendica-Konten usw.
- Die brigen 10% wissen auch letzteres, und zwar sptestens, seit ihnen ein "berlanger" Post von Friendica ber den Weg gelaufen ist und sie sich mit dem Nutzer dahinter gezofft haben, weil der sich weigert, seine "Trts" auf maximal 500 Zeichen zu beschrnken. Aber das sind die fanatisierten Fundamentalisten. Die wollen, da alle nach Mastodon kommen und im Prinzip das ganze Fediverse zu Mastodon wird.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodonFINAL FANTASY TACTICS
Final Fantasy Tactics - , , - . .
First of all, I apologise if you already know this, but there are so many who have been on Mastodon for much longer than you, and who don't know: If you want to follow Friendica users, you can do so from Mastodon. Even though Friendica and Mastodon are fundamentally different. You don't need a Friendica account just for that. You'd only need a Friendica account if you personally need Friendica's extra features.
First of all, why are they so different Why are they so much different that it may cause friction with Mastodon Why didn't they make Friendica more like Mastodon
Because "they" (actually originally one man in Australia, now two guys in Germany) made it
before Mastodon. Friendica first came out in July, 2010. Mastodon first came out in January, 2016. Five and a half years later. And immediately when Mastodon was first released, it was federated with Friendica. And it has continuously been ever since then.
Also, Friendica has never aimed to be a full-on, all-out Facebook
clone. Its goal has always been to be "like Facebook, but better than Facebook". So it is different from Facebook. It doesn't look like Facebook, it doesn't feel like Facebook. It just does what Facebook does with extra stuff on top.
As Friendica is so much older than Mastodon and developed entirely independently from Mastodon, don't expect it to be anything like Mastodon either. Half of what you know about Mastodon you can toss out of the window when you join Friendica and re-learn it.
Now, the first difference between Mastodon and Friendica is: Mastodon being like Twitter means that it's
social media. It's about
following accounts and consuming their content, it's about others following your account and consuming your content.
Friendica is like Facebook. It's true
social networking. It's about
people connecting with people. Even though Friendica has adopted the "follower" and "followed" wording from Mastodon, its default is still the bidirectional connection. Maybe you still remember that you didn't follow people on Facebook, and they didn't follow you back, thus creating two unidirectional connections. You didn't have followers, you didn't follow,
you had "friends" which always went into both directions.
"Social networking" also means that on Friendica, much unlike on Mastodon, you don't follow people because of their content first and foremost. Friendica is more geared towards connecting with people because of their profiles. A Mastodon profile has not even half a dozen text fields. A Friendica profile has
well over a dozen. Including a dedicated text field for keywords.
This contributes to the directory being much, much more useful on Friendica than on Mastodon. You can search the Friendica directory for names. You can search it for keywords. It comes with a keyword cloud. And it has a "suggestion" mode in which Friendica matches other profiles with yours.
So you're into dogs. You add "dogs" to your keyword field. Someone else has "dogs" in their keyword field. And what do you know, they slide up your list of suggestions! Also, I guess (I've been out of Friendica for many years, using two of its surviving descendants instead this comment comes from ) that connections of your connections move to the top of the suggestions, too. Just like on Facebook. Key feature on everything that's truly social networking.
There's even a .
Discussions on Friendica are better than on Mastodon. That's because Friendica, just like Facebook, like Tumblr, like a blog, like a forum, like almost everything that isn't Twitter or Mastodon, has threaded conversations. It's fully aware of entire threads. A conversation is not loosely tied together from posts and more posts like on Mastodon. Instead, it's an enclosed object with exactly one post. The start post. And otherwise any number of comments. Which are totally not posts.
Now, what does that mean in practice Let's play through a conversation that entirely happens on Friendica.
Imagine you're connected with Alice. Alice posts something. You receive Alice's post on your stream (= timeline).
Bob comments. You are not connected with Bob. Bob doesn't mention you. In fact, Bob doesn't mention
anyone. But still, Alice knows about Bob's comment because it's listed as an unread activity. And you know about Bob's comment, too, because it's listed as an unread activity for you as well.
By the way: Unread activities. Another thing that doesn't exist on Mastodon. On Mastodon, you read your unread stuff by scrolling and scrolling and scrolling through your timeline and scrolling some more until either you hit the stuff that you've already read, or until you've got no more time and/ore spoons to read any more. If the latter, there'll inevitably be a whole lot of toots that you'll never know about. On Friendica, you have a counter and a list of posts and comments that you have not read yet. And you can go through it by and by, until there's nothing anymore that's unread. Luckily, Friendica doesn't show you posts and comments one by one, but it always shows you entire threads.
Okay, back to the conversation: Carol comments on Bob's comment on Alice's post. Carol only mentions Bob to make sure that she's replying to Bob rather than directly to Alice. Again, the mention is not needed for Bob to see her comment. She doesn't mention Alice either, she doesn't mention you, and you aren't connected with Carol.
But yet again, Carol's comment is listed as an unread activity.
Now you want to check Alice's post, Bob's comment and Carol's comment. Again, you don't have to check them one by one. If you click either, Friendica will show you the whole conversation at once. Like a post on Facebook with comments below. Like a blog post with comments below. And it will mark Alice's post, Bob's comment and Carol's comment as flagged.
This is how conversations should be. Always. You have a post on your stream, you get
all the comments on it. At least all that come in after you've received the post.
But Friendica goes even further: It has groups. Discussion groups. Like forums. It has always had them. I mean, Facebook has always had groups, too, right Basically, after you've joined a group, you receive all posts from that group plus all comments under these posts. And if you post to a group, everyone in the group receives your post. All without fumbling around with hashtags and hoping people on other instances happen upon your post by searching for that hashtag.
Now you may say that Mastodon has Guppe groups. Yeah, but they're a glued-on hack made by someone who probably thought the Fediverse is only Mastodon. They can't be searched for whereas . Speaking of public groups, they can be private. As in, outsiders can't see the profile, outsiders can't see the posts in the group, and they aren't listed in any directory. Also, Friendica groups can be moderated. Guppe groups can't.
What else Posts. You can
do more in a post on Friendica than you can
see on Mastodon.
Vanilla Mastodon is limited to 500 characters. It can be raised, but not by configuration. Raising the limit requires hacking into the source code and usually having to do so after each Mastodon upgrade.
Friendica, as far as I know, is "limited" to 200,000 characters. At the same time, as far as I know, Mastodon rejects posts from outside if they're longer than 100,000 characters. Friendica lets you write posts that are so long that Mastodon refuses to even import them.
Friendica supports all kinds of text formatting. Mastodon can display bold type, italics, maybe underline, also bullet-point lists, quotes (it still can't display quote-posts which Friendica has had from the get-go as well), well, and that's about it. Friendica can
create all this and more. Much more. If you can do it in a blog post, you can do it on Friendica. Maybe even more than that.
A very good example is how Friendica handles images. Mastodon can only handle images as file attachments and only four of these. If you only know Mastodon, you perceive this as the one and only Fediverse standard, and you can barely imagine that it could possibly be any different. That's because Mastodon can only handle images with these limitations in content from outside as well.
Friendica, on the other hand, is not limited in how many pictures you can have in a post. And it can actually have pictures
in a post. Embedded within the post. With text above the picture and more text below the picture and another picture below that text and so forth. Just like a blog.
Since Mastodon refuses to render embedded in-line images, Friendica actually has to additionally convert all imported images into file attachments which Mastodon understands. But even then, Mastodon will throw all of them away except four if you have more than four.
How does Friendica do that Well, part of the secret is because Friendica has its own cloud file space built into each account. If you upload an image to Mastodon, it ends up somewhere where you can't access it. If you upload an image to Friendica, it ends up in your cloud file space. With its own little file manager. Which even supports folders and subfolders.
In fact, Friendica even has image gallery functionality!
That said, as Friendica is so much different from Mastodon, and particularly, since it's so much older than Mastodon, it has its own culture which is rooted in a) its vast set of features and b) the early 2010s. Friendica has never adopted Mastodon culture, and it never will. That's because Mastodon culture clashes so much with Friendica's native culture and with Friendica's features.
For example, Friendica users happily churn out posts and comments which at least some Mastodon users perceive as so long that they're disturbing. Namely over 500 characters long. Ask a Friendica user to chop their long posts into threads with never over 500 characters, and you will not receive.
Friendica users do stuff in their posts that Mastodon won't render. This includes embedding images and more than four. If Mastodon won't render them, then from a Friendica point of view, it doesn't mean that Friendica is using some non-standard freak feature that should be avoided. It rather means that Mastodon is broken. And if the Mastodon devs refuse to fix it, then Mastodon is broken by design.
This may come as a surprise to you, but: Mastodon's CW field was not invented from scratch as a CW field. Originally, it's a summary field. It's a summary field on Laconi.ca/StatusNet/GNU social. It's a summary field on Friendica (where it's called "abstract"). It's a summary field on everything that came after Friendica. But in 2017, someone proposed to make it a CW field on Mastodon. Ever since then, everyone on Mastodon "knows" that this field is purpose-made for CWs and for CWs only.
Again, on Friendica, it's for summaries. Friendica users either use it for a summary (and even then, this involves a pair of BBcode tags), or they don't use it at all.
At the same time, Friendica historically, and to this day, handles CWs differently: It generates them on the reader's side. Automatically and only if you want to. For this, it has an optional, very basic filter-like feature named "NSFW" that comes with not much more than a keyword list. If a keyword from that list is in a post or a comment or a PM, the whole thing will be automatically hidden behind a button. Much like a Mastodon CW, but unlike a Mastodon CW, it's only rendered for you (and everyone else who has that keyword on the list) and not forced upon everyone all the same.
(By the way: Mastodon has introduced the self-same functionality to its filters with the release of Mastodon 4.0 in October, 2022. But even though this was right before the biggest Twitter-to-Mastodon migration wave ever, nobody knows about this.)
This leads to culture clash:
- Mastodon users are disturbed because Friendica users don't add CWs to sensitive content.
- Mastodon users are extra disturbed because Friendica users "spam" their posts with hashtags. These hashtags are used to trigger the generation of reader-side CWs which are not part of Mastodon's culture because nobody knows they exist, and because they didn't exist in mid-2022 when Mastodon's culture was (re-)defined.
- Mastodon users are extra special disturbed because Friendica users "misuse" the CW fields for "like, titles or summaries or whatever that stuff is".
- Friendica users are disturbed because Mastodon users misuse the abstract field for CWs without even adding an actual abstract.
- Friendica users are extra disturbed because Mastodon users don't add keywords or hashtags to trigger their NSFW.
Also, Mastodon users mute or block Friendica users because they post over 500 characters at once. In turn, I know at least one Friendica user who blocks everyone upon first strike who chops a longer post into a thread with never more than 500 characters in one message. Friendica users are perfectly used to posts with 10,000 characters, but they find the same posts cut into threads with over two dozen tiny posts cumbersome and tiring.
Before mid-January, 2025, accessibility didn't play any role on Friendica. The old Friendica guard saw alt-text as another dumb fad from Mastodon's stupid and ignorant culture that perceives the Fediverse as only Mastodon. Not to mention that adding alt-text to images on Friendica is still kind of cumbersome because next to nobody has ever actually considered using that feature until very recently.
Interestingly, Zuckerberg's further enshittification of Facebook which triggered a slow but steady migration wave from Facebook to Friendica also coincided with the very first time ever that a Friendica veteran (the same guy who blocks thread posters) was asked to add alt-text to an image. Which must have been a rather disturbing experience for him.
Another cultural difference concerns connections with other software and platforms. Still today, over half of all Mastodon users think the Fediverse is only Mastodon. And truth be told, many many Mastodon users would love the Fediverse to actually be only Mastodon. Anything that connects with Mastodon and sends content to Mastodon is seen as rogue, culture-less intruders.
On Friendica, in a stark contrast, connection with anything and everything has been an integral part of the concept, of the philosophy and thus of the culture from the very beginning on.
Friendica doesn't only communicate through ActivityPub which it didn't even support until 2019 (it also has its own protocol, DFRN). Even then, it has a much more complete and standard-compliant ActivityPub implementation than Mastodon.
It can also connect do diaspora*, another much less feature-rich "Facebook killer" from later in 2010 which refuses to support any protocol other than its own, and which actually doesn't aim to federate with anything else (all the cross-project federation work was entirely done on Friendica's side). If you've been intensively using Friendica for at least a year or two, it's absolutely normal to have contacts on diaspora*.
It's also one of the very last Fediverse projects that still support OStatus, the old protocol used by GNU social, formerly StatusNet.
It can integrate Bluesky accounts so you can connect to Bluesky without the Bridgy Fed bridge and without Bridgy Fed's limitations. It can integrate Tumblr accounts. It could theoretically still integrate accounts if the node admin had the millions for an API license. In the early 2010s, it was even able to integrate Facebook accounts. It can natively crosspost to WordPress and Libertree.
It can subscribe to RSS and Atom feeds while generating Atom feeds itself. It can communicate via e-mail. And its chat has at least basic XMPP compatibility.
Friendica's credo is something like, "If it exists, we federate." Mastodon's credo rather seems to be something like, "There's Mastodon, there's evil, there's broken, and there's both broken and evil. If it isn't Mastodon, it'd better not disturb us."
In fact, most Mastodon users barely notice the Fediverse outside Mastodon, also because they barely identify content from outside of Mastodon as such. Another reason why they try to force Mastodon's culture upon non-Mastodon users: They don't even notice that these aren't Mastodon users at all.
Friendica users are fully aware of how colourful the Fediverse is, also because Friendica's Web UI actually tells you where a post or a comment came from. They still find the behaviour of many Mastodon users disturbing and tiring. But they're more aware that Mastodon has its own culture, and they don't try to force Friendica's culture upon users of something that isn't even technologically fit to adopt Friendica's culture.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
MastodonCulture #
Friendica Friendica apps are generally installed and work on your local device.
Friendica's own frontend can be modified extensively with themes built into a node. But there are no full-blown third-party frontends that completely replace Friendica's built-in frontend like Phanpy fully replaces Mastodon's frontend or Mangane fully replaces Pleroma-FE and Akkoma-FE.
Currently, the only platform that gives you a selection of alternative, third-party frontends that fully replace Friendica's frontend is Android because there are quite a few dedicated, native Friendica apps available for Android.
On Windows or Linux, all you can do is install . But it's an early and not entirely open beta, it's very incomplete and unfinished, and to my understanding, it still lacks important features.
On a Mac or an iPhone, you're completely out of luck. Again, there's only Relatica which is just as unfinished and incomplete as on Android, Windows and Linux. But Relatica for macOS and for iOS is which requires an account on in order to get into contact with the Relatica developers.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
FriendicaApp #
FriendicaAppsOmar, candidat au chat le plus long du monde
Nia Long
Ich bleibe trotzdem dabei: Ein "Ich zeig dir, wie sich das mit Erde und Sonne verhlt - dann wird dir einiges klarer und leichter." finde ich einladender.
Selbst das fhlt sich doch fr nicht wenige Mastodon-Nutzer schon wieder wie bergriffiges Reply-Guying an, wenn sie nicht explizit genau danach gefragt werden. Und die allermeisten fragen gar nicht erst. Schon kriegt man auf den Deckel.
Ich sollte die Hashtags #
Fedisplaining und #
CWFedisplaining wieder hufiger benutzen, wann immer ich ungefragt etwas erklre, damit die Leute noch mehr zum Filtern haben. Ich mu berhaupt wieder mehr darauf achten, auch wirklich alle wichtigen Hashtags zum Filterauslsen einzubauen. Auch wenn ich dann auf den Deckel kriege, weil ich mehr als vier Hashtags verwende.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
ReplyGuy #
ReplyGuys So unterschiedlich sind die Wahrnehmungen zwischen reinen Mastodon-Nutzern und Nicht-Mastodon-Nutzern. Das erfahre ich immer wieder.
Auf der einen Seite ist da die breite Masse der Nur-Mastodon-Nutzer und Nur-Mastodon-Kenner. Ich wage zu behaupten, auch wenn besonders aktuell geradezu explosiv wchst, weil viele von Instagram abhauen, bleibt das auf Mastodon, vor allem dem deutschsprachigen Mastodon, weitestgehend unbemerkt. Auch das allmhliche Wachstum von durch Leute, die von Facebook umsteigen, merkt man auf Mastodon kaum.
Resultat: Wahrscheinlich immer noch weit mehr als die Hlfte aller Mastodon-Nutzer ist immer noch der Ansicht, da das Fediverse nur aus Mastodon besteht.
Dazu zhlen Leute, die schon seit drei, vier oder noch mehr Jahren dabei sind und haufenweise Kontakte haben. Aber entweder schaffen sie es, obwohl sie aberhunderten oder gar abertausenden Leuten folgen, ausschlielich Leuten auf Mastodon zu folgen, die auch wieder nur Leuten auf Mastodon folgen. Keiner von denen hat a) Ahnung vom Fediverse und b) Interesse am Fediverse. Und so bekommen sie vom Fediverse auerhalb von Mastodon nichts mit. Oder sie bekommen stndig Posts und Kommentare von auerhalb von Mastodon rein, erkennen diese aber nicht als von auerhalb von Mastodon. Und auch darin redet niemand vom Fediverse auerhalb von Mastodon.
Aktuell die Fluchtbewegung von Instagram nach Pixelfed, von TikTok nach Loops, von Facebook nach, na ja, wohin auch immer die Facebook-Flchtlinge gelotst werden, all das erzeugt eigentlich einen Riesenrummel im Fediverse. Aber ihre Kontakte scheinen davon nichts mitzubekommen, deren Kontakte auch nicht, und so merken sie selbst auch nichts davon. Auch von Flipboard oder von der ActivityPub-Integration in WordPress haben sie nie etwas mitbekommen. Das meine ich mit "hinterm Mond".
Bisher dachten aber Leute wie (auf Friendica),
(auf ) oder ich (auch auf Hubzilla), da es schlecht und behebenswert wre, wenn Leute glauben, das Fediverse ist nur Mastodon. Und nicht der unverrckbare Normalzustand, den es bitteschn zu respektieren gilt.
Ich kenne im Fediverse einige, die eben gerade nicht wie 99,999% aller Fediverse-Nutzer irgendwann in den 2020ern von Twitter nach bzw. ber Mastodon gekommen sind. Statt dessen sind sie schon sehr viel lnger im Fediverse und noch dazu auf Anwendungen unterwegs, die nicht nur nicht Mastodon sind (aber trotzdem voll mit Mastodon verbunden), sondern
sehr extrem nicht Mastodon. Die fundamental anders sind als Mastodon.
Das heit auch: Wir erleben das Fediverse anders als die breite Masse, die nur Mastodon kennt. Wir erleben, wie aus Unwissenheit ber das Fediverse jenseits von Mastodon der Unwille wird, etwas ber das Fediverse jenseits von Mastodon zu lernen. Und daraus Ignoranz und Borniertheit. Und daraus eine totale Mastodon-Zentrizitt und Mastodon-Normativitt. Und daraus die stndige Diskriminierung des Nicht-Mastodon-Fediverse. Ja, Diskriminierung. Nur weil Mastodon-Nutzer sie nicht wahrnehmen, heit es nicht, da sie nicht existiert.
Beispielsweise versuchen nicht wenige von diesen Leuten, die Mastodon-Kultur, die Mitte 2022 auf der Grundlage von Mastodon 3.x (und auch nur darauf) entstanden ist, mit aller Gewalt im ganzen Fediverse durchzusetzen.
Da wird dann ein (Calckey, standardmig 3000 Zeichen) von einem Mastodon-Nutzer angeschnauzt, er habe geflligst lange Posts in Threads aus Schnipseln von nicht mehr als 500 Zeichen zu zerhacken oder sich geflligst aus dem Fediverse zu verpissen. Weil das ganze Fediverse bitteschn nur Standard-Mastodon zu sein hat.
(Wahrscheinlich wrden sich umgekehrt tausende von Mastodon-Nutzern aufregen, wenn sie wten, da (Friendica, 200.000 Zeichen) jeden sofort blockt, von dem er auch nur einen einzigen Schnipsel-Thread empfngt.)Da kloppt sich derselbe mit einem Tech-Journalisten, der felsenfest darauf beharrt, da es ein in sich geschlossenes Mastodon-Netzwerk gibt und Crossgolf (und einige andere Nutzer von z. B. Akkoma, Friendica, Hubzilla usw.) als ahnungslose Idioten beschimpft, weil die etwas anderes behaupten.
Da wird ein
Jakob (Friendica) von einer Mastodon-Nutzerin nach kurzem Disput stante pede geblockt. Weil er Friendica nutzt. Weil sie glaubt, er sei ein bser Hacker, der sich mit seinem bsen Hacker-Tool namens "Friendica" illegalerweise ins Mastodon-Fediverse reingehackt hat, um da Mastodon-Nutzer anzugreifen oder so.
Da wird etwas entwickelt namens .
FEDIDevs. Aber es wird vollumfnglich hart nur gegen Mastodon gebaut ohne Rcksicht auf irgendetwas anderes. Ohne da auch nur in Erwgung gezogen wird, da es im Fediverse auch noch was anderes als Mastodon geben knnte. "
FEDI" impliziert doch, da es fr das ganze Fediverse ist. Ist es aber nicht. Erst vor kurzem ist auch fr die ersten paar anderen Fediverse-Serveranwendungen die Mglichkeit eingebaut worden, sich mit Konten dort zu registrieren. Und bis heute knnen in den nur Mastodon-Konten eingetragen werden.
Noch dazu
wollen viele gar nichts ber das Fediverse lernen. Sie wollen viel lieber auf dem "Fediverse gleich Mastodon"-Stand bleiben. Fr immer. Denn so gefllt ihnen das Fediverse am meisten: wenn es nur Mastodon ist.
Jeglicher Versuch, sie darber zu informieren, was und wie das Fediverse tatschlich ist, ist dann gleich bergriffiges Reply-Guying und Mansplaining/Fedisplaining, und sie haben jegliches Recht oder gar die Verpflichtung, sich dagegen zu verteidigen.
Das fhrt dann dazu, da Nutzer von Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon, Neko, GoToSocial, Mitra, micro.blog, Socialhome, Friendica, Hubzilla, (streams), Forte, Lemmy, /kbin, Mbin, PieFed usw. usf. praktisch permanent auf Eierschalen laufen. Das, was sie benutzen, ist so anders als Mastodon, da es fr Mastodon-Nutzer strend ist. Die Art und Weise, wie sie es gem ihrer eigenen Kultur benutzen, ist auch wieder so anders als die Mastodon-Kultur, an die die Mastodon-Nutzer gewhnt ist, da es auch wieder fr Mastodon-Nutzer strend ist.
Warum habe ich denn unter meinen Posts und Kommentaren so einen Wust an Hashtags, wenn auch nur die geringe Chance besteht, da sie bei irgendjemandem auf Mastodon landen knnten Vor allem die, die mit
#CW
anfangen Damit empfindliche Mastodon-Nutzer was zum Filtern haben.
Umgekehrt drfen aber Mastodon-Nutzer sich auffhren wie die Axt im Walde. Sie drfen Friendica-Nutzer, die schon seit zwlf Jahren dabei sind, anschnauzen, sie drfen ihnen den Befehl erteilen, sich ab sofort nur noch an die Mastodon-Kultur zu halten, und sie drfen ihnen indirekt befehlen, die sehr viel ltere und sehr viel besser an Friendica angepate Friendica-Kultur fr immer aufzugeben. Und 80% von Friendicas Features gleich mit, weil Mastodon 3.x die nicht hatte und sie daher nicht Teil der Mastodon-Kultur ist.
Wenn sie wten, da...
- derjenige auf Friendica ist und nicht auch auf Mastodon
- Friendica vllig anders ist als Mastodon
- es so gewollt ist, da Friendica vllig anders ist als Mastodon
- Friendica ein vllig anderes Konzept hat als Mastodon
- Friendica vor allem lter ist als Mastodon, und zwar gute fnf Jahre
- Friendica seine eigene Kultur hat, die auch wieder lter ist als die von Mastodon
...dann wrden sie sich vielleicht migen.
Nicht nur wissen sie davon aber nichts, sondern sie wollen es nicht wissen. Und sie haben alles Recht, jedem, der versucht, ihnen davon auch nur ein bichen zu erklren, wegen bergriffigkeit, Reply-Guying und Mansplaining/Fedisplaining auf den Deckel zu geben.
Ernsthaft, ich wnschte, Leute, die erst seit ein paar Monaten oder Jahren auf Mastodon sind, knnten wenigstens kurzzeitig das Fediverse aus der Sicht von jemandem sehen, der seit acht Jahren auf Friendica oder Hubzilla ist.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon Forschungsnetzwerk zu Long Covid gestartet: Am Montag ist ein Netzwerk zur Erforschung von Langzeitfolgen von Covid-19 (Long Covid) gestartet. Ein weiteres Netzwerk aus Modellpro...
One of the worst things that can happen in an grid, except its complete and permanent shutdown, is the inventories of all avatars being wiped clean. It has happened in Metropolis, I think, in 2019. Many of those who were around back then decided to move away to another grid that promised to be more reliable. Those who were AWOL returned later, just to find their inventories completely empty and their avatars consisting of only the white, textureless system body. In either case, their inventories didn't even contain the "building blocks" for standard Ruth, and when they returned, a blank skin, a blank shape, blank hair and blank eyes had to be created on the spot.
Except for what they had installed in-world, if anything, they had to start over from scratch. Not exactly few decided to do so on another grid, basically starting Metropolis' shrinking process.
Now, Metropolis was one of the oldest grids, launched in 2008. When it was shut down in 2022, it was the fourth-oldest grid. For a while, it even used to be bigger than OSgrid. But this age also meant it was dragging around a whole lot of old assets that were no longer in use.
is even older. Except for maybe the odd impromptu private test grid to get recently-created OpenSim running, it has always been the oldest grid. It was launched in 2007, so it's a whopping 17 years old now. Also, for most of the time, it has been the biggest grid and basically the "lighthouse instance" of OpenSim where almost all newbies ended up.
In other words, a whole lot of people contributed to the filling of what has been one of the most troubled asset servers in OpenSim for years already. The admins had tried quite a few things over the last few years to improve the situation, only to worsen it. Assets in inventories were broken or missing altogether. Announcements that the situation would normalise in a few months (with an increasing number of months estimated) never came to pass.
What was identified as a major issue are assets that don't exist in-world, and that are broken or faulty to begin with. Some may only exist on the asset server, but others linger in the inventories of avatars, many of which haven't been used in years. A lot of these were stolen from Second Life and haphazardly imported, or they broke upon export already.
So they decided to take this last resort and reset all inventories to get rid of broken content. The announcement came yesterday.
But as it seems, they've received a whole lot of criticism. They may also have been reminded that the total inventory reset with everyone losing everything that wasn't rezzed in-world was the beginning of the end of the once-mighty Metropolis Metaversum. Apparently, the OSgrid admins all pack lightly, and they seem not to be able to estimate how much the still active avatars would lose and have to save or reconstruct.
Sure, it's possible to save your entire OSgrid inventory as an IAR. But that's only possible if you have land, if you have at least one sim attached to OSgrid. So this could also have been seen as a ploy to get those who don't have land yet to host and attach sims so that OSgrid can outgrow the again and reclaim its spot as the biggest grid on the Hypergrid. I mean, it's commonly known that OSgrid doesn't take Lbsa Plaza not being the top spot on either. Besides, many simply don't have what it takes to host your own sim, not even temporarily.
And so Dan Banner, one of the admins, changed the asset reset announcement. The OSgrid team had understood how bad an idea it actually is to purge all assets that aren't rezzed in-world and delete everything from everyone's inventories, actually including payware from commercial grids. It would drive people away from OSgrid even faster than the current situation which mostly has them create backup avatars elsewhere.
It would not only drive them away from OSgrid, but over to commercial competitors like or Wolf Territories which not only aren't younger than OSgrid, but which have their own powerful asset servers and actually take good care of them. Especially the Wolf Territories Grid comes with the advantage of being only three years old and never having been used as a gateway for mass-importing tons of copybotted content. Also, these commercial grids have stable sources of income in the shape of land rentals. OSgrid doesn't have land rentals at all all sims that aren't official are hosted by their users and attached for free. So OSgrid only makes money from donations and an annual in-world auction.
And indeed, has that 87 sims were just recently moved to Wolf Territories via OAR export and import. This greatly reeks of a beginning OSgrid exodus.
This must have caused a change of mind among the OSgrid admins. They still consider a reset, but now they want to try to restore the assets in people's inventories afterwards. That's all we know now.
Asset Reset - OSgrid News
#
Long #
LongPost #
CWLong #
CWLongPost #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
OSgrid #
Kitely #
WolfTerritories #
WolfGrid #
WolfTerritoriesGrid