Pushing updates about Groups (Communities) to clients

[benparsons]

Documentation: https://drive.google.com/open?id=1GzwhGdnWWMENYOaXMFP8CD-M9ny1vznxHnNqT3I3NZI
Author: @ara4n
Date: 02/01/2018

[non-Jedi]

For anyone else still trying to figure out how groups updates work in practice, currently synapse includes a key "groups" in the /sync response that looks like this:

{'leave': {},
 'join': {},
 'invite': {'+test:thebeckmeyers.xyz': {'profile': {'avatar_url': None,
    'name': 'test'},
   'inviter': '@adam:thebeckmeyers.xyz'}}}

(note that above is copy-pasted from python-sdk, so some stuff might be off from standard json formatting)

If this is just a remnant that won't be sticking around, I'd appreciate some clarification to that effect and maybe a pointer towards how we should currently be tracking groups.

[turt2live]

I think this is largely superseded by MSC1772: Spaces

@mscbot fcp close

[mscbot]

Team member @turt2live has proposed to close this. The next step is review by the rest of the tagged people:

• @dbkr
• @uhoreg
• @turt2live
• @ara4n
• @anoadragon453
• @richvdh
• @erikjohnston
• @KitsuneRal

Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for information about what commands tagged team members can give me.

[mscbot]

🔔 This is now entering its final comment period, as per the review above. 🔔

[mscbot]

The final comment period, with a disposition to close, as per the review above, is now complete.