Quick note that uploading and extracting from ZIP files doesn't currently trigger any syndication. It should do ideally.

Similarly, any scheduled actions (calendar and news) don't trigger any syndication. This issue is documented in tut_facebook, so people will know to workaround it - so that note needs removing.

The above affects:
- Syndication (the main issue here)
- Upload syndication (or whatever the new cloud filesystem implementation is called)
- Activities

I had a look at some of the Open Source social networks. A couple stand out, but are still very obscure. There may be some interest here given the audience is much more technical so may have more affinity with OSS.

Diaspora 1/500th of Twitter
minds.com 1/150th of Twitter

This note in the documentation will need updating once we can syndicate out to Vimeo:
"install the [tt]gallery_syndication[/tt] addon, to automatically use YouTube as a transcoder."
This is because we're trying not to preference Google too much on the platform, listing alternatives where available.

Look at Apple's new sign on button:
https://thenextweb.com/apple/2019/06/03/apple-introduces-privacy-focused-sign-in-with-apple-button-for-sites-and-apps/

I am wondering if it might be better to rip out some of the syndication stuff from Composr, and instead have third-party systems do syndicating by looking at RSS (along with possibly something like RSS-Cloud or whatever).

Why have Composr integration with X services, and maintain all that, when it can just integrate with a single syndication standard?

The Hybridauth library (which in v11 we've integrated for login) provides some of the functionality we need. I wonder if we can improve Hybridauth rather than adding a lot of stuff directly to Composr.

https://hybridauth.github.io/developer-ref-user-activity.html
https://hybridauth.github.io/developer-ref-user-status.html

I've made big headway towards this issue, using Hybridauth (as indicated in my last comment).

Hybridauth is getting a new API, "Atom API" - which allows atom-feed like data to be pulled and pushed from Hybridauth providers that implement it.
I have it implemented for Facebook, Twitter, and Instagram (Instagram is read-only though due to FB restrictions on non-business accounts).
[Assuming they accept my pull request, which I am confident they will]

Composr's Hybridauth addon then integrates with the Atom API.

And Composr's activities API has been improved and renamed to syndication. The syndication API allows syndication of both content and of activities by any addons that choose to implement it.

Hybridauth, and the activity_feed addon, both implement the syndication API.

The activity_feed addon now uses Hybridauth for syndication activity content, rather than having its own Twitter and Facebook implementations. Meaning it can syndicate to anywhere Hybridauth can.
To clarify, the flow for this is:
Composr -> Syndication API -> activity_feed -> Hybridauth Atom API -> Hybridauth -> Social media networks..

I also intend to fold the old gallery_syndication API so that we truly just have one Composr syndication API, rather than a mess of different implementations that we had before.

Various issues we've had with the old activity_feed implementation are improved. For example, scheduled content can now be syndicated, as well as gallery content imported from Zip files.

The nice thing about building around Hybridauth is that we avoid having to take responsibility for adding all kinds of third party integrations directly into Composr. The Hybridauth project can do that, and we can contribute to that project ALONGSIDE OTHERS WHO ALREADY DO. We're expanding the scope of Hybridauth beyond mostly a system for login buttons into a major PHP social network integration library that hasn't existed yet.

To that end, I don't have any plans to implement into Hybridauth the long tail of different social networks identified in this issue and our tracking spreadsheet. Instead I will bring these suggestions to the Hybridauth project, and if people want to contribute/sponsor that via Hybridauth, great. It doesn't all need to be directly under our own umbrella. And this absolves us from the need to be a gatekeeper on what social networks are valid/reputable.

I have removed/deconsidered any functionality revolving around users syndicating content to their personal feeds. This isn't a recommended thing nowadays, which is good (it's spammy and bloated).
I have dropped the idea of trying to cross-post forum posts and comments across mediums as it wouldn't work well and would be messy.

I plan for us later to also build a new PHP filesystem wrapper around the Hybridauth Atom API too - for integration with things like Dropbox, Amazon S3, and so on. This is issue #3147. However, at this point I want to completely separate any discussion of that and put it in its own corner, for version 12, which should include many Cloud improvements to Composr.

All-in-all, things are now streamlined and pointing in the right way, a lot of progress is made.