Kegan Dougal

+1 : This takes forever to run. Doesn't seem to be using max CPU when it's doing this either.

This library does not currently support SAF yet, so make sure your image URIs are compliant if you're running on Kit Kat. https://developer.android.com/guide/topics/providers/document-provider.html

Author of sliding sync here: yes you would be able to use sliding sync for this use case, however sliding sync is a long term project, and won't help you...

[MSC 3079: Low Bandwidth CS API](https://github.com/matrix-org/matrix-doc/pull/3079) may be an alternative to this as it makes it viable to rely on `/sync` for push notifications directly as it is made bandwidth...

Indeed, they can be complementary but at the cost of an increased API surface. If you don't trust your push provider, that has knock on concerns though. Malicious push providers...

This MSC doesn't seem to talk about sync filters at all. Sync filters are used by clients to filter out unrender-able events, which would be broken by this MSC due...

I like this and it's easy to implement - will get to work on a Dendrite impl (though I'm reluctant to add the download endpoint)

An extension to [MSC 3079](https://github.com/matrix-org/matrix-doc/pull/3079) to support WebSockets may be an alternative to this proposal. It requires more client and server work, but saves far more bandwidth than this proposal...

https://github.com/UZ-SLAMLab/ORB_SLAM3/blob/master/Examples/Monocular/mono_euroc.cc#L83 The last arg needs to be `true` as that sets `bUseViewer` - https://github.com/UZ-SLAMLab/ORB_SLAM3/blob/master/src/System.cc#L42

Good idea, I'll look into this. Thanks!