Add recommendations for mobile clients

[agx]

This came out of a discussion at https://matrix.to/#/!XXSJTvRPInupfUgQVb:matrix.org/$IUx1flZV7iLWIviEeJWrmIw8LHgv4DhKGDKnO1hU688?via=pixie.town&via=matrix.org&via=element.io

When looking into adding UnifiedPush support to a client I was looking around for RFC style "Best Comon Practice" implementation hints but couldn't find any. Maybe it makes sense to add something to the documentation? I couldn't find a more sensible place than the spec if there is one please point me to it?

Pull Request Checklist

• Pull request includes a changelog file (left out as this repo maybe isn't the right location to add this?)
• Pull request includes a sign off
• Pull request is classified as 'other changes'

[anoadragon453]

I think this may go better under https://spec.matrix.org/v1.11/client-server-api/#receiving-notifications.

@matrix-org/rust could I confirm whether this is the best practice for mobile developers to receive (non-)encrypted events?

[anoadragon453]

Suggested change

	- Use [push notifications][/client-server-api##push-notifications] to get notified about new events
	- Use [push notifications][/client-server-api#push-notifications] to get notified about new events

[anoadragon453]

Suggested change

	- Fetch the events indicted in the push notifications via the ``GET /rooms/{roomId}/event/{eventId}`` API call
	- Fetch the events included in the push notifications via the ``GET /rooms/{roomId}/event/{eventId}`` API call

[anoadragon453]

Also, could you linkify GET /rooms/{roomId}/event/{eventId}? Likewise with /sync?

[bnjbvr]

@matrix-org/rust could I confirm whether this is the best practice for mobile developers to receive (non-)encrypted events?

Yep, something like this. For what it's worth, instead of using /context or /event for retrieving the event, we're doing a limited sliding sync, because the two former endpoints don't work for stripped events (coming from invited rooms). And if the event was encrypted, we're indeed trying to run a sliding sync limited to the to-device and encryption extensions; this may change with the new evolution of the sliding sync protocol.