New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support groups #139
Comments
|
I made a decision not to implement groups. They offer little benefit over a cost of added complexity, and the bangtag syntax personally irks me too. |
Revert "Revert "Create component for announcements"" Merge pull request mastodon#161 from pixiv/revert-160-feature/create_component_for_announcements Revert "Create component for announcements" Merge pull request mastodon#160 from pixiv/feature/create_component_for_announcements typo Change announcement manager Remove unused import remove comment out Create react-component for announcements Merge pull request mastodon#156 from pixiv/revert-155-fix_autosuggest_z_index Revert "トゥートの登録フォームで長文を書いても、アナウンスパネルにかぶらないように" Merge pull request mastodon#155 from pixiv/fix_autosuggest_z_index (origin/fix_autosuggest_z_index, fix_autosuggest_z_index) Add zindex style (svg_encode) Merge pull request mastodon#141 from pixiv/add_privacy_policy_for_sp Fix title/ogp. Fix text. Merge pull request mastodon#151 from pixiv/add_protocol (origin/add_protocol, add_protocol) Add protocol Merge pull request mastodon#149 from pixiv/allow_5_megabytes (origin/allow_5_megabytes, allow_5_megabytes) Reject large profile Merge pull request mastodon#148 from pixiv/notice_pixiv_link (origin/notice_pixiv_link, notice_pixiv_link) pixivアカウントと連携した場合の注意を表記する Merge pull request mastodon#147 from pixiv/disable_two_factor_authentication (origin/disable_two_factor_authentication, disable_two_factor_authentication) Hide two factor authentication if user is linked with pixiv account 二段階認証が有効な場合はpixiv連携できない Merge pull request mastodon#145 from pixiv/remove_announcements (origin/remove_announcements, remove_announcements) Remove announcements on mobile Merge pull request mastodon#144 from pixiv/fix_sidebar_ex Fix sidebar scroll css. Merge pull request mastodon#143 from pixiv/fix_sidebar_scroll Merge pull request mastodon#122 from pixiv/render_announcements Render announcements Make sideber scrollabled at setting page. Merge pull request mastodon#139 from pixiv/replace_mastodon_to_pawoo Add sample text at view. Add controller method. Add endpoint. Destroy InitialPasswordUsage Remove unnecessary index Expire cache of nginx (origin/replace_mastodon_to_pawoo, replace_mastodon_to_pawoo) Replace 'Mastodon' -> 'Pawoo' Update site_title 'Mastodon' -> 'Pawoo' Replace 'Mastodon' with 'Pawoo' Render pixiv url Prevent destroy if user has initial_password_usage Replace factory.dev with pawoo.dev Add comment for normalize_username Render error message when failed linking Optimize query for finding by uid and provider Update locale of oauth_authentication Rename RedisCache -> RedisSessionStore Enable popup signup sdk Do not remove upcase Replace :preload -> :includes Refactor Form::OauthRegistration Find oauth_authentication by uid (hotfix_oauth_login) Merge pull request mastodon#135 from pixiv/replace_toppage_image Remove site_extended_description Replace demo image Revert cookie_store key Fix text. Revert "Add i18n-tasks to ci" cookie_storeのキー名を変更 Merge pull request mastodon#105 from pixiv/omniauth-pixiv Merge pull request mastodon#124 from pixiv/improve_top_page (origin/improve_top_page, improve_top_page) Skip view spec for contact page Improve home#show home#more Merge pull request mastodon#123 from pixiv/i18n-tasks (origin/i18n-tasks) Add i18n-tasks to ci (origin/omniauth-pixiv, omniauth-pixiv) Fixes undefined method error 日本語とスタイルを調整 Merge pull request mastodon#100 from pixiv/fix/remove-unused-message Fixed typo Merge pull request mastodon#113 from pixiv/omniauth-pixiv-with-badge Add oauth authentication status badge to user page Add oauth authentication status badge Load oauth_authentications Rename `ソーシャルログイン` -> `pixivアカウント連携` Update secrets.yml Fixes gemfiles Update oauth_registration.rb Add null constraint to initial_password_usages Fixes specs Do not delete oauth_authentication if user has initial_password_usage Send reset password instruction if user has initial password Send reset password instruction if user has initial password Create InitialPasswordUsage for initial user Create InitialPasswordUsage Destroy OauthAuthentication that related with expired users Update oauth registration form signin popup Add omniauth action buttons autoresize textarea replace oops image media aspect ratio change to 16:9 Create OauthRegistrationsController CookieStore can not store data because it is tiny Clean redis data each test Create Auth::OmniauthCallbacksController Create Settings::OauthAuthenticationsController Create OauthAuthentication Install omniauth-pixiv Feature/change displayname style (mastodon#102) Merge pull request mastodon#76 from pixiv/feature/hide-follow-when-blocked Merge pull request mastodon#103 from pixiv/fsubal/fix-broken-account-description Merge pull request mastodon#66 from pixiv/fix/url_escape add HTML escape test put a comma after the last item ブロックしているユーザーにフォローボタンを出さない Merge pull request mastodon#99 from pixiv/autoresize_textarea autoresize textarea replace oops image 謎の clear: both; を削除 Update accounts.scss add tests Remove unused translation Merge pull request mastodon#98 from pixiv/media_aspect_ratio_change_to_16_9 media aspect ratio change to 16:9 add rel=nofollow fix character escaping in URL Merge pull request mastodon#90 from pixiv/sidekiq-statistic Merge pull request mastodon#96 from pixiv/admin_script Destroy local account from admin page Merge pull request mastodon#92 from pixiv/fix/translation_ja_modal about.termsにするとどうか? フィードバックを受けて翻訳を微調整した
|
This is the main reason that I'm not using Mastadon. Groups are a wonderful feature of GNU Social, and I would love to see them implemented on Mastadon. However, while that certainly does keep me from enjoying Mastadon, the root of the matter is that...
This, being an old and closed issue, likely doesn't get the attention that it deserves, but I know that I am not the only one that holds this view. At any rate, It would be great to see groups in Mastadon, please reconsider. |
|
Reopening, but not high priority. |
|
Coming from GNU Social I also miss groups a lot. It is a easy way to exchange messages about a specific topic without the need to follow all the people (and also get all the unrelated messages). But after thinking about it for a while I wonder why there is this arbitrary distinction between groups and hash tags? Maybe it would be better to simply add the possibility to follow hash tags, similar to Diaspora. It achieves the same but makes it probably easier to use and understand for new users. |
I agree! And @schiessle, that's #1096, if that helps at all. |
|
I think that either option (following hashtags or creating groups) is a good idea. However, groups has a potential edge in viewership/participant restriction. |
Implement highlight function.
|
I would very much like groups. I think they would help users find other people who share their interests, especially since Mastodon by design limits discoverability by not allowing full text search, and other social media platforms have been training users off hashtagging. (Twitter no longer requires a post contain the actual hashtag in order to appear in the hashtag search results.) |
|
I heard rumors that groups might come in one of the next releases. 😉
|
|
There is a fair amount of discussion on the merit of !groups on #1096 in case anybody missed the link to that issue upthread. |
|
I note that Edit: It was pointed out that #1096 is a duplicate, but I think my point still holds! #1096 has 35 👍 and #945 has 13. |
|
@Gargron Will the groups feature be discussed further before/during implementation? I'm interested in how CoCs will work, e.g. will a user of a group be subject to a group CoC as well as their instance CoC when posting to the group? |
|
My home instance in the Fediverse is a Mastodon instance and I simply want to be able to search for, see, and subscribe to Lemmy "communities" (i.e., groups) (e.g., |
This is already possible but you would use the same webfinger style as elsewhere: |
|
Just adding my voice here (echo-ing some of what's been said before). Private groups are the only reason I still have Facebook (and are the reason I hear from many that they cannot move to decentralized social media). I dropped Twitter but still have valuable private groups that I do not want to leave that are on FB. Public groups could still be valuable but I get that you get the same kind of effect with tags. The key difference is groups would be moderated by group owners whereas post tags are moderated by instance. One way to think of it is it allows an instance's moderation to be distributed to more people to allow for more self-organization - similar to Reddit. This can be done now via group=instance paradigm, but "go create your own instance and be and instance admin" isn't really practical IMO. I think this is a feature that would move Mastodon from merely a Twitter clone (which it does well enough) to a true alternative to sites like Facebook or Reddit. I guess it's a question of what the Mastodon community sees its mission as: Twitter/public feed alternative - or - Social Media that facilitates self-organization of people on it (without requiring them to create their own instance). |
I totally agree with this! Facebook groups is a great feature, especially private groups. So please please give us groups. |
|
@JamesTheAwesomeDude : What happened to your bounty on this feature ? |
|
Couldn't this group functionality be implemented through Lists? Lists already allow for replies to list only (disclaimer: haven't yet used). Add "Post to List only" as publish option. The main drawback being that you must follow a user in order to add them to a List. (Piggyback on request to open Lists to non-followed users, perhaps?) |
|
@TymeForChange no; lists are subsets of your follows, not your followers. also, work for adding groups as a separate context from timelines is in #19059 |
Well, you cannot add someone to a List unless they are following you. So, in practical terms, Lists are a subset of your Followers. |
|
incorrect; you cannot add someone to a list unless you follow them |
|
Do groups exist meanwhile or are planed? The reason is that we want region specific "subnetworks". We maybe can do this now only by unlink our network from the "universe" and create for each "group" an own instance which is then on the allow list of the other instances. But on one side we don't want to isolate the community completly, but on the other side we also want to prevent our users to get flooded by unrelated trash of other communities. Especially we don't want to get the flood of fake news and anti democratic conspiracy shit. If a user subs to a doofus that's ok, but it should not spread around our instances. Maybe groups are not neccessary, but still would be a very good start for linking the people together which need to solve specific problems. At least we need some tool to keep the community clean of absolutely unrelated internet trash. If I get the information correkt I found there is only one solution at the moment: Setup a instance for each region, link them together to a private network, introduce special tags for special problems and promote them on some way (maybe this even need a fork to change the UI, I could not find any tips for customisation) |
Ah. Well, then it's this issue: #20541 |
I think they are just recognizing actors that are labelled Group from the AP spec. Examples are accounts from https://gup.pe and https://chirp.social What is the handle of that group? |
They are indeed at *.gup.pe. |
For what it's worth, I (like others) landed here precisely because I disagree. Perhaps Mastodon only wants to be a twitter style shout out to the world style microblogging platform? If so a shame, not least given the popularity wave it's experiencing. Because not until it considers itself a social media platform and offers private and public interest groups as a way of containing conversations will it ever draw much migration from Facebook. I would love to migrate some groups from there to Mastodon. But I see nothing that maps well to the notion of Facebook Groups .... C'est la vie I guess, I'm just sayin' ... and dreaming of a fediverse that can draw Facebook users. Alas, until Facebook is obliged to support interperability at some level can I see a mass migration from it. So many are stuck the way telephone users were before the big national Telcos were broken down. All their friends are on Facebook, all the utility they get out of social media is on Facebook and so to migrate away and go it alone is a big ask, and the only way I can see it happening at all is either if Facebook is obliged (legislated to) support interoperability (like ActivityPub) or at bare minimum a decent alternative that can lure casual users away (offering groups, events, pages ...) so select groups can be convinced to make the hop together. |
As a data point, Twitter has "communities" now. |
Good to know. Just another voice in favour of closer circles, both open and closed (groups, communities, circles, hangouts heck different sites playing with different names for talking to a subset of the world of all users). Mastodon has one such differentiation, the Local and Federated views. But Local has a pretty huge overhead (is tied to hosting a whole server) with its own URL etc. It would be nice if for example on https://mastodon.au/ we could have interest groups (open or closed) that make migrating such groups from Facebook into the Fediverse much easier and easier to sell to group members. That said, I don't see Communities anywhere on Twitter right now? Is it well hidden or am I not looking in the right place? I admit I'm not a Twitter fan/user per se, just use it occasionally. |
|
Private groups would also allow for our NGO (Psychologists for Future) to use it for internal as well as external communication at the same time, which would be so helpful and alleviate a lot of technical pressure for us as non-technical people! Plus, that way it would bring even more users to the platform due to the usecase of internal communications being possible. UX-wise I would still have some questions, as of course that also would bring new challenges. But that is also a matter being discussed elsewhere, I guess? I'll happily lend my psychologist brain if that can be helpful - leisure time programmer, so I am not totally ignorant of limitations and powers of datastructures :) I don't want to pressure though, because it is hard developing open source software and I really appreciate what is possible with mastodon already, thanks a lot, @Gargron and all involved! |
|
After some research I came to the point that groups will unlikely be part of Mastodon. They concentrate on their vision of a Twitter clone. A solution to this would be only to search for another project which has that feature or to create a new project. I do currently something in between. I wish I would have more time and experience with ActivityPub. My focus now is on another project which has a server first approch and is API compatible to mastodon. I will try to make this a headless service with its own auth endpoints to bypass OAuth for the same-origin scope and also add a RPC service to it in a way that something like sending emails and ActivityPub messages can be used by other services without the need of reimplementation. The Idea is that additional logic, like groups, group chats, games, video and text blogs, podcasts, what ever, can be added as loosly coupled (micro-) services. Similar for the PWA frontend. For the basic functionality anybody can connect with a Mastodon client. The PWA is a seperate project and can also be extended, forked, new implemented... Currently most projects focus on standalone monoliths and they are not interested in extendability and easy ways for integration in existing projects or projects which want to make heavy use of additional features. That's ok for that project goals, but not for the people which don't want only a clone of something and rather create something better or hybrids of different approches. |
|
Hi, I just wrote a piece on the support of groups in Mastodon & the Fediverse. https://raphael-jolivet.name/en/blog/groups-in-mastodon-and-the-fediverse |
|
@raphaeljolivet You forgot GNU Social which has had !groups since forever. Subscribing to #tags is not nearly as powerful in terms of stitching the fediverse together. The star network structure of !groups means two otherwise unconnected instances can be linked via a !group on a third instance. #tags by comparison only propagate to instances your instance federates with directly. You also can't administer a #tag like you can a !group. Finally "banggroup" is just too great a term to pass up |
That a great article... I'm very surprise of that branch ( #19059 ), as you said, it's pretty mature. If not happening in 2022, i suppose it's will come to 2023 at that pace. Very happy to see it ! The last huge step would be to force all social network to join ActivityPub. I know France had mades somes attemps intoo this topic. But mostly, it's would be by law, provide interoperability or get domain name banned from ISP. |
|
#19059 is great work and will be a huge feature for Mastodon IF that can be completed and IF it will get released. Sadly it does not fit our requirements for groups. They need to be private (not federating) but public to all community members. Nobody outside of the community should be allowed to post, comment, etc. The alternative to this would be a participation request for federated users. A very important requirement is also to define custom forms. For example people should be forced to fill out some data before asking for advice. As a 65k+ group admin on FB I know the problems if that isn't given: The people get advice which don't fit their needs or the first 10 replies asking for more informations before giving advice. That's why I still think that it would be much better to make Mastodon more flexible, customizable and extendable instead of adding big features into the core. But that's just my opinion, others like monoliths for some reasons. Happy downvoting. ^^ |
|
I see ‘MAS-15 Groups’ as in progress on the roadmap now, so I’ll take the liberty of sharing two blog posts of mine that provide a rudimentary ‘state of groups’ report from a threadiverse perspective: https://blog.erlend.sh/transitioning-r-rust-to-the-threadiverse The most important takeaway here is the emergence of FEP-d36d for group-to-group following as a force for consolidation. I hope it will be seriously considered as a follow-up as soon as Groups has landed. |


support groups using bangtags
The text was updated successfully, but these errors were encountered: