Join GitHub today
Syndication URL returned for possible display? #4
If Mastodon returns the permalink for the syndicated copy of the post, it would be nice if this plugin would store/provide that data so that plugins like https://github.com/dshanske/syndication-links could potentially display where copies of the post went.
A sample of the UI can be seen here: http://boffosocko.com/2017/10/25/testing-syndication-to-mastodon-from-wordpress/
I read now for about half an hour about syndication but still don't get it.
Would it help, if the plugin displays the Post URL? So that in the "Successfully posted" message, also the URL to the new created Mastodon Post is included?
Thanks for help,
referenced this issue
Jan 24, 2018
Thanks @L1am0, I'm suspecting that this should work to help close the loop.
Since I would guess you'd use it all and for a clearer explanation for the reasons for this, it might help to look at the similar but more fully fleshed out and working birdsite (aka Twitter) example which goes like this:
The end result is that I own all the content I publish on my WordPress site and simultaneously I can cross post to other social silos which can now communicate back to my original posts. In the end, ideally, a full transcript of the conversation that happens around my content ends up on my website.
As an example, you can look at this post: The Facebook Algorithm Mom Problem which I syndicated to several other locations. You'll see many of the responses to my WP post were not posted to my native comment section, but were instead backfed from Twitter, Facebook, etc. via Brid.gy and or other sites which support Webmention. In the end, the majority of the conversation is stored on my site. Sadly none of it is built out for Hacker News or the volume would be double, though by clicking on the Hacker News Icon in the syndicated section will allow one to see that portion of the conversation (at least as long as that site stays up).
A large group of people (many under the banners of IndieWeb, the Social Group of the W3C, and surely many other independents) are working at better federating pieces of the internet so that websites can talk to each other in a more coordinated and decentralized fashion. Your fix should help close out half of 3 on the list, we'll just need to finish out 4 which is documented here.
I'll also note that the creator of Bridgy also has a FedBridgy service which is working at the entirety of the problem from a different perspective leveraging the built in plumbing of Mastodon. Another separate alternative would be for Mastodon to support sending/receiving Webmentions natively.
Hopefully this "short" description helps. If you're curious about more, I'm happy to help point you to resources for additional details and/or help.
Thanks for building Mastodon Autopost!!