DSC9445 by samjstone

Discord has completely warped the term "server" for entire generations of Internet users. On Discord, "server" means "chatroom".
In the Fediverse, "server" doesn't mean "chatroom". It means "". A computer.
For example, .
Or or running at someone's home, connected to their landline.
On each one of these, a big or small Twitter can be running (Mastodon).
Or a wholly different Twitter (Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, Catodon, Meisskey, Tanukey, Neko...).
(Here's the first important new thing for you to learn about the Fediverse: The Fediverse is not only Mastodon.)
Or a Facebook with a side of a blog and a cloud server (Friendica, (streams), Forte).
(Here's the second important new thing for you to learn about the Fediverse: The Fediverse is not only short-form microblogging. Look at this comment. Look at what I've done. Embedded links. Bold type. Impossible on Mastodon. But possible elsewhere in the Fediverse.)
Or a Facebook meets WordPress meets Google Cloud Services meets even more stuff on top (Hubzilla this is where I am).
Or an Instagram (Pixelfed).
Or a YouTube (PeerTube).
Or a Twitch (Owncast).
Or a Reddit (Lemmy, /kbin, Mbin, PieFed).
Or a Goodreads (BookWyrm).
Or whatever. There are over 150 different server applications in the Fediverse.
mastodon.social, where you are, is only one of over 10,000 big and small Twitters of the same kind (Mastodon).
If Mastodon was like Discord, all 10,000+ Mastodon servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc.
If the Fediverse was like Discord, all 30,000+ Fediverse servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc. Also, they would be fully identical in functionality.
But as I've said above: They're all running on their own separate machines. With their own separate owners.
And the different server applications have different developers, and they are being developed independently from one another.
Okay, now comes the kicker: These server applications are not walled up against one another. Not only are all instances of the same server applications (e.g. Mastodon) connected to each other, but all instances of one server application are also connected to all instances of all the other server applications.
Imagine you're on Twitter. But your new friend is on Facebook. You can't follow a Facebook user on Twitter, and you can't follow a Twitter user on Facebook.
In the Fediverse, you can. You can be on Twitter. And follow a Facebook user. Directly from Twitter. Without a Facebook account.
Only that they aren't named Twitter and Facebook in the Fediverse. Twitter is named Mastodon or Pleroma or Akkoma or Misskey or Calckey or Firefish or Iceshrimp or Sharkey or Catodon or... There are dozens of Twitter alternatives in the Fediverse. Well, and Facebook is named Friendica or Hubzilla or (streams) or Forte.
You can be on Mastodon. And you can follow Friendica accounts. From Mastodon. Without a Friendica account.
This comment is a very good example. You are on , created by in 2016 as an alternative to Twitter that aimed to be as close to Twitter as possible.
The server that you're on, , is owned by Mastodon, Inc. and running on one or multiple rack servers in San Francisco, California, USA owned by .
I am on , created by Mike Macgirvin in 2012 by forking his own from 2010, and currently mainly maintained by Mario Vavti and Harald Eilertsen. Hubzilla has got nothing to do with Mastodon whatsoever. It started out as an alternative to Facebook, but not a clone, rather better than Facebook, with full-blown long-form blogging capability and a built-in file storage, and it has been enhanced greatly in functionality even beyond that.
The server that I'm on, , is owned and administered by Mark Nowiasz, who has no affiliation with the Hubzilla developers, and running on a rack server in Nuremberg, Germany owned by .
And yet, you can see this comment coming from Hubzilla on Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Server #Instance #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Sharkey #Catodon #Meisskey #Tanukey #Neko #Friendica #Hubzilla #Streams #(streams) #Forte #Pixelfed #PeerTube #Owncast #Lemmy #/kbin #Mbin #PieFed #BookWyrm #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse

Please make it descriptive: tell us about colours, what the person looks like, the background, and anything else you can think of.

I've got a few examples of image posts of my own with very detailed image descriptions. These posts are not on Mastodon, but they are very much in the Fediverse in places that are federated with Mastodon, and they all have actually ended up on Mastodon timelines. So I guess Mastodon's accessibility requirements apply to these places just as well.
Would you say they're too descriptive Or would you even say they aren't descriptive enough yet, and that there are important details missing
One example is (content warning: eye contact) with two images, my most recent one. It is not available on mastodon.online. These images also show a digital avatar, so in a sense, I've described a person.

• The first image has exactly 1,500 characters of alt-text, 990 are short image description, 509 explain where the long description can be found.
• The second image has 1,499 characters of alt-text, 989 are short image description, 509 explain where the long description can be found.
• The long descriptions have almost 11,000 characters in the common preamble, over 2,800 characters specifically for the first image and almost 6,600 characters specifically for the second image because it has more surroundings. All in all, the long descriptions have almost 21,000 characters. It took me eight hours to research for and write them. The visual description of the avatar plus necessary explanations alone takes up almost 7,000 characters.

Another example is with one image. You can also find it by searching for the hashtag #UniversalCampus and scrolling to the bottom of the results there you can see what it looks like on Mastodon.

• The alt-text is exactly 1,500 characters long, 1,402 of which are the short image description. The note where to find the long description had to be shortened to the point of being half-useless.
• The long description in the post is over 60,000 characters long. It took me two full days, morning to evening, to research for and write it.
• I've actually had to limit myself in comparison to earlier image descriptions: There are no longer any detailed descriptions of images within the image, especially not at a higher level of detail than what the images within the image themselves show in-world.
• This description is outdated because I've used absolute measures rather than measures relative to what people are familiar with, and the descriptions of the colours may not be detailed enough.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility

What are the differences between Diaspora, Pleroma, Hubzilla, Hometown, and Glitch How do they compare to Friendica as far as features

As for Hubzilla vs Friendica, I've made a series of tables that compare Mastodon, Friendica, Hubzilla and (streams). I've made them for those who are looking for a Facebook alternative in the Fediverse, but who only know Mastodon first-hand and Friendica from hearsay. But these tables are useless for blind or visually-impaired users, and I can't change that because it's in the nature of tables. Also, I don't have all data for Friendica yet. (In case someone sighted comes across this comment and wants to see the tables: ).
So I'll try to do a Hubzilla vs Friendica comparison here. Hold on and take some time, for this will be very, very, very long. 42 lines of comparison with over 10,000 characters.
Friendica was created by Mike Macgirvin in 2010.
Hubzilla started out as a Friendica fork by Mike Macgirvin himself in 2012, originally named Red (from spanish la red = the network), then renamed Red Matrix. It was repositioned, reworked, massively extended beyond Friendica's features and renamed Hubzilla in 2015.
Friendica has native Android apps, a closed beta native iOS app and support for Mastodon apps, even though Mastodon apps only cover 20% of Friendica's features at most. Hubzilla doesn't have any mobile apps, at least none for iOS, none in the Google Play Store, none that could be installed on a new Android device and none with a fully native mobile user interface.
Hubzilla also also doesn't support Mastodon apps and never will. That's mainly because a Mastodon app can't cover over 90% of Hubzilla's features, including features which you need all the time such as file upload, image embedding, handling of connections and permission controls, simply because Mastodon doesn't have these features. Hubzilla would require its very own apps, and due to Hubzilla's immense complexity and wealth of features, a fully-featured, dedicated Hubzilla app would be absolutely gargantuan and just as complex as Hubzilla itself.
On Friendica, ActivityPub federation is available from the get-go. On Hubzilla, ActivityPub federation is optional, and on newly-created channels, it is off by default.
Friendica can integrate Bluesky and Tumblr accounts. Hubzilla can't.
On Friendica, your account is your identity. Your identity is firmly tied to your account. On hubzilla, your identity is independent from your account. It resides in a container called a "channel", of which you can have multiple, fully independent ones on the same account. This also allows you to switch back and forth between channels or identities without logging out and back in.
Friendica has limited capabilities of moving your identity to another instance. Hubzilla has nomadic identity. For one, this makes it possible to relocate an entire channel with all posts, all comments, all private messages, all connections, nearly all settings, all files in your file space etc. etc. to another instance. Besides, it makes it possible to clone a channel to one or multiple other instances. This gives you live, hot, real-time, bidirectional backups of your channel, and you can log into and use any of them. That way, your channel is much more resilient against instance shutdown.
If you delete a Hubzilla channel, you cannot create a channel with the same short name on the same Hubzilla hub unless the admin fully deletes your channel from the database.
If you delete a clone of a Hubzilla channel, you cannot clone the same channel back to the same hub unless the admin fully deletes your channel from the database.
Friendica has client-side support for OpenWebAuth magic single sign-on. Hubzilla has full support. This means that Friendica logins are recognised by instances with full OpenWebAuth support, but Friendica itself doesn't recognise logins elsewhere. Hubzilla logins are recognised the same, and Hubzilla does recognise logins elsewhere.
Friendica has some basic permission control. On Hubzilla, it is much more advanced and fine-grained.
On Friendica, you can set your profile to private. On Hubzilla, you can give permission to see your profile to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your list of connections to private. On Hubzilla, you can give permission to see your connections to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your timeline to private as far as I know, this happens along with setting your profile to private. On Hubzilla, you can give permission to see your stream to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
I don't know if Friendica can give specific permissions to specific connections. Hubzilla has so-called "contact roles". Each contact has a contact role that grants or denies 17 different permissions. Permissions granted channel-wide from the channel role are inherited by all contact roles. Two of these permissions are for your contacts to send you their posts and for your contacts to send you private messages.
On Hubzilla, you can keep both everyone and specific contacts from sending you repeats/boosts/reposts/renotes with a line of filter syntax in a filter blacklist.
On Hubzilla, you can send any of your posts as public, only to yourself, to all members of a privacy group (which is similar to a circle on Friendica), to whoever is assigned a certain non-default profile, to one specific group/forum or to a custom selection of contacts. You can also define your default post audience, either one of your privacy groups, or your posts are public by default.
Hubzilla has three levels of reply control. At channel level, you can give permission to reply to your posts to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself. In addition, you can choose to let comments in from those who are not permitted to comment on your posts, preview them and then manually decide whether or not you accept each comment.
Reply control at per-contact level means that you can use contact roles to grant or deny permission to reply to your comments to certain connections.
Reply control at per-post level is optional and off by default. It lets you disallow comments on individual posts of yours entirely.
Likewise, there is quote-post control at channel level and at per-contact level.
On Friendica, you can report posts to the admin. On Hubzilla, you can't. This feature is currently being discussed.
I don't know about Friendica, but Hubzilla has a channel-wide filter with a whitelist and a blacklist, and optionally, it has an individual filter for each connection with a whitelist and a blacklist.
Hubzilla allows regular expressions in filter lines, but only for normal keywords, not in lines with filter syntax.
Hubzilla's filter syntax can recognise posts, comments and private messages. This is of very limited usefulness, however: If you want to whitelist certain keywords for posts, but let all comments and all private messages through, you'd have to use filter syntax in a whitelist. But in whitelists, keyword lines are connected with "or" whereas filter syntax lines are connected with "and" which means that you cannot combine keywords with filter syntax. There is also filter syntax for keywords, but these lines are connected with "and" in whitelists, too, and each line can only contain one keyword with no regular expression.
On Friendica, summaries or Mastodon-style content warnings are created with a pair of BBcode tags, either abstract/abstract or abstract=apub/abstract. This works for posts, comments and private messages. Hubzilla has a dedicated summary field for posts, but none for comments. In theory, it also has the BBcode tag pair summary/summary, but in practice, it is broken.
Friendica optionally offers Markdown for text formatting in addition to BBcode. Hubzilla only offers BBcode.
Friendica doesn't have or support polls. Hubzilla has full support for basically unlimited polls.
Friendica calls reposting "sharing" and quote-posting "quoted sharing". Hubzilla calls reposting "repeating" and quote-posting "sharing".
On Hubzilla, you can optionally be notified when a stranger mentions you out of the blue outside any conversation on your stream.
On Friendica, you can make a group restricted or private. On Hubzilla, you can give a group or a forum privacy, too, but by choosing the "Custom" channel role instead of the "Community forum" channel role, and you have to adjust the level of privacy by hand. The advantage is that you have fine-grained control over what exactly you want to be private in your group or forum.
Private Friendica groups can be joined by users on Friendica, Hubzilla, (streams) and probably also Forte. Private Hubzilla groups or forums can only be joined by users on Hubzilla, (streams) and maybe Forte.
Friendica has a central directory of users, groups etc., the . Hubzilla doesn't have such a thing.
Friendica nodes have their own directories I'm not sure if they only list Friendica accounts or accounts and channels of everything that uses ActivityPub, or if they even include diaspora* users. Hubzilla hubs have such directories, too, but they only list Hubzilla and (streams) channels because they can only list what uses the built-in and permanently activated Nomad protocol.
In your Hubzilla directory, you can hide channels that are flagged not safe for work.
Hubzilla has an option that gives those who are permitted to see a post the permission to also see any media embedded in the post, regardless of the permissions set for the respective media in your file space. This was introduced due to the wide-spread issue of people uploading images and setting them or the directores the images are in to private, then embedding them into public posts and the audience of the posts not seeing the images.
On Hubzilla, you can give guest access tokens to people whom you want to access certain files or directories in your file space.
The file space built into your Hubzilla channel can be accessed via WebDAV.
Hubzilla also has a built-in CalDAV calendar server which can use the event calendar as a simple frontend and an optional headless CardDAV addressbook server.
Hubzilla optionally has "articles", long-form text posts with the same full text formatting capabilities as normal posts, but which don't federate.
Hubzilla optionally has "cards", basically planning cards with the same features as articles plus a few extra features.
Hubzilla optionally has multiple wikis per channel with multiple pages per wiki. Wikis can be set up to use either BBcode or Markdown as their markup language with a few wiki-specific additions in both cases.
Hubzilla optionally has simple, static webpages which can be formatted with either BBcode, Markdown or plain HTML. Hubzilla's own official website is a webpage on a Hubzilla channel.
I think that's about it.
As for diaspora*: Forget it. For one, it does not support ActivityPub, and it does not federate with most of the Fediverse. The diaspora* developers staunchly refuse to add any other protocols to diaspora*, especially ActivityPub. One has actually said that you don't implement ActivityPub, you implement Mastodon. And the diaspora* developers don't want to make themselves dependent on Mastodon.
Besides, diaspora* is withering away. Around December 29th, a number of major diaspora* pods shut down. According to one source, diaspora* lost over half its user accounts in three days. And the closure of diasp.org, one of the biggest pods, is scheduled for April 1st now.
Quote:

Are there any other networks I should know about

End quote.
From the same creator as Friendica and Hubzilla, there is something he created in 2021 at the end of a long and somewhat complex line of forks. It is officially and intentionally nameless, brandless, not a project and released into the public domain. Colloquially, it is named (streams) in parentheses after the name of its code repository. You can find the latter with an extensive readme . It is slimmed down in features from Hubzilla, and it doesn't offer nearly the connection and federation options of Friendica and Hubzilla. But it is easier to handle while still having a steeper learning curve than Friendica, and especially its permission system is both another bit powerful and significantly easier to use than Hubzilla's.
(streams) has no mobile apps and no compatibility with Mastodon apps either for the same reasons as why Hubzilla doesn't isn't compatible with Mastodon apps.
(streams) is included in my comparison tables, too. If you want me, I can rattle down another comparison with Friendica like the one with Hubzilla above.
In August, 2024, Mike made another fork based on (streams) named Forte. It's basically (streams), but with a name, with a brand identity, as a project, released under the MIT license and with no support for the Nomad protocol anymore. It does everything using only ActivityPub. This also means that it relies entirely on ActivityPub for nomadic identity. Since especially this is still highly experimental, Forte itself has not officially been released yet, it is not recommended as a reliable daily driver, nor does it have public, open-registration instances.
Quote:

Finally, will the interface of the page on Friendica change depending on my instance

End quote.
As far as I know, different Friendica nodes have different default themes, especially now that the Facebook-like Bookface theme may be officially included into Friendica.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #diaspora* #Friendica #Hubzilla #Streams #(streams) #Forte Not quite, and that says someone who .
Hubzilla wikis don't federate. In any way. They always stay within the Hubzilla channel which they belong to.
Not only that, but I, as the owner of this Hubzilla channel, have to manually permit other people to edit my wikis. And these have to be on something that supports client-side OpenWebAuth: Friendica, Hubzilla, (streams), Forte. And they have to be connected to my channel (in Mastodonese, that's "follow me, and I have to follow them back", but connections on Hubzilla are bidirectional by default) so I can give them permission to edit my wikis.
I've read about a federated wiki engine with ActivityPub in the making, but the name eludes me.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Wiki If you mean "groups" as in "Facebook groups", then you can't create them from your account. They aren't a separate functionality like on Facebook.
On Friendica, groups are accounts like user accounts, only with different settings. So if you want to create a group, you have to register a new account. I recommend you to do that on another Friendica node so you can be logged into both your personal account and your group account simultaneously, just in case you have to do something in your group.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Groups

as i said yesterday the facebook bridge is also broken

There is no Facebook bridge.
I guess you must have heard from someone on Mastodon who has heard from someone on Mastodon etc. something about Friendica and Facebook being connected. Chinese whispers, Fediverse-style. But that's only a tiny chunk of the true story.
There was a Facebook connector. And it wasn't a bridge. It was fully natively integrated into Friendica, just like Bluesky and Tumblr are fully natively integrated into Friendica today. But they require a Bluesky or Tumblr account, and the Facebook integration required a Facebook account. (Source: I've actually used it back in the day.)
Also, Facebook disallowed third-party apps to extract content from Facebook in 2012. And in 2013, Facebook made extracting data impossible, thus ending the functionality of the Facebook integration add-on.
Facebook integration on Friendica has been gone for three years longer than Mastodon has been around.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #Friendica

Don't hesitate to ask if you're unsure of something, but never think that we don't notice your effort.

I do have a few questions, specifically because my image posts have gone unnoticed by blind or visually-impaired users so far.
Judging and assuming from the information I've gathered so far, my original images require very extensive and detailed descriptions. A full description is too long for alt-text, so what I do is write a full description with all text transcripts and all necessary explanations, put it into the post text body and then condense a shorter, but still long alt-text from it. What's your stance on this method of describing the same image twice over
Also, where would you personally prefer a long description In the post itself Or in an external document that's linked into the post If you're on a phone app, remember that the external document will inevitably open your Web browser.
Do you prefer images described, based on what a sighted person can see in the image as it is posted Or do you prefer a description that is not limited by the restriction of the image itself, for example, assuming an infinite image resolution and an infinite zoom factor that would let sighted people theoretically see even tiniest details
If I mention something in my image description of which you don't know what it looks like, do you need a detailed visual description
Concerning text transcripts: Let's assume a bit of text in an image is too small to be legible for sighted people, but I can read it at the original source, so I can transcribe it nonetheless. Shall I transcribe it What about if said text is too small to be recognisable as text or so tiny that's it's practically invisible I mean, after all, the concept of image resolution should not matter to totally blind people, so writing that a piece of text can't be read because the resolution of the image is too low ought to sound like a lame excuse for skimping a transcript.
If there's a building in one of my images, I can safely assume that you don't know what that one specific building looks like, so I guess I can also assume that you need it described. If I could, I would do so using architectural terms and then explaining all these architectural terms right after using them. Would you say that's the correct way Because that's why I avoid having realistic buildings in my images.
If there's an image in my image, do you need it described At a level that I can source right where the image is without moving away too far, or at a level that I can only source by moving farther away to the place shown in the image What about an image in an image in my image (I'm serious. I've actually described images within images within my image, but I've stopped when this was about to go out of hand due to there being too many to describe.)
I'm currently working on a series of posts with images showing a virtual-world avatar in various but similar outfits in fact, I have been since last year. I may have questions later regarding at what level of detail I have to describe that avatar.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

DSC9445 by samjstone

I often spend more time writing alt text than the text in the toot itself - not just to keep the toot itself as short as possible.

I always spend more time describing my images than writing the post that they go into.
For my meme posts, that's because I have to explain the picture and find the appropriate links to external explanations (KnowYourMeme etc.) to shorten my explanation block if possible.
For my original images, it's because I have to describe them twice. There's always an alt-text which, as of late, fills the 1,500-character limit imposed by Mastodon, Misskey etc. to the brim. But that alt-text is only a shortened and slightly adapted version of an extremely long long description which goes into the post text body and which also includes transcripts of any and all text in the image, readable or not, as well as all explanations which I deem necessary for outsiders to understand the image. Since the images are about an extremely obscure niche topic, this means I have to explain a lot.
A while ago, I spent two full days, morning to evening, researching for and describing and explaining one single image. The result was . And I actually had to limit myself, otherwise the description would have been even vastly longer and taken over a month to complete. Good thing I don't have any character limit to worry about. The only exception is that Mastodon may reject posts from outside with over 100,000 characters.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Unless you need a Facebook replacement, unless you plan to use Friendica or Hubzilla or (streams) or Forte, only the first three paragraphs are of interest for you.
Basically, all Fediverse instances are separate websites. If you want to use one of them like you use pdx.social, you need an account on that instance. Your account on pdx.social won't do. It doesn't matter if that instance is a Pixelfed instance or a Loops instance or a PeerTube instance or a Misskey instance or an Akkoma instance or whatever.
So, no, with your Mastodon login, you can't just simply use Pixelfed or Loops or PeerTube. If you want to use Pixelfed (= post pictures), you need an account on a Pixelfed instance. If you want to use Loops (= upload videos), you need an account on the currently only Loops instance. If you want to use PeerTube (= upload videos), you need an account on a PeerTube instance.
Got that so far
But, and this is something that even many Twitter refugees from 2022 haven't understood yet: Mastodon and Pixelfed and Loops and PeerTube and Misskey and Sharkey and Akkoma and Friendica etc. etc. aren't walled off from one another.
You can be on Mastodon, but you can follow Pixelfed accounts from Mastodon. And you can follow Loops accounts from Mastodon. And you can follow PeerTube channels from Mastodon. And so forth. Just like you can follow accounts on other Mastodon instances from your Mastodon account on pdx.social. Just like you already do.
By the way: Right now, you do not only follow Mastodon accounts. I've looked through those you follow. There's one Neil E. Hodges (tkf.kawa-kun.com). Scroll down the list of those whom you follow. When you find him, look at his profile. Okay, now look at his profile at its source. Safari (or whatever is your default Web browser) will open. And you'll see .
This is not a Mastodon account on a Mastodon instance with a weird UI. This is an account on . A Facebook alternative from 2010 which is not Mastodon, which has never been Mastodon, which is developed completely independently from Mastodon, which is very different from Mastodon, and which is over five years older than Mastodon.
But: Just like Mastodon, Friendica is part of the Fediverse. And it has been federated with Mastodon since Mastodon was created. This means: Since Mastodon was created, it has been possible for Mastodon users to follow Friendica accounts from their Mastodon accounts. And vice versa, it has been possible for Friendica users to follow Mastodon accounts from their Friendica accounts.
You yourself are right now following someone who is on something that is not Mastodon. Very much not Mastodon, in fact.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #PeerTube #Friendica #Federation Pixelfed is wholly separate software from Mastodon on wholly separate servers with wholly separate owners. So yes, you need a separate Pixelfed account. It's a bit easier on Pixelfed if you're already on Mastodon: Pixelfed lets you automatically create a new user account by "logging in" with your Mastodon login credentials. But only Pixelfed has this as far as I know.
Loops is wholly separate again, but there's only one instance so far because it's too unfinished to even be open-source. So you'll need a Loops account next to your Mastodon account and your Pixelfed account.
Also, you'll have different followers on Mastodon, on Pixelfed and on Loops. But what you could do if you want your followers on Mastodon to see your Pixelfed posts is: Follow your own Pixelfed account from Mastodon. And then, whenever you post something interesting on Pixelfed, wait for it to arrive on your Mastodon timeline, and then boost it.
There's one thing that exists already now: OpenWebAuth magic single sign-on. But it's only available on Hubzilla, (streams) and Forte and partially on Friendica.
What it does is recognise your login on another instance, even on an instance of another server application. Hubzilla, (streams) and Forte recognise logins from Friendica, Hubzilla, (streams) and Forte, but Friendica can't recognise logins.
However, this is only used by the permissions system. For example, someone whom I'm connected to could have made their profile only visible to a certain subset of their connections, including myself. If you visit their profile, you won't see anything. If I visit their profile, their home instance recognises my Hubzilla login, and I can see the profile.
What it does not do is give you the same full-blown rights as a user with a local account. I can't just, like, go to some (streams) instance and post away as, what, jupiterrowlandrumbly.net or go to a Hubzilla hub where I don't have an account and create a webpage or a wiki or a CalDAV calendar right away without logging in. That's not how it works.
By the way, client-side OpenWebAuth support (= your login is recognised on Hubzilla, (streams) and Forte) was proposed and actually developed to the point of a pull request for Mastodon. As far as I know, it was rejected. OpenWebAuth won't come to Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #Friendica #Hubzilla #Streams #(streams) #Forte #OpenWebAuth #SingleSignOn Tatschlich ist meines Erachtens dichter an Friendica dran als , weil nicht so berladen. Das kennt blo auerhalb von Hubzilla und (streams) selbst praktisch keine Sau. Da habe ich auch zwei Kanle.
Friendica wrde ich nur empfehlen, wenn jemand unbedingt, unbedingt eine Android-App braucht. Oder willens ist, eine iOS-App mit einem Riesenaufwand ber TestFlight zu installieren. Vielleicht noch, wenn jemand mit (streams) nicht klarkommt (wobei auch Friendica nicht unbedingt "registrieren und loslegen" ist).
Hubzilla, da bin ich jetzt hier gerade selber, ist schon ziemlich hardcore von der Lernkurve her und braucht zwingend einiges an Einstellungen, bevor man loslegen kann. App kann man auch vergessen, aber ich schaudere beim Gedanken einer Fully-featured-Hubzilla-App mit komplett nativem Mobilinterface.
Wenn Forte offiziell freigegeben wird, werden die Karten vielleicht neu gemischt. Aber in der Bedienung wird es sich nicht groartig von (streams) unterscheiden. Der einzige Unterschied ist, da Forte das Nomad-Protokoll nicht mehr hat, sondern nur noch ActivityPub.
Fr die, die es noch nicht wissen: Das ist alles eine Software-Familie, die derselbe Entwickler seit beinahe 15 Jahren in Entwicklung hat. Und zwischen Hubzilla und (streams) gab es noch ein Geflecht aus mindestens sieben weiteren Forks, die alle eingestellt sind.
Ich habe brigens krzlich einen tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) gemacht, falls es jemanden interessiert.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookErsatz #Friendica #Hubzilla #Streams #(streams) Auf Mastodon gar nicht. Mastodon hat fr Gruppen keinerlei Untersttzung und wei gar nicht, was Gruppen sind.
Hier sind ein paar Sachen, wo du nach Gruppen suchen knntest, mit denen du dich trotzdem von Mastodon aus verbinden kannst:
listet aktuell ber 220 ffentliche Friendica-Gruppen. (Falls nicht bekannt: Friendica ist eine Facebook-Alternative im Fediverse.)
listet aktuell fast 28.000 Lemmy-Communities. (Falls nicht bekannt: Lemmy ist ein Reddit-Klon im Fediverse.)
Es gibt noch einiges mehr, was Gruppen hat, aber dafr jeweils keine umfassende ffentlich erreichbare Suche.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Lemmy #Gruppeninbal Dror 2021 collection.

Richtig.
Das ist genau wie 2022/2023. Da wurde doch die groe Masse der Mastodon-Nutzer direkt nach mastodon.social geholt, ohne da ihnen erklrt wurde, was Mastodon ist (auer dem blichen "literarisch Twitter ohne Musk") oder gar das Fediverse. Die haben teilweise Monate gebraucht, um berhaupt nur zu merken, da Mastodon keine einzelne monolithische Silo-Website ist.
Heute gibt's genau das immer noch. Zustzlich wird den Leuten erklrt:

• Pixelfed = literarisch Instagram ohne Zuckerberg = pixelfed.social
• Loops = literarisch TikTok, aber in Amiland erreichbar ohne Musk was auch immer = loops.video (gerechtfertigt, da wird's bis auf weiteres nur die eine Instanz geben)
• Friendica = literarisch Facebook ohne Zuckerberg = friendica.world (auch weil die meisten Amis keinen anderen englischsprachigen Node kennen, weil die anderen groen Nodes alle deutsch sind)

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pixelfed #Loops #Friendica You can't connect Fediverse accounts like that and make them one, at least not generally all over the place, and especially not between Mastodon and Hubzilla. These two will always be fully separate logins.
The best you can do is follow your Hubzilla account from Mastodon, then confirm the connection request on Hubzilla which, from Mastodon's point of view, creates a mutual follower/followed connection.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla babenextdur IG



Since you're already offering multiple options to switch to, here are some more proposals:
Facebook -> ()
Facebook -> ()
-> ()
-> ()
Threads -> ()
Threads -> ()
Reddit -> ()
Reddit -> ()
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Meta #MetaPlatforms #Facebook #Streams #(streams) #Hubzilla #Twitter # #Threads #Misskey #Iceshrimp #Reddit #Mbin #PieFed #GlobalSwitchDay

New entry of AI-generated and added to our :

's

From a purely technical point of view, he'll only need a Pixelfed account. You can follow Pixelfed accounts from just about everywhere in the Fediverse.
A better question would be if he'll get the reach he wants with only a Pixelfed account. One could argue that he'd be better off with a Mastodon account on top to advertise for his Pixelfed posts by boosting them. But one could also argue that this may lead to people following his Mastodon account rather than his Pixelfed account. And that it'd amount to cheating.
His advantage, however, would be that he wouldn't start out all alone in the Fediverse. I think I can expect you to follow him. You are already on Mastodon, you already have a substantial amount of followers, so I guess he could leave the "plugging" to you.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed

the only 3 posts on Pixelfed

Do you mean posts from people whom you follow on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
Do you mean your own posts which you've posted on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
There is only one way to connect a Mastodon account and a Pixelfed account: You can follow your own Pixelfed account with your Mastodon account. This doesn't make one account out of two accounts. You only become your own follower. Just like you can follow anyone else's Pixelfed accounts from Mastodon. Or just like anyone else on Mastodon can follow your Pixelfed account.
When you do so, and you post something on Pixelfed (you have to log into Pixelfed for this), you receive these posts on Mastodon. The purpose of this is e.g. to boost your Pixelfed posts to your Mastodon followers so they can see them without also having to follow your Pixelfed account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed The Fediverse is a bunch of different, independent applications which nonetheless are connected in such a way that users of one application can follow users of another application. But they're still separate instances of different, independent applications.
If you're on Mastodon, and you want to follow a PeerTube channel and comment on the videos from that PeerTube channel, you can simply follow that PeerTube channel from Mastodon. You don't need a PeerTube account.
If you're on Mastodon, and you want to upload videos to PeerTube, then you need a PeerTube account.
What Pixelfed does, namely automagically create a Pixelfed user account for everyone who "signs in" with their Mastodon credentials, is an exception, but it misleads Fediverse newbies into thinking that they've got full user power on all instances of all Fediverse server applications with their Mastodon login.

Should we all be having the same handle with different instances (each instance a different UX/app) or... nah

You can. If you want to. Advantage: People can be fairly sure that it's the same you as the Mastodon you.
But you don't necessarily have to. Not if e.g. you want to represent an entirely different persona on, say, Misskey than your normal, standard public self on Mastodon.
I mean, you can also have multiple accounts on Mastodon (or anything else) under different names, with different identities, with different personas or even for different purposes. For example, if you love posting about topic A and topic B, you make an account for topic A and one for topic B with different names. That way, the people who follow you for topic A don't have their timelines cluttered with your topic B stuff that's uninteresting to them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #FediTips Find the latitdue and longitude of any place (streams) ist Hubzilla

• minus alle Protokolle auer Nomad (beide Versionen) und ActivityPub
• mit ActivityPub im Kern und standardmig an
• minus RSS/Atom-Aggregator
• minus Artikel
• minus Karten
• minus Wikis
• minus Webpages
• mit nur einem Profil pro Kanal
• mit Verifizieren externer Identitten (wie z. B. auch bei Mastodon und WriteFreely)
• mit einfacherer Berechtigungssteuerung und vier kanalweiten Berechtigungslevels weniger als Hubzilla
• mit Kanaltypen, die nur noch ganz wenige Berechtigungen steuern und nicht mehr alle kanalweiten Berechtigungen wie Hubzillas Kanalrollen
• ohne Custom-Kanalrolle, weil unntig
• mit vier Kanaltypen fr Gruppen/Foren
• mit der Mglichkeit in Gruppen/Foren, Posts und Kommentare von Neulingen durch Admins freizuschalten
• mit einzeln pro Verbindung schaltbaren Berechtigungen Berechtigungsrollen (Hubzilla: Kontaktrollen) sind nur noch Presets zur Bequemlichkeit und nicht mehr die einzige Mglichkeit, Verbindungen Berechtigungen zu erteilen
• mit der (optionalen) Mglichkeit, da nur deine eigenen Verbindungen auf einen bestimmten Post antworten drfen und/oder nur bis zu einem bestimmten Datum auf einen bestimmten Post geantwortet werden darf
• mit der Mglichkeit fr Nutzer, ganze Instanzen zu blockieren
• mit der Mglichkeit fr Admins, ganzen User Agents und damit auch ganze Fediverse-Projekte instanzweit zu blockieren
• mit Textformatierung in Posts per nicht nur BBcode, sondern auch Markdown und HTML
• mit Tags fr Zusammenfassungen/Mastodon-CWs statt einem Eingabefeld
• mit der Option, auch ganze Threads auf den eigenen Stream zu holen, in denen ein eigener Kontakt geantwortet hat
• mit ActivityPub-Konten und -Gruppen im Verzeichnis und nicht nur Nomad-Kanlen

Einen kompletten tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) habe ich gemacht.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams)

With all the servers, it's a bit confusing. For instance, I don't know which one I can connect to peerfed for uploading videos or share videos from other source that I find interesting.

There's a difference between following someone on something that isn't Mastodon and using something that isn't Mastodon.
You can follow a PeerTube channel on Mastodon and see their new videos on Mastodon. But you cannot upload videos to PeerTube from Mastodon yourself. For that, you do need an account on a PeerTube instance.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #PeerTube Hast du jemals Friendica oder Hubzilla genutzt
Und ich meine wirklich genutzt Nicht kurz reingeschnuppert, nicht verstanden, fr doof befunden, weil es sich nicht wie Mastodon bedient, und dann einen toten Account/Kanal zurckgelassen Ich meine, hast du jemals Friendica oder Hubzilla ber Monate oder gar mehrere Jahre intensiv als deinen primren Daily Driver genutzt
Hinter PepeCyBs Welt steckt Der Pepe (Hubzilla) . Der ist schon lnger im Fediverse, als es Mastodon gibt, und schon seit frhester Zeit auf Hubzilla. Auch ich bin schon sehr frh nach Hubzilla gekommen. Wir beide nutzen Hubzilla als Daily Driver. Und wir beide nutzen Hubzilla nicht wie Mastodon als Twitter-Ersatz, sondern wir reizen es aus als das, was es ist. Auerdem haben wir beide Erfahrungen mit Friendica, und wir haben beide aktive (streams)-Kanle.
Probier mal Friendica oder Hubzilla aus. Und zwar ernsthaft. ber mindestens ein halbes Jahr als primren Daily Driver. Und nicht durch die Mastodon-Brille. Dann wirst du sehen, inwiefern beide sehr viel eher soziale Netzwerke sind als Mastodon.

Der einzige Unterschied zwischen Mastodon und Hubzilla ist, dass Mastodon ein Mikrobloggingdienst und Friendica / Hubzilla Makrobloggingdienste sind, die gemeinsam im Fediversum verbunden sind.

Das ist der eigentliche Unsinn.
Und sind die Unterschiede zwischen Mastodon einerseits und Friendica, Hubzilla und (streams) andererseits.

• Hat Mastodon bzw. Gruppen Nein, Mastodon wei gar nicht, was eine Gruppe ist, und kann mit Gruppen nichts anfangen. Friendica, Hubzilla und (streams) haben dagegen sowohl ffentliche als auch private Gruppen. Mit Moderation. Nativ eingebaut. Schon immer.
• Kann Mastodon einem eine ganze Liste von potentiellen Kontakten vorschlagen anhand dessen, was man selbst im Profil hat Und zwar sortiert danach, wer entweder am ehesten zu dir pat oder mit dir die meisten gemeinsamen Kontakte hat Nein, kann es nicht. Friendica kann es, Hubzilla kann es, (streams) kann es.
• Hat Mastodon standardmig bidirektionale Verbindungen wie Facebook oder StudiVZ oder Wer-kennt-wen usw., also alles, was sich je klassischerweise "soziales Netzwerk" nannte und nennt Nein, es hat nur Folgebeziehungen wie Twitter. Und "gegenseitig" heit zwei voneinander unabhngige Folgebeziehungen. Friendica, Hubzilla und (streams) hatten dagegen schon immer die bidirektionale Verbindung als Standard.
• Versteht Mastodon Konversationen Jetzt wirst du natrlich sagen: "Ja, natrlich!" Aber benutz mal Friendica oder Hubzilla oder (streams). Dann wirst du Konversationen erst richtig kennenlernen. Und dann wirst du sehen, da Mastodon einen Schei versteht.

Ganz zu schweigen von vielen anderen Sachen, die vor allem Hubzilla und (streams) haben, die Mastodon nicht hat. Hochdetaillierte Berechtigungverwaltung auf drei Ebenen, Selbstmoderation der eigenen Konversationen, Antwortenkontrolle, nomadische Identitt, mehrere separate Identitten auf demselben Konto... Und von dem, was Hubzilla exklusiv hat (Artikel, Karten, Wikis, Webpages...), habe ich noch gar nicht angefangen.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams)

da hatte ich ja mehr auf die Unis gehofft.
Zum einen weil der Funktionsumfang doch eher fr deren Bedarf und den der Wissenschaft spricht als 500 Zeichen bei Mastodon. Selbst wenn man das aufbohren kann.
Da bin ich echt ernchtert worden, das die sich freiwillig so begrenzen.

Gerade Unis sehe ich ja am ehesten noch auf Hubzilla. Solche Institutionen knnen Hubzillas Exklusivfeatures bis hin zu Webpages eigentlich sehr gut gebrauchen, sogar auf Studentenkanlen (wobei sich die Frage stellt, ob und inwiefern man nach Studienende seinen Kanal mit allem Drum und Dran dann nomadisch mitnehmen drfen soll nach woandershin).
Aber erstens sind selbst Unis mit Informatikstudiengngen in Sachen IT genauso langsam wie andere Institutionen in Deutschland. Bei denen kommt gerade kleckerweise die Erkenntnis ber die Existenz von Mastodon an. Wenn man Glck hat, halten sie das Fediverse fr nur Mastodon. Viel eher haben sie vom Fediverse noch nie gehrt.
Zweitens suchen sie ja "nur" nach einem Ersatz fr . Erstmal. Da ist Mastodon fr sie auf den ersten Blick mehr als genug. Also gehen sie nach Mastodon. Und weil sie weder Mastodon noch das Fediverse verstanden haben und Mastodon womglich fr eine monolithische Silo-Website halten, schlimmstenfalls nach mastodon.social. Von da aber woandershin umzuziehen, wre so aufwendig, da sie dann an diesem Mastodon-Konto bis in alle Ewigkeit festhalten werden, komme, was wolle.
Und drittens: Sogar Unis mit Informatikstudiengngen haben doch heutzutage keine eigene IT mehr. Das haben die alles hnlich outgesourcet wie der deutsche Mittelstand, nmlich an die Klitsche, die dafr am wenigsten Geld verlangt. Viele Unis drften tatschlich IT ohne jegliche Wartung und Betreuung haben, weil die lokale Computerbude, die ihnen das alles damals eingerichtet hat, ein paar Jahre spter dichtgemacht und weder Dokumentation noch Pawrter dagelassen hat. Wer soll da also eine Instanz fr irgendwas aufsetzen und betreuen
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla Maybe a dumb question: Did you mention your Mastodon counterpart on Friendica
Friendica supports threaded conversations as enclosed objects. Anyone who has received a post also received all comments with no extra means necessary. On Mastodon, however, everyone who is intended to receive a reply must be mentioned.
If Friendica doesn't add mentions automatically, and it usually doesn't, you have to add mentions manually.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica Ja, aktuell merkt man wieder, wie Fediverse-Neulinge durch mehrere Phasen gehen mssen. Klassischerweise war das:

1. Mastodon existiert.
2. Mastodon ist nicht nur eine einzelne Website, sondern eine ganze Menge davon, und die sind (fast) alle miteinander verbunden. Das nennt man "dezentral" und "fderiert". Und man redet auch vom "Fediverse".
3. Das Fediverse ist nicht nur Mastodon, sondern auch noch ganz andere Dinge.
4. Du kannst Leuten auf diesen anderen Dingen von Mastodon aus folgen und brauchst da nicht noch Extrakonten.

Bis vor ein paar Wochen war es nichts Ungewhnliches, wenn Mastodon-Nutzer fr Punkt 2 zwei, drei Monate brauchten und fr Punkt 3 fnf, sechs Monate oder mehr. Und mehr als die Hlfte aller Mastodon-Nutzer kam nie auch nur bei Punkt 3 an. Auch die nicht, die lngst Leuten auf Firefish, Iceshrimp, Sharkey, Akkoma, Friendica, Mbin usw. folgten, ohne das zu merken.
Jetzt werden gerade unzhlige Mastodon-Nutzer, die teilweise schon seit 2022 dabei sind, geradezu zwangsweise auf Stand Punkt 3 gebracht. Jetzt erfahren sie, da es auch Pixelfed und Loops gibt. Und jetzt zeigt sich, wie unvorstellbar Punkt 4 ist, nmlich, da man direkt von Mastodon aus einem Pixelfed-Konto folgen kann.
Gleichzeitig werden Leute von Facebook ins Fediverse geholt, nicht selten direkt nach Friendica. Die bekommen aber gleich die "Druckbetankung" bis auf Punkt 4 innerhalb weniger Tage, Stunden oder Minuten. Die glauben gar nicht erst, da Friendica nur Anonsys, Loma oder friendica.world ist, und hoffentlich auch nicht, da das Fediverse nur Friendica ist.
Im Grunde ist das ja auch im Spirit der alteingesessenen Friendica-Community, fr die es bei Friendica sogar dazugehrt, da sie sich mit allem verbinden knnen, was nicht bei drei auf dem Baum ist. Es wre schade, wenn die ganzen Facebook-Flchtlinge jetzt die alte Friendica-Kultur, die sie nie kennengelernt haben, verdrngen mit einer ganz neuen Kultur, die Friendica als entweder Walled Garden oder Zentrum des Fediverse ansieht, nach dem sich alles andere zu richten hat.

Mit den vielen die jetzt (berzeugt werden und) Plattformen wie fb verlassen kommen eben auch viele bzw. eine Menge mehr "nur user".

Was ich aktuell viel sehe, das sind Leute, die schon auf Mastodon sind und jetzt zustzlich von Facebook abhauen wollen. Da sind einige schon weit jenseits von "was ist eine Instanz". Die wollen nmlich ihre eigene aufsetzen.
Solche Leute sind dann manchmal auch hardcore genug, da ich sie gleich an Friendica vorbei zu (streams) kriege, auch wenn's dafr keine Mobil-Apps gibt. So oder so freuen die sich ein Loch in den Bauch, da Friendica, (streams) und sogar dieses Monster Hubzilla nur einen LAMP-Stack brauchen und auch nur wenig Hardware drunter.
Ich glaube, ich habe sogar vor ein paar Tagen den einen oder anderen nach Hubzilla geholt. Die, die da jetzt hingehen und bleiben, haben meinen Respekt verdient. Ich meine, selbst wir alten Recken lernen stndig neue Sachen an Hubzilla kennen, die es da teilweise schon gab, als es noch Red hie. Daran sieht man doch schon die immense Lernkurve.
Jedenfalls rotiere ich aktuell ziemlich, weil ich auf "in den ther gerufene" Supportanfragen bezglich Friendica reagiere, die die alten Friendica-Hasen nicht mal mitbekommen. Manchmal mache ich es uns allen aber auch einfach, hole die Anfragen auf meinen Stream und repeate sie an meine diversen Friendica-Kontakte. Genau fr sowas ist groe eigene Reichweite in den richtigen Kreisen saupraktisch.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #FacebookExodus #Fediverse #Mastodon #Pixelfed #Loops #Friendica #Hubzilla #Streams #(streams)The Fediverse seems to be going crazy now. Or it's just me and the hashtag search RSS feeds on mastodon.social that I've recently subscribed to.
The blissfully uninformed for whom "Mastodon" and "Fediverse" mean the same have apparently been pushed into the background, just like the fundamentalists who want the Fediverse to be only Mastodon. Even those who have been dragged from Facebook to Mastodon by either of the two groups, and who try to apply what they're used to from Facebook to a wannabe Twitter clone, are few and far between.
No, there are many more for whom the Fediverse is Mastodon, Pixelfed, Loops and Friendica. For many of these, these four are fully separate networks, and they cannot for the lives of them imagine that you can be on one and directly connect to someone on another. I mean, you can't follow Instagram users from either, right So why should this be possible in the Fediverse Isn't the Fediverse an umbrella term for everything free, open-source and decentralised anyway (Spoiler: No, it isn't. Yes, all that stuff is connected.)
Curiously, not only total Fediverse newbies believe this, but even people who have joined Mastodon in 2022. There are Mastodon users for whom the idea is totally alien that Mastodon users can follow non-Mastodon accounts. Mind you, sometimes while following users all over the Fediverse already.
And so there are Mastodon users who join Pixelfed, not because they want to post pictures, but because they want to follow someone on Pixelfed. And they cannot imagine that they can do that from Mastodon.
Likewise, there are Mastodon users who join Friendica, not to shake off Mastodon's tight constraints and get a taste of the good stuff, but because some of their Facebook friends want to join Friendica, too. And they cannot imagine that they can follow Friendica accounts from Mastodon. Even though they may actually already do that.
Speaking of Friendica: This is where things got even crazier.
There are people looking for a Facebook alternative in the Fediverse. Some say someone should totally make one. Because the Facebook alternatives that already exist in the Fediverse, some of which have actually been around for longer than Mastodon, are still too obscure.
And then there are those who do know Facebook alternatives in the Fediverse.
That is, for one, there's the faction for whom "the" Facebook alternative in the Fediverse is Friendica. Not because they think Hubzilla, (streams), Forte and Socialhome are unfit as Facebook alternatives. But because they've never heard of Hubzilla, (streams), Forte or Socialhome. And they themselves are on Mastodon, they don't know a single Friendica user, they've never (knowingly anyway) come into contact with a Facebook user, and so they only know Facebook from hearsay and by name.
And then there's the faction that suggests Friendica and diaspora*. Clearly, they only know both from hearsay and by name, too. For it's obvious that they don't know two important things about diaspora*.
One, diaspora* does not use ActivityPub. It is not federated with Mastodon (which, for many, defines "Fediverse"). The only projects that can communicate both via ActivityPub and with diaspora* are Friendica, Hubzilla and Socialhome. Granted, if you regard the various server applications in the Fediverse as "decentralised walled gardens", and if following a Friendica account from Mastodon goes beyond your comprehension, this doesn't matter.
Two, diaspora* is withering away. A few days before New Year's Eve 2024, several of the bigger diaspora* pods shut down for good. According to at least one statistics site, diaspora* lost more than half of its users within three days. And on Saturday, January, 25th, diasp.org will be the next, one of the biggest and most important pods.
Well, and then there are those on Mastodon who think about joining Friendica, but who need some information first. They shout their request for help into the void. And almost never does even a single actual Friendica user reply. Not even a former Friendica user. Instead, either all replies come from other Mastodon users who only know Friendica from hearsay, or nobody replies at all.
All this is where I keep having to step in.
Just like the last three years when I kept having to tell people that, no, the Fediverse is not only Mastodon, now I often have to tell them that, no, Friendica is not the only existing alternative to Facebook in the Fediverse. I've lost count of how many times I've told people about Hubzilla and especially (streams). I've even made that cover Friendica, Hubzilla and (streams) and additionally Mastodon so that Mastodon users have something they can relate to, just so that I don't have to explain the same stuff over and over again.
It's especially when a replacement for Facebook groups, private groups in particular, is requested that I suggest (streams) instead of Friendica. Yes, Friendica has private groups, too. But why not try and go all the way with fine-grained permission control, with four different types of groups to choose from and with the possibility to use the permission system to appoint additional admins, not to mention instance shutdown resilience by means of nomadic identity
I may actually have successfully gotten a few people to join (streams). The lack of public, open-registration instances (there are only two) doesn't even seem to matter because many are looking for something to host themselves. (streams) is nice for self-hosting because it has a rather small footprint, especially considering how powerful it is, and all it needs is a LAMP stack. Granted, self-hosting (streams) kind of defeats the need for nomadic identity, at least mostly. And I'm still not sold about the idea of setting up a server of something before you really know what it is and how it works and handles. Oh well.
In fact, I'm recommending (streams) more often than Hubzilla now, also because it's easier less difficult to set your channel up and get going. I mean, (streams) can really need some more users. Still, it kind of feels like backstabbing the Hubzilla community that's looking for new users itself. And it'd feel like going into direct competition with the Friendica community, weren't it for the fact that the Friendica veterans whom I'm directly or indirectly connected to don't even notice most of those help requests, much less what I'm doing.
That is, if someone really explicitly needs help with Friendica specifically, I do something else: I import the post itself into my stream, and then I repeat (= boost) it. I'm connected to enough Friendica users to increase the likeliness of help from the right people by magnitudes.
But often enough, the biggest obstacle is another: The help-seeker is on an iPhone, probably exclusively, and they couldn't possibly use any Fediverse server software without a native iOS app. In this case, it barely matters whether they join Friendica or Hubzilla or (streams): There's nothing for Friendica in the Apple App Store.
Yeah, sure, you can connect Friendica to at least some Mastodon apps, much unlike Hubzilla and (streams). But using Friendica with a Mastodon app that doesn't cover several of Friendica's core features can only be a stopgap, and what people are looking for is a full-blown, permanent replacement for the Web interface which they never ever want to lay their eyes and hands on. Ever. And getting into the beta test for Relatica is too much of a hassle for almost everyone.
But seriously, why do I, a Hubzilla and (streams) user, have to give more Friendica support than actual Friendica users
Well, at least I've yet to be attacked for alleged reply-guying and Fedisplaining.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookReplacement #FacebookGroups #diaspora* #Friendica #Hubzilla #Streams #(streams) #Groups #FediverseGroups

• Look up that someone's Pixelfed ID (<shortname><pixelfeddomain>.<tld>).
• Copy it (to your clipboard for pasting).
• Go to whatever user interface you use for Mastodon (app, Web interface in browser).
• Paste the copied Pixelfed ID into the search field.
• Start the search.
• You should be presented that user's Pixelfed profile along with a Follow button.
• Click/tap the Follow button.

What you (should) have achieved here is: You're following a Pixelfed account with your Mastodon account. Without having to log into Pixelfed. Not even with your Mastodon account.
In the Fediverse, you can follow Instagram users on Twitter, so-to-speak. You don't have to log into Instagram with your Twitter account. You can log into Twitter with your Twitter account. And follow Instagram users. On Twitter.
Or you can follow Facebook users on Twitter. Or you can follow YouTube channels on Twitter. Or you can follow YouTube channels on Facebook. Etc.
Only that the Fediverse has over 10,000 different Twitters, 1,300 YouTubes, over 4,000 different Facebooks and so forth. And they're all connected with one another.
I know this sounds totally incredible. But that's how the Fediverse works.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse There is no Mastodon that covers Friendica's entire functionality, yes. That's because Mastodon apps generally only cover Mastodon's functionality. Only Fedilab goes further, but even FediLab isn't a full-blown Friendica app.
Dedicated Friendica apps like RaccoonForFriendica, Friendiqa, DiCa and Relatica should cover a great deal more of Friendica's functionality. I'm not quite sure if either of them cover everything, e.g. if you can use them to manage the files in the file storage or integrate a Tumblr account.

ActivityPup doesn't automatically mean everyone can do all the stuff the same way as a completely unrelated other platform does.

I don't think there's a single mobile app that uses the ActivityPub C2S API. All Mastodon apps are built against the Mastodon C2S API, and the Mastodon C2S API doesn't cover anything that Mastodon can't do either.
Friendica has its own client API which dedicated Friendica apps make use of.
A hypothetical universal Fediverse app that covers everything of everything would also have to use all Fediverse client APIs out there.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #FacebookReplacement #FacebookGroups #Friendica #MastodonApps #RaccoonForFriendica #Friendiqa #DiCa #Relatica #FediLab

CAPE TOWN, South Africa -- The names are carved on poles of African hardwood that are set upright as if reaching for the sun....CHECK THE FULL ARTICLE BELOW
#117972958

These sites represent Fediverse server applications, just like represents the Fediverse server application Mastodon.
Allow me to elaborate:
Imagine Mastodon as 10,000 big and small Twitters. They're all connected to one another (instance blocks notwithstanding).
But the Fediverse is not only Mastodon. It has never been.
For example, there's . PeerTube isn't a website. Imagine PeerTube as 1,300 big and small YouTubes. And they're all connected to one another.
Here comes the kicker, something that even some people who have joined in the big Twitter migration waves of 2022 haven't understood yet:
Those 1,300 big and small YouTubes named PeerTube are also connected to the 10,000 big and small Twitters named Mastodon. You can literally follow someone on PeerTube from your Mastodon account.
Or . 3,000 big and small Facebooks. All connected to one another. But also connected to the 10,000 big and small Twitters named Mastodon and the 1,300 big and small YouTubes named PeerTube.
This comment, by the way, comes from . But you can see it on Mastodon nonetheless.
That's the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse

That it works only between Friendica instances is not a surprise.

It doesn't.
AFAIK, you can also join private Friendica groups from (made from a Friendica fork by Friendica's own creator) and (fork of a fork of three forks of a fork (of a fork) of Hubzilla, still by the same creator). Nobody knows this because at least three out of four Fediverse users have never even heard the name Hubzilla, (streams) is almost entirely unknown outside its own and Hubzilla's user communities, and what they can do, even fewer people know.
What's true, however, is that you can't join private Friendica groups from anywhere else like Mastodon. And you can't join private Hubzilla or (streams) groups/forums from outside Hubzilla and (streams) AFAIK due to their very advanced permissions systems.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Groups #FediverseGroups

So, AFAIK there's no mobile app that can fully interoperate with Friendica or Streams.

There are multiple dedicated Android apps for Friendica. First and foremost, there is RaccoonForFriendica, but there are also DiCa and Friendiqa. I can't say how much of Friendica's functionality either of them covers I left Friendica many years ago.
There is also Relatica for both Android and iOS, but it's a closed beta, you have to apply for testing it, and it may be buggy.
As for (streams), no, there isn't any mobile app for it. And it's highly unlikely that there will ever be one. After all, the goal for such an app should be to be a full replacement for the Web interface. Just look around Mastodon there are plenty of users who have been around since October/November, 2022, or longer, and who have never even seen the Web interface. So even a mobile app for (streams) with a native mobile UI that only covers what users are likely to need sooner or later would be more complex than FairEmail, and FairEmail is a monster.
Also, (streams) tends to change quickly and without notice. (streams) isn't a project that ceremoniously rolls out new releases like Mastodon, Friendica or Hubzilla, and Fediverse Report has something to cover in its news. Instead, even if the main dev has declared himself retired from Fediverse development, (streams) rolls out new versions every couple days without telling anyone. And a native mobile (streams) app would always have to catch up with these changes.
By the way, there has been one attempt at building an Android app for Hubzilla. It is named Nomad, it's still available on F-Droid, but it hasn't been updated in over five years. Most of it is not native, though it mostly displays the Web interface. Granted, Hubzilla actually manages to be even more complex than its own descendant (streams).
Friendica was made to replace all important functionality of Facebook from the get-go, and not just yesterday, but in 2010, over five years before Mastodon was made. The only Facebook features "missing" from Friendica are Facebook's games, data mining and half the population of the planet having an account on the same website.
If Facebook has it (on its Web interface anyway), and it's actually needed for social networking (FarmVille isn't, for example), then Friendica has had it readily available for almost a decade and a half.
(streams) is from Friendica's own creator and down a long path of forks of which Hubzilla was the first. It still carries Friendica's DNA (minus Friendica's many connection and federation options), but it's technologically more advanced and more geared towards privacy, security and resilience which also gives it a bit more of a learning curve.
Also, both do have groups built-in. Friendica can optionally have private groups, and (streams) can have public groups on three security levels plus private groups, all with some extra permissions configurable.
with Mastodon, Friendica, Hubzilla and (streams) which I've made this week they should clear a few things up.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #FacebookReplacement #FacebookGroups #Fediverse #FediverseGroups #Friendica #Hubzilla #Streams #(streams) I guess I can call myself a Hubzilla veteran. I was there when it introduced "tech levels" which are long gone. I currently have multiple cloned channels, and I do use Hubzilla's special features like and occasionally.
That said, I also use something that you may not have heard of. It's at the end of a long line of forks which leads back to Hubzilla and Friendica, all from the same creator. Officially, it's intentionally nameless and brandless. Colloquially, it's named (streams) after . I've got two channels there as well.
If you want to dive in headfirst, but your Fediverse experience is largely limited to Mastodon, then I'd say that (streams) is easier to get into (only few public, open-registration instances are the biggest obstacle).
Most importantly, (streams) makes handling permissions a great deal easier, and on both Hubzilla and (streams), permissions are everything, and everything is permissions. I mean, I've started writing a Hubzilla getting-started guide, and it contains a whole lot of configuration and app installations and stuff before you can even think about connecting to anyone, much less post.
I'd say that (streams) is better for groups/forums as well. You can do private groups/forums on Hubzilla, but they require the "dreaded" Custom channel role plus getting past a warning pop-up to configure the channel-wide permissions. That's because the only pre-defined channel role for a forum is public.
(streams), on the other hand, has four channel types for groups/forums:

• Normal (public, with file upload for group members to the group channel)
• Limited (like Normal, but without file upload for group members to the group channel)
• Moderated (like Limited, but posts and comments from new members have to be approved by those who are appointed admins this isn't possible on Hubzilla at all AFAIK)
• Restricted (like Normal, but with membership approval by admins and with profile, members and stream hidden from non-members)

To make a group even more private, you can choose for your group to not be listed in directories, and you can of course choose for it to not be indexed by search crawlers (Google etc.).
As a normal user, you can hide any of your connections from spying eyes, including groups/forums which you don't want to openly admit you're a member of. But that's possible on Hubzilla as well.
(streams) has a few more perks in comparison to Hubzilla. For example, alt-text. (streams) lets you add alt-text to images either when uploading them to the file space of your channel or after uploading. And whenever you embed that image into a post, you always get the same alt-text. Hubzilla, on the other hand, always requires you to manually edit the image-embedding BBcode in your post draft and add the alt-text to it.
Speaking of BBcode, Hubzilla only supports that in posts. (streams) supports any combination of BBcode, Markdown and HTML.
Hubzilla's big advantage are of course the several extra features: Articles, Cards, Wikis, Webpages. And unlike (streams), it still keeps newer versions of some of Friendica's many connectors around, including to diaspora*.
In case you're curious, I've made an article with a number of tables that compare the features of Mastodon, Friendica (as far as I know them), Hubzilla and (streams).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Groups #FediverseGroupsFr die, die es noch nicht mitbekommen haben:

Fediverse Sprechstunde!
am Donnerstag 23.01.2025, 19:30 Uhr!
ONLINE!
Bist du oder in der Welt des Fediverse Kein Problem! Wir helfen dir bei den ersten Schritten: Profil einrichten, Sicherheitstipps, Posten und Vernetzung. Sei dabei!
Hauptthema: mit pepecyb - Ich freue mich darauf.
Eingeladen sind auch alle, die bereits Erfahrungen mit Mastodon, Friendica, Pixelfed, Misskey oder anderen Anwendungen haben und ihr Wissen gerne weitergeben mchten.
Wissensaustausch: Deine Kenntnisse im Fediverse knnten anderen Teilnehmern sehr ntzlich sein, besonders denjenigen, die noch neu in der Community sind.
Networking: Dies ist eine hervorragende Gelegenheit, sich mit anderen engagierten Mitgliedern der Gemeinschaft zu vernetzen und neue Kontakte zu knpfen.
Ideen und Inspiration: Deine Perspektive als erfahrener Benutzer oder Betreiber einer Instanz kann dazu beitragen, innovative Ideen zu frdern und die Zukunft des Fediverse mitzugestalten.
Der Raum wird 10 Minuten vor Beginn geffnet.
Der Link: kommt wird hier 1 Tag vor Beginn gepostet und steht in meinem Profil.
Das Online-Treffen findet auf unserem BigBlueButton-Server statt. Du bentigst keine zustzliche Software, sondern nur einen Browser vorzugsweise Firefox oder Chrome ein Mikrofon (es handelt sich schlielich um eine Sprechstunde) und, wenn du mchtest, eine Webcam. Wir freuen uns auf einen lebhaften Austausch!
Der Ablauf der Sprechstunde sieht folgendermaen aus: Zu Beginn geben wir Tipps und Hinweise fr Anfnger und Einsteiger. Anschlieend geht es um Ratschlge fr Instanzbetreiber und Moderatoren. Ein solcher Austausch ist wichtig und notwendig fr eine gute Vernetzung untereinander. Es wird nicht nur um Mastodon gehen, denn die Welt des Fediverse ist weitaus grer. Mehr Miteinander statt Gegeneinander.
Je mehr mitmachen, desto besser!




#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteTweet #QuoteToot #QuoteBoost #Drko #Fediverse #FediverseSprechstunde #Hubzilla

do u have experience with streams

Yes, I've got of my own.

Is it being maintained

Yes. Even though the main (and pretty much only) maintainer has declared his retirement effective September 1st, (streams) still unceremoniously rolls out new versions every couple days.

Is it compatible w masto clients

Nope.
And to be honest, it wouldn't even make sense. A Mastodon app couldn't even cover 10% of (streams)' features as it only covers Mastodon features. It wouldn't give (streams) users access to important, essential, even critical features just because Mastodon doesn't have them.
No threaded conversations. Maybe not even reading replies at all. No text formatting. No posting images. No CWs. No alt-text. No handling connections. No permission control whatsoever. I'd be surprised if you could even reply to anyone. You couldn't do much more than post in public.
On a phone, you've only got two choices, both of which mean you'll use the Web interface:

• Use it in a browser.
• Use a browser to install (streams) as a Progressive Web App.

Just so you know what I'm talking about, and just in case you've missed it:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Streams #(streams) That's kind of difficult, actually.
Technically speaking, there is Friendica which was created in 2010 as a Facebook alternative (better than Facebook rather than an outright Facebook clone), and there are Hubzilla and (streams), both descendants of Friendica created by Friendica's creator. They're quite powerful, (streams) more than Friendica and Hubzilla even more than (streams), and they've got everything you need for social networking.
I've made a series of tables that compare these three with one another and with Mastodon.
But if you say, "app," I suppose you mean, "dedicated native mobile phone app." This is the first hindrance. Native specialised phone apps are only available for Friendica and then only for Android and Sailfish OS. The only iOS Friendica app is a closed beta it exists, but you have to join its beta test program instead of being able to load it from the App Store easy-peasy.
Technically, you can use Friendica with some apps made for Mastodon. But you'll only have those features that Mastodon has, too. You won't see threaded conversations. You won't have text formatting. You won't have groups. You won't be able to post pictures. You won't have any access to any configuration. And so forth. You'll only have the absolute, bare-bone basics.
Otherwise, and for Hubzilla and (streams) generally, there's no way around the Web interface (browser, PWA).
As for community building, Friendica, Hubzilla and (streams) not only support groups, but they have groups/forums, optionally even private ones. Organisational presentation is possible, too. All three have blogging-level support of text formatting in their posts all the way to embedding an unlimited number of images right in the middle of a post. So a group could make an introduction post with headlines and bullet-point lists and tables and pictures and all the shebang and pin it at the top for all (permitted) visitors to see. Hubzilla even supports simple webpages which could be used for presentation.
"Easy and clear," that's the issue here. Friendica has quite a bit of a learning curve. (streams) has an even steeper learning curve. Hubzilla has the steepest learning curve of all three. None of them has the UI/UX of something created by a Silicon Valley start-up from $50,000,000 of venture capital.
Ironically, Hubzilla is the one with the best user documentation. But what I mean is not the user documentation built into the hubs, but that's intended to be built into Hubzilla itself one day and replace the old documentation. If you want to peruse it, you'll have to be told by an experience Hubzilla user that it exists, and where you can find it. Still, Hubzilla is highly complex with quite a bit of pitfalls and the worst UX of the three.
, but it mostly covers how-tos for certain things instead of being a full-blown user manual.
(streams)' built-in help system is gradually being rebuilt from zero, but in the style of a technical specification again. And it's very incomplete.
Still, you will need some kind of documentation to get started with all three, ideally plus how-tos for Facebook refugees on how to get started and then do Facebook things. You can't use on either of the three what you've learned from Facebook. They do have everything you need as a Facebook refugee, but it looks different, it feels different, it works differently.
For example, if you're on either of the three, and you're looking for the place where you can create a new group/forum, you can look forever in vain. Unlike on Facebook, groups/forums are not an additional feature of their own. They're accounts (Friendica)/channels (Hubzilla, (streams)) like your user account/channel, but with special settings. This alone makes many Facebook users scream out that this feature is completely unuseable, simply because it isn't what they expect it to be.
In addition, if you run a Friendica group on the same node as your personal account, you have to log out and back in again to administer or moderate the group and to get gack to your account. But nobody tells you to have your group on another node than your personal account.
On Hubzilla and (streams), it's the opposite: It's better to not only have a group or forum on the same instance as your personal channel, but on the same account. You can have multiple channels, multiple fully separate identities on the same account because your identity is fully detached from your account. If you have your personal channel and your forum channel on the same account, you can jump back and forth between the two. But this is something that practically doesn't exist outside of Hubzilla and (streams), and so, nobody will tell you about this feature.
Even if you can wrap your mind around all this, you still aren't over the hump. Especially not on Hubzilla and (streams). On Hubzilla, you can have a restricted or private group/forum. But you have to dive into the permission settings of your forum channel, a place where you're being warned that you have to act carefully, and set the corresponding permissions accordingly by hand. On (streams), there's less to configure and no warning instead, there are not one, but four types of forums. But neither the Web interface nor the documentation tells you what's what, and what does what.
Another idea, but much less like Facebook, would be . Technically, Mbin is an alternative to Reddit and Hacker News and kind of feels like Reddit, UI-wise. But it also offers personal microblogging instead of being limited to only group discussions, and it's much more compatible with the rest of the Fediverse.
There are two caveats again. One, most Mbin users are former Redditors. This means that Mbin's culture = Reddit's culture, including, but not limited to dank maymays, shitposts all over the place and potentially also power-tripping mods (if you want to join existing Mbin magazines (= subreddits) rather than starting new ones). However, I guess that Mbin, on average, is not as hostile and xenophobic towards the rest of the Fediverse as large parts of Lemmy are.
Two, again, there's no iPhone app that works with Mbin. For Android, there's Interstellar. For iOS, there's only the Web interface.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookAlternative #FacebookGroups #Friendica #Hubzilla #Streams #(streams) #Threadiverse #Mbin

Fedi isn't meant for that. It doesn't provide encryption.

Mastodon doesn't. But just because Mastodon doesn't, doesn't mean it isn't available anywhere in the Fediverse.
() and () offer groups/forums like Facebook groups. These groups can even be made private. This means:

• These groups aren't listed in directories.
• You can't see the group profile unless you're a member.
• You can't see what's happening in the group unless you're a member.
• You can't see the members of the group unless you're a member yourself.
• You can join public Hubzilla or (streams) groups from Mastodon, but you can't join private Hubzilla or (streams) groups from Mastodon, only from Hubzilla or (streams). And even then, your group membership must be manually approved.
• Groups can theoretically even have various ranks of memberships with various levels of permission. So even new members may not see everything.
• Conversations within private groups are hidden from everyone who isn't part of the conversation. They don't show up on federated Mastodon timelines, full stop. They're like DMs, but not necessarily with only two participants.

If you really want to talk in private, you and your counterpart can activate encryption, exchange a common password and communicate with encryption both on the servers and during transmission. In theory, even groups/forums can activate and, if so desired, use this form of encryption.
And Hubzilla and (streams) are very much part of the Fediverse. I'm on Hubzilla right now, and you can read this on Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams)

Last updated: 2025-01-27

Problems Making a Will rule from beyond the grave