nemomobile/buteo-sync-plugins-social

buteo-sync-plugins-social's Issues

Remove dead code related to multi-account support

There is currently a significant amount of dead code in the repository, which is left over from historical support for multiple accounts per sync profile. We ported to "per-account sync profile" support a while ago, and should remove the "multi-account-isms" from the code.

EG:

https://github.com/nemomobile/buteo-sync-plugins-social/blob/master/src/common/socialnetworksyncadaptor.cpp#L88
It should not be possible to trigger the template (ie, non-per-account profile) any more.

https://github.com/nemomobile/buteo-sync-plugins-social/blob/master/src/common/socialnetworksyncadaptor.cpp#L119
This function should probably only be used in "exceptional" circumstances, as in the common case, a given per-account profile will be triggered (either for sync or for cleanup/removal) separately.

https://github.com/nemomobile/buteo-sync-plugins-social/blob/master/src/google/googledatatypesyncadaptor.cpp#L76
That comment is wrong, as "all-account" syncs are no longer supported.

Similarly, anywhere were we pass around a "QList accountIds" should probably be refactored to taking just a single account id.

Google + browsing support

As with Facebook, it can be interesting to get Google + feed, photos and contacts. As Google + API is read only, it won't be possible to have post though.

Instagram support

Instagram support, at least for photos browsing could be nice. Photo uploading is not allowed, so we cannot support sharing feature.

Facebook API 2.0 support

With Facebook API 2.0 coming soon, the buteo-sync plugins will probably need to be reworked:

• Contact sync will not work reliably anymore, as graph API will only show friends that use the application.
• Posts won't work anymore either, as FQL will be deprecated. We can fallback to the graph API but posts from graph API are not as nice as thos from FQL.

There might be other parts that I didn't looked at, like some API breakage with events, images or notifications. Comment this issue if you have more information about it.

The most critical part that need to be worked is contacts support. Should it be dropped for API 2.0 or should we just keep it as a limited version of contacts sync ?

Make twitter limit configurable

Quote from #4: I suggest we rework this patch and make it read the limit from a configuration file and set the limit to 10 by default. That way anyone interested in raising it can do it easily via a simple configuration.

Use the Buteo::Logger macros in trace.h

Currently, sociald has its own runtime logging macros.
Recently, Buteo gained its own runtime logging macros (rather than build-time), and so we should now port trace.h over to using those.

https://github.com/nemomobile/buteo-sync-plugins-social/blob/master/src/common/trace.h#L31

After porting, the environment variable would be MSYNCD_LOGGING_LEVEL rather than SOCIALD_LOGGING_LEVEL, and the most-verbose level for MSYNCD is 9 rather than 3.

Support Google's Other calendars

Currently only "My calendars" are synced and shown within the Calendar application in the "Manage calendar" meny option.

Please add sync for "Other calendars".

See https://developers.google.com/google-apps/calendar/concepts#calendarLists_resource for the "difference" between "My" and "Other" calendars. Other calendars are ones which are subscribed from another person or other things, like holidays.

(also, I'm not sure if this is the correct project to add this issue, if not please direct me to the correct one).