- cross-posted to:
- [email protected]
You must log in or # to comment.
There is $4k in the bank in their OpenCollective, that should be enough to buy a new domain name. Let’s see what happens.
I never saw the point of these at all somehow, but maybe someone can explain how I’m wrong (because I may well be!):
The way I understand guppe groups worked is that you could create any group simply by tagging or following any string followed by a.gup.pe. But those groups didn’t have moderators or owners or anything like that. How is that different from following a hashtag?
Threadiverse communities differ from following hashtags by having moderators who can remove posts or ban users. That provides extra value because that means people can’t post spam or off-topic things in them as long as the mods are doing their jobs. But if that isn’t possible, then why not just follow a hashtag and post to it?
In any case, it seems that federation to Lemmy never worked properly, it was possible to see that guppe groups existed on Lemmy, but they didn’t accept my follow request and (maybe because of this?) didn’t federate at least to my instance: https://discuss.tchncs.de/c/[email protected] and https://discuss.tchncs.de/c/[email protected] are both empty despite me being in “subscribe pending” state on them.
Mastodon hashtags are not accounts and do not
Announceevery post and reply like Lemmy. If nobody follows you on external instances, your hashtagged toot will not leave your instance. On the other hand, if you mentioned a guppe group followed elsewhere, the group would boost you post to its followers.Better (more Lemmy-like) discovery.
PieFed was able to subscribe to Guppe groups along with PieFed/Lemmy communities, Mbin magazines and PeerTube channels.
That’s a good point, thanks.
I see good points in this comment, even if the analogy of their being like hashtags might be a little off.
gup.pe groups have a 1-word description. Most of them I’ve been unable to assign a topic to because I didn’t know what the word means or it has ambiguous meanings. Most have no posts. So they land in the “unknown” topic.
I always wondered what I would do if someone started posting porn or hate to them. It would be a nightmare. I’d just have to block the group, I suppose.
Frankly, instead of someone creating a gup.pe-like group, I think they ought to create a community in PieFed, MBIN, or Lemmy. gup.pe was an early experiment when there wasn’t a threadiverse.
I tested posting from Mastodon to test Lemmy communities on two different instances (szmer.info and fedit.pl). The toot arrived at fedit, but neither community reblogged the post into Mastodon. Lemmy will not work as a Guppe alternative.
Threadiverse communities differ from following hashtags by having moderators who can remove posts or ban users. That provides extra value because that means people can’t post spam or off-topic things in them as long as the mods are doing their jobs. But if that isn’t possible, then why not just follow a hashtag and post to it?
Same feeling here.
I could’ve sworn that Guppe has announced that the project was dead (looked it up, I’m thinking of Chirp which recommended moving to Guppe). The last commit was two years ago, so it may well be anyway.
There is another group solution for Mastodon: https://fedigroups.social/ .
@rimu, you probably want to check if groups there work with PieFed
They do not :(
It’s probably not hard to fix but after finding a.gup.pe pretty disappointing (see Jerry’s comment) I’m not enthusiastic. If Mastodon users want to do groups they should switch to a platform that does them properly.
To Misskey, whose channels do not even federate? (and no fork has changed this behaviour) To Pixelfed, which promised having groups many times, but still has not delivered them yet? To Friendica, which suffers from performance issues, and fixes for them will arrive only in the future? To PieFed, Mbin or Lemmy and give up on feeds of followed people? Out of the Fediverse?
I use both Mastodon and PieFed. It’s ok to have two accounts, they’re free ;)
$10 says it was to get rid of @[email protected]
