I just entered several #Guppe groups (e.g. @mathematics @physics
) but the groups just keep silent from my point of the view.
I wonder if it is just because nobody posts for the past 12 hours or some other technical issues (or I just misunderstand the mechanism of it)?
„Das Twitterlehrerzimmer war einmal noch wie dieses coole Stadtviertel, von dem keiner so genau weiß, was genau es eigentlich ausmacht. Aber wo jeder weiß: Da findet man alles und jeden.“
If you haven't heard, sadly, #ChirpSocial, one of the popular #ActivityPub “groups” platform, is shutting down “probably” on February 29th.
In an email they sent to admins, the owner and developer can no longer support https://chirp.social financially as they failed to find a new job after they were laid off by #Google last year.
This reminds us the importance of having a built-in groups feature, and one where the groups feature actually federates.
Back in 2008, when the #Fediverse was born, we did have a built-in federated groups in #Laconica / #StatusNet (today known as #GNUsocial). We used bang (!) instead of at (@). A built-in groups feature is more stable as established instances can host them.
Today, we have #Friendica and #Hubzilla (as well as #Streams-based instances) to fill in that, as groups is a built-in feature in those software products. It's just a matter of finding an instance that's open to hosting groups for any topic for the ActivityPub protocol.
That said, any Friendica, Hubzilla, Streams-based instances you suggest for groups?
@retrobeetism I have a similar experience. #Guppe groups (at least after it went offline for almost a month(?)) rarely works all other #Fediverse platforms (those I've tried). But #Chirp groups, #Friendica forums, #Kbin magazine, and #Lemmy communities, there are rarely any problems.
My brain tells me that the issue is with Guppe platform, since all other similar software works fine. They did something to break interoperability with the rest of the Fediverse, and created its own bubble with Mastodon.
#Guppe for us has been a problem for a long time. Users on our Firefish server just can't follow them. #Chirp too has issues. Especially inbound. The responses are malformed. Right now I have 11 in our Inbound queue which will eventually fail and disappear, so the subscribe user will never see the message.
From what others more knowledgeable that me have said, the implementation of ActivityPub for these services is poorly constructed and have been cobbled together for Mastodon servers
And the lord looked upon the creation of the group @red_state_insurgents
and it was good.
And the lord said "hey all you brave leftist souls living in red states ... Go forth and insurge!
But seriously ...
If this describes you, and you'd like a group where you can plot, scheme, commiserate, support, and maybe have fun meeting some people who share this particular geographic affliction; then come join the fun!
See you there 😎
Oh yeah ... please boost for reach 🙏
@Susan60 Hi, I apologize. I've decided to indefinitely shut down the autobooster since I realized that this is a really ugly workaround (there's just no way as far as the software I used goes to even determine whether it's a reply or posted by a user that has #nobot in their bio) for #GoToSocial's lack of support for relays as well as #guppe and #chirpsocial not federating well with GTS (I can't follow groups from there).
Hey #fediverse, does anyone know if a.gup.pe and chirp.social has some sort of #API which lists all groups in it? I've just thought of an idea to make this #GoToSocial instance I manage federate even more instances than just 600+ servers, which is to #massfollow them all with a #followbot. Yeah it's a really bad thing to use against normal instances (it's gonna annoy humans behind the accounts), but it shouldn't be a problem if I just follow group accounts, right? :sagume_think:
I'm gonna also try mass following every community in #Lemmy and #kbin as well.
#Fediverse question:
Is it just me that has issues following #guppe groups or #lemmy communities on #iceshrimp or #mastodon? Or is this just a problem with ActivityPub microblog platforms?
"'The threadiverse', aka #fediverse group servers like #guppe, #lemmy and #kbin are all based on the premise that each community is hosted on one instance, but users and posts can come from all over. So it's like any normal #phpBB-style forum, except you use your own user instead of having to register and check everywhere.
Makes sense to me, and I'm not saying that they should do it any other way, but this is exactly how mailing lists work."
Mit den vielen neuen #Gruppen im #Fediverse geht euch vielleicht ein wenig die Übersicht verloren. Zum Glück gibt es in #Friendica eine Möglichkeit direkt nach Gruppen zu suchen und diesen zu folgen. Damit entfällt die #Suche auf externen Seiten.
Die Suche wird statt eines "@" mit einen "!" eingeleitet. In der Treffervorschau werden euch alle Gruppen angezeigt, die zu diesen Namen gefunden wurden. Die Trefferliste liefert euch gleich noch die korrekte Adressierung zum Abonnieren einer Gruppe.
Testing how it works when a #Guppe group becomes a “magazine” in #Kbin.
For this post, the test is to see if this will appear as a reddit/stackexchange/quora “question”, or is this post going to appear in Kbin's “microblog” tab?
Bonus: If it appears as a question-type (not microblog), then is it going to federate in other fediverse software that are not reddit/stackexchange/quora types through the Guppe group? Or, should we subscribe to this Kbin “magazine” first?
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.
Earlier this week, #guppe announced that they were going to sunset the platform because they had become too popular, and didn't have enough funding to sustain itself.
But today they announced that due to a last minute surge on Open Collective, they are now able to cover server costs.
The platform lives another day. That said, they still don't yet have enough funding to cover labour costs.
If you'd like to make a contribution, here's the Open Collective page:
> "As a final opportunity to preserve Guppe, we have reduced the minimum contribution amount to join the Guppe Platform Cooperative to $2/month or $19/year. If Guppe cannot reach a level of funding to cover all of the hosting and a couple hours of administrative labor per month, then service at a.gup.pe will shut down on May 31st, 2023."
@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.
The long-running Fediverse group service Guppe (https://a.gup.pe) will shut down on 31st May 2023 if it doesn't receive enough funding to cover its costs:
Testing how posting a Kbin ‘thread’ works (fedia.io)
If the Kbin ‘magazine’ is a #Guppe group.
deleted_by_author
Mastodon monoculture problem (rys.io)