that the main way people use groups for microblogging is suddenly defunct because one person forgot to renew their domain might be a good indication that decentralisation and network resilience includes more than counting the number of servers
-
@laurenshof wait, what did I miss?
@jenniferplusplus aguppe groups is dead, they lost their domain name
https://github.com/immers-space/guppe/issues/118 -
@jenniferplusplus aguppe groups is dead, they lost their domain name
https://github.com/immers-space/guppe/issues/118@laurenshof @jenniferplusplus What is/was that, in short? Never heard of it
-
that the main way people use groups for microblogging is suddenly defunct because one person forgot to renew their domain might be a good indication that decentralisation and network resilience includes more than counting the number of servers
@laurenshof One way to solve this would be for users to have a server where they can store their personal data, and then connect it with another app that can view the same data so they can pick up where the last one left off.
-
@laurenshof @jenniferplusplus What is/was that, in short? Never heard of it
a sort of hacky system to create groups for Mastodon, where if you tag the group account it gets boosted to all the people following it. didnt work super well, but it was the most used system for lack of an actual group system thats compatible with microblogging
honestly fairly similar to hashtags, but it had some form of rudimentary moderation system tacked onto it i believe
-
a sort of hacky system to create groups for Mastodon, where if you tag the group account it gets boosted to all the people following it. didnt work super well, but it was the most used system for lack of an actual group system thats compatible with microblogging
honestly fairly similar to hashtags, but it had some form of rudimentary moderation system tacked onto it i believe
@laurenshof @mackuba it also works around federated delivery issues in a way that hashtags don't.
-
@laurenshof @mackuba it also works around federated delivery issues in a way that hashtags don't.
@jenniferplusplus @mackuba hmm, mind saying more on that? the edge cases with ap delivery stuff is confusing
-
@jenniferplusplus @mackuba hmm, mind saying more on that? the edge cases with ap delivery stuff is confusing
@laurenshof @jenniferplusplus @mackuba Hashtags aren’t federated beyond your follows. So you’ll never see topics with those hashtags if you aren’t already connected in some way.
Everyone follows the guppe account related to a topic, and that account boosts and delivers all posts directly to you. I don’t have to be following you to get your post if we both follow the guppe account.
-
@laurenshof @jenniferplusplus @mackuba Hashtags aren’t federated beyond your follows. So you’ll never see topics with those hashtags if you aren’t already connected in some way.
Everyone follows the guppe account related to a topic, and that account boosts and delivers all posts directly to you. I don’t have to be following you to get your post if we both follow the guppe account.
@box464 @jenniferplusplus @mackuba hashtags also federate to the accounts who follow the hashtag though right? even if they dont have a direct follow connection
-
@box464 @jenniferplusplus @mackuba hashtags also federate to the accounts who follow the hashtag though right? even if they dont have a direct follow connection
@laurenshof @box464 @jenniferplusplus I mean, you only see hashtagged posts if they're somehow already on your instance. So for example, following hashtags is completely useless on my instance, because I will only see posts that I already see anyway.
-
@laurenshof @box464 @jenniferplusplus I mean, you only see hashtagged posts if they're somehow already on your instance. So for example, following hashtags is completely useless on my instance, because I will only see posts that I already see anyway.
-
@laurenshof @box464 @jenniferplusplus Yeah, this can't really be easily solved using the current AP architecture I think, because when you make a post with # something, your instance would somehow need to know that it needs to push that post to all instances where someone is following that hashtag… so here that group service is handling this I guess.
-
a sort of hacky system to create groups for Mastodon, where if you tag the group account it gets boosted to all the people following it. didnt work super well, but it was the most used system for lack of an actual group system thats compatible with microblogging
honestly fairly similar to hashtags, but it had some form of rudimentary moderation system tacked onto it i believe
laurenshof@indieweb.social ah I’d say that Piefed ended up beating aguppe on that… Ask atomicpoet@atomicpoet.org
-
@julian@activitypub.space @laurenshof@indieweb.social @general@activitypub.space I agree. Gup.pe always felt like a stop-gap for group microblogging rather than a real solution. The better approach is to cross-post into a proper forum, where people can choose the UI that suits them best. Personally, I’m a fan of Piefed—even if I haven’t yet tested how this plays out on NodeBB.
-
a sort of hacky system to create groups for Mastodon, where if you tag the group account it gets boosted to all the people following it. didnt work super well, but it was the most used system for lack of an actual group system thats compatible with microblogging
honestly fairly similar to hashtags, but it had some form of rudimentary moderation system tacked onto it i believe
@laurenshof @mackuba @jenniferplusplus
>it was the most used system
No. And the project has been officially dead for nearly two years.
-
@laurenshof @box464 @jenniferplusplus Yeah, this can't really be easily solved using the current AP architecture I think, because when you make a post with # something, your instance would somehow need to know that it needs to push that post to all instances where someone is following that hashtag… so here that group service is handling this I guess.
@mackuba
@laurenshof @box464 @jenniferplusplus
This would actually be fairly straightforward to do with the current AP infrastructure by instances maintaining a collection of hashtags that are followed on that instance and caching the collections from other instances and sending to them when a hashtag is used. Its just not implemented by mastodon.
