Skip to content
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

Bridging group membership with 3rd party group sources #3801

Closed
benparsons opened this issue May 10, 2018 · 7 comments
Closed

Bridging group membership with 3rd party group sources #3801

benparsons opened this issue May 10, 2018 · 7 comments
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal rejected A proposal which has been rejected for inclusion in the spec

Comments

@benparsons
Copy link
Member

benparsons commented May 10, 2018

Documentation: https://docs.google.com/document/d/1Nyk3Jf9BF0T2jHbeOV4DltazY5a3eP2meovSnMKDsxU/edit#heading=h.aienm7wdvf4q
Author: @lukebarnard1
Date: 15/11/2017

@ara4n ara4n added the proposal A matrix spec change proposal label May 15, 2018
@richvdh
Copy link
Member

richvdh commented Nov 5, 2018

Is this abandoned, or is it related to the way that the IRC bridge does the +irc group? @Half-Shot, any ideas?

@Half-Shot
Copy link
Contributor

I've not seen this before, but it looks like we use 'Option C' for applying a group to a userid namespace (@freenode_.* is bridged to +freenode:matrix.org). Synapse supports this. Notably, the bridges have no awareness of this because it's a registration file option for synapse.

This is something that needs to be specced for the appservice registration file

@richvdh
Copy link
Member

richvdh commented Nov 7, 2018

ok; it sounds like this is a thing that doesn't even affect the Matrix protocol, then. Accordingly I'm not sure this even qualifies as an MSC?

@Half-Shot
Copy link
Contributor

Half-Shot commented Nov 7, 2018

It's definitely a protocol thing, since the AS spec defines the format of the registration file. Whether it's an MSC thing though is up to @anoadragon453 I guess.

@anoadragon453
Copy link
Member

If this would just constitute a change to reg files, then that is more of an implementation/Synapse-specific item then a protocol change, so if that's the case then I do not think it should be an MSC.

However, we should probably refactor the spec on specifying options for appservices, by saying there are any number of ways it can be done, here is how Synapse does it, and link to a doc in the Synapse repo.

In the long term, we may be able to eliminate registration files altogether, which would help standardize appservices across every homeserver. I believe including the registration file in the current spec was in an effort to maintain standardization across home servers until a cleaner solution is found.

@turt2live
Copy link
Member

re: changing registration files. https://github.com/matrix-org/matrix-doc/issues/1309 tries to propose a way to have a standard API, although the options included in the request are relatively implementation specific.

@turt2live turt2live added the kind:feature MSC for not-core and not-maintenance stuff label Apr 21, 2020
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ara4n ara4n transferred this issue from matrix-org/matrix-spec May 9, 2022
@turt2live
Copy link
Member

Closing as groups were effectively rejected from the spec. This MSC appears to need significant re-work for Spaces.

@turt2live turt2live added the rejected A proposal which has been rejected for inclusion in the spec label Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal rejected A proposal which has been rejected for inclusion in the spec
Projects
None yet
Development

No branches or pull requests

6 participants