Apparently Lemmy.world and Beehaw having some beef at the moment. No idea what's going on. Just saw some posts about one defederating the other. What a nice way for all the reddit refugees to get introduced to Fediverse politics :ablobbonelightstick:
@JungleGeorge It depends on how the UI and UX works for an individual.
For example, for me #Lemmy feels “isolated”. It doesn't show you the wider #fediverse. But in #Kbin, it has a “Microblog” tab where you will be able to see what the rest of the fediverse are saying about your topic -- posts that don't appear as a “Thread”.
For other people, #Calckey's UI and UX are working well. Like me for example, I see the topics I want to see, and the communities around it, because I'm using Calckey's antenna feature combined with a Deck UI. I see discussions and communities I do not see from a Mastodon instance.
I also used to have a solo #Hubzilla instance and I can say the same for it, I can see the wider fediverse and the different communities surrounding the different topics I am interested in.
The thing with a fediverse account, first and foremost, it is what it is for you based on how you built your network. What you see, what you interact it, is your #ObservableFediverse.
Some people only follow groups/communities/magazines. They have few 1-to-1 “following”. If the instances these groups/communities/magazines goes offline… their “Observable Fediverse” will be cut a lot, and they might even feel isolated suddenly.
So, for me, my “Observable Fediverse” is wide and revolves around the topics I care about. Thus, I see the “community” in using Calckey and Hubzilla (and Kbin for that matter) far more than using Lemmy.
^_^
(PS I have accounts where its “Observable Fediverse” is purely reliant on groups/communities/magazines. It's a totally different Fediverse experience from those accounts.)
All these “fediverse browsers”, like Lemmy and Kbin, are commonly referred to as fediverse software. (extra info: Wikipedia calls Lemmy, Kbin, and similar answers-type or Threads-type software as “Link-aggregators”.)
There is no “Mastodon network”. There is no “mastoverse”. There is no “threadiverse”. There is no “Threadinet”, or whichever -verse / -network people are coming up with.
Any software that is using the ActivityPub protocol is part of the “Fediverse network”. Just like how any software that uses the HTTProtocol is part of the Web.
That clear so far?
Now, we go to your question.
Q: I moved to lemmy.world and have noticed that lemmy.ml has been popping up as another featured instance. What differs from lemmy.world vs lemmy.ml? Is .ml more active?
lemmy.world and lemmy.ml are called instances (the terminology used to refer to a fediverse server/service). These two are only two out of many fediverse instances available. In paritcular, these two instances are only two out of probably a hundred Lemmy-based instances available.
What differs between the two? As far as features and functionalities go, none. Since these two Lemmy-based instances are using the same software, they have the same set of features. The only difference would be if one instance fell behind in Lemmy version upgrades.
Since lemmy.ml is one of two flaship servers of the Lemmy software project, naturally it will get the bulk of registrations and content.
For example, before the Reddit Migration, there were already existing communities for many similar Subreddits, and many of those are in lemmy.ml and are very active. So, when Subreddits started to migrate, some chose lemmy.world and other lemmy instances. Which allowed lemmy.world to catch up with the number of users and number of active communities that lemmy.ml already have. AND, some of these are about the same topics/fandom.
vielleicht auf #Hubzilla ? gnulinux.ch/serie-fediverse-di… @Jupiter Rowland ist gerade am Testen, wie die Föderation zwischen Hubzilla und #Lemmy so im Einzelnen läuft und könnte da vielleicht mehr zu sagen?
Fediverse-Serie: ActivityPub bei WordPress - einen Blog in ein soziales Netzwerk bringen
Das Plugin implementiert das ActivityPub-Protokoll in einen Word-Press-Blog, was bedeutet, dass Blogbeiträge im Fediverse verfolgt werden können. Darüber hinaus werden Antworten aus dem Fediverse automatisch zu Kommentaren im Blogbeitrag.
If there isn’t much cross-platform engagement between the #threadiverse and #mastodon, and Reddit migrants leave because of insufficient activity … is this a failure of sorts of the #fediverse ?
I’m leaning yes. If cross-platform activity is essentially irrelevant but more of a minor awkward perk at times then the fediverse doesn’t exist (yet) at the level of being a social media platform or space.
Instead, it’s a tool for FOSS platforms to scale through decentralisation.
It depends on how you look at it. There are thousands of fediverse servers, and there are at least a million active users in total.
Based on the context of this discussion thread/branch, those Lemmy servers mentioned would not even fall near the “dominating the network”, they are very far from dominating the fediverse network.
But, if you are referring to “Reddit-like / Stackexchange-like / Quora-lack”, then sure, those servers mentioned are “dominating” the “answers UI/UX” space. However, the fediverse doesn't work like that, and you probably won't even notice it while using any fediverse software.
In the fediverse, #Lemmy and #Kbin servers acts like a group. If you have used #Chirp and #Guppe groups (chirp.social and a.gup.pe respectively), then Lemmy and Kbin servers works similarly.
If I post to a Lemmy “community” or to a Kbin “magazine”, that post will be re-shared/boosted/re-posted to everyone who subscribed/followed that community/magazine. Anyone who replies to that post, it will be re-shared/boosted/re-posted also.
In other fediverse software, it will just appear as a regular status update thread. In Lemmy and Kbin, it will appear as a comment to a certain post.
It's the same for, say, #BookWyrm. The flagship BookWyrm server is “dominating” the “bookshelf UI/UX” space, however, outside of that, it's just another software. The only difference is that with BookWyrm, you get a shelf, track your book reading, leave reviews to a specific book, and so on.
However, everything else are the same… if you leave a comment or posts an update about the book you are reading, it is no different from using #Calckey, #Hubzilla, #Friendica#Misskey, #Rebased, #Akkoma, #Mastodon, #Pleroma, to post a new update that “I am not at page 879 of the book ‘Shaka. When the Walls Fell’.”
And as far as the fediverse is concerned, BookWyrm is far from “dominating” the network.
Having second thoughts about my self-hosted #Mastodon instance, it’s just too much of a resource hog for a single user / small instance on a 4 core / 4G vServer if you want to run other stuff (#writefreely is live, #pixelfed to be installed!) as well. On the other hand it is very nice that the software is stable, reliable and well designed. So either I need to move to a bigger server or decommission my self-hosted profile and look into other options for micro / macro blogging self-hosting again. I did like #gotosocial but the current version doesn’t install on my #yunohost properly. Tried #Akkoma and #Pleroma - weren’t my thing, can’t get over the design. I do like #Friendica and its possibilities but it is a bit clunky at times and I have some doubts if protocols other than the quasi standard #ActivityPub have much of a main stream future which kinda could make the additional Friendica features a little islandish. Same applies to #Hubzilla which I only start testing. Leaves #Misskey and #Calckey which could be good options but not sure about the reliability and gameplan there, I don’t want to tinker every night on my server so #Calckey probably need to become a little more stable first, #Misskey seems to have no current version on YunoHost, so need to explore other install options… Any thoughts very welcome! @fediversenews@fediversede
Join the JoinFediverseWiki - "eine Enzyklopädie über das Fediverse"
Das Wiki bietet schon umfangreiche Informationen über das Fediverse und dessen diverse Plattformen. Es enthält jedoch auch noch einige Lücken, die darauf warten, von fleißigen Fedizens gestopft zu werden.
After the registration process, it's time to create your first channel. You will have to choose if you want it to be public by default ("Public") or followers-only by default ("Personal"). Don't worry, this setting can be overridden for individual posts if you wish.
Find your first contacts. Since you are here, you probably already know some Hubzillians. (If your server supports Activitypub you can also add contacts from Mastodon, Calckey, Friendica).
Those are the necessary steps, simplified. Hubzilla is a huge toolbox with a lot of possibilities to fine tune your settings. But for your first try - this will be enough.
@shimriez where does a #Hubzilla user have to go to learn about its quirks? I have a clear question but having to ask it on #ActivityPub would hurt my feelings for Hubzilla 😁
#ActivityPub#spam seems to be spreading nowadays. It isn't new, I moved away from my previous instance because it didn't have active mod volunteers.
#Snikket's idea of invites (#XMPP, not AP) seems like a good way to both control spam and onboard users. Mods can rate-limit account creation by judiciously creating invites. Users can generate 1 invite each, but can expect to also get banned if their invitee is a spammer. User-invited users would have a real account to bootstrap their connections.
@volkris interesting view. Web of trust-ness seems to be there in #SecureScuttlebutt (it "gossips" content from friends and friend-of-friend, friends are cryptographically verified by design).
Per your view, #Zot / #Nomad would work well on the user-in-control front (although whether their #Hubzilla / #Streams UX implementations work for users is questionable).
I envision actors having public keys as their IDs, possibly with some system for updates/revocations. When actor references are passed, they're sent together with the current (or last known) network location of the actor. Each server keeps a directory mapping IDs to locations. Actors can transparently move between instances, by sending a Move notification about their new location. Anyone who misses the notification can query friends/others who did get it.
@pere
> public keys as ID's
> directory mapping ID's to current location
#Hubzilla does this in its #Nomad protocol. In its #Streams incarnation, it seems to present #ActivityPub posts as a public stream and native Nomad posts as a fine-grain-permissioned stream.
@butter, @dessalines, I've grown quite fond of Friendica for that very thing, following things, not just people. Not only does it let me follow topics via tags, but things like #lemmy and #guppe get added as "forums", plus I can follow any #RSS or #Atom feed. All of these are added the same as adding any other contact (follow). All of these different ways of following things get listed in the same area of my account, as "contacts", where they can be easily separated into to multiple groups (lists). Each followed hashtag, forum, contact group, or protocol type is always listed down the side of my page where I can simply click on it to filter my current feed.
I know that other #fediverse / #ActivityPub interfaces such as #Pleroma, #Akkoma, #Misskey, #Calckey, #Hubzilla, and #Streams have some/all of these capabilities, each to their own extent. However, having played around extensively with all of them, I've come to find that #Friendica is the one that works best for me. And at the end of the day, this is the only thing that matters. It may be a bit time consuming, but trying all the things is the best (only?) way to see how they'll work for you.
Auf der Suche nach #socialmedianetwerk relevanten Webseiten zum Selbsthosten gerade über einen Artikel von Chris Burger gestolpert und in begeistert gelesen!
Hut ab ... ich werde mir das auf jeden Fall einmal genauer ansehen! :)
@chris
Stimmt. Umso wichtiger, sie #sinnvoll zu nutzen - was mir - durch externe Anforderungen - leider immer schwieriger fällt.
Deshalb jetzt etwas Nachforschung, wie ich mich möglichst stressfrei möglichst unabhängig im Netz bewegen kann und meine Anforderungen fokussieren. #hubzilla scheint da eine echte Alternative zu den ganzen verstreuten Diensten zu sein.
@jeff we already have been there almost 10 years ago with #diaspora*. I personally hosted a pod (an instance of diaspora*) during seven years. This is why my hope for the federation by that time was a protocol taking into account the precarious nature of servers in a decentralised network. Notably minimal dependency upon DNS for users. But we got #activityPub poorly protected against servers shutdown rather than #Hubzilla and it’s nomadic identities persisting beyond servers lifetime.
I think it's safe to say that only Mastodon opens uses its local cache to open a remote profile. Other software, regardless if they have a local cache, opens the URL since it starts with https: and not a webfinger.
But it's also not entirely @gruber's fault because the media doesn't really talk about the Fediverse, and when they do, it's as a synonym for "Mastodon".
How would @gruber know about the massive development efforts to build more user-friendly alternatives to Mastodon?
No one in the media talks about the growth of *key apps, and how they're now the #2 most used Fediverse platform.
The main reason why I can't move from my current #Pleroma installation to anything else ( #Akkoma, #Misskey, #Calckey, #Hubzilla or #Friendica ) is that none of them accept importing an existing backup from a different service into a brand-new account. At most you can migrate your address but not your posts.
It will depend on the platform. For example, #Friendica (and to an extent #Hubzilla and #Streams), the owner of the group (and anyone else given moderation access) can block accounts. There is also chirp.social which can also block accounts.
Then there is #GNUsocial, which is a rebranded #StatusNet itself a rebranded #Laconica (the first #Fediverse software, c. 2008) have built-in groups feature; which IIRC, can also block users if needed.
Personally, services like Guppe really need to add moderation features, otherwise, what you just described will more likely happen.
deleted_by_author
Wiki o.ä. für Standard-Fragen German
Gibt's auch Pläne, hier ein Wiki für Standard-Themen/Fragen aufzubauen? Wo könnte das gehostet werden?...
deleted_by_author
Other use cases for the fediverse
I never got into mastodon because I couldn't connect multiple instances. I like this a lot about Lemmy so far (just here for a few minutes though)....
Mastodon monoculture problem (rys.io)