Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publicize: Store the syndicated URLs on the local site #7359

Open
kraftbj opened this issue Jun 18, 2017 · 9 comments

Comments

Projects
None yet
3 participants
@kraftbj
Copy link
Contributor

commented Jun 18, 2017

After Publicize has processed a post, let's pass the URLs on social media back to the local site. It is already stored in meta on wp.com, so would need to update Publicize to insert post meta after success and Jetpack to be able to receive it.

This could help tie into indieweb setups that utilize syndicated URLs for webmentions and whatnot.

@kraftbj

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2017

Added bonus: Could update the Publicize metabox to provide disabled checkboxes on which social media services a post was Pub'd to. Currently, this is a gap between WP.com and Jetpack.

@kraftbj kraftbj self-assigned this Jun 18, 2017

@kraftbj

This comment has been minimized.

Copy link
Contributor Author

commented Jun 19, 2017

Talking through this more, my suggestion would be:

  1. Sync this data to the same post meta fields that we use on WP.com, with it "frozen" on WP.com so the local site can't override that data on the WP.com side.
  2. Plugins could listen for adding that post meta and grab it.
  3. We add a 3rd-party hook to support Syndicated Links, which is the plugin suggested by the IndieWeb community, or at least work with the developer to make sure we're on the same page.
@kraftbj

This comment has been minimized.

Copy link
Contributor Author

commented Jun 21, 2017

The post meta currently in use on WP.com may be going away at some point in the future (deferring to the publicize_actions section of the activity log), but the publicize_save_published_action hook on WP.com could be used to trigger a push to JP of the URL or we could access the activity log via an API if needed. (h/t @artpi for catching me up on the current status and direction of Publicize data storage).

@dshanske

This comment has been minimized.

Copy link

commented Jun 21, 2017

I am the developer of Syndication Links. It is a relatively simple plugin. Happy to volunteer or participate.

@dshanske

This comment has been minimized.

Copy link

commented Jan 17, 2018

This has been a while...has there been any movement on this?

@kraftbj

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2018

@dshanske No, not yet.

@stale

This comment has been minimized.

Copy link

commented Jul 24, 2018

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Jul 24, 2018

@dshanske

This comment has been minimized.

Copy link

commented Jan 31, 2019

Checking in on this issue

@lancewillett

This comment has been minimized.

Copy link
Member

commented Apr 9, 2019

User vote on this thread: https://boffosocko.com/2019/03/28/55747397/

I’m still surprised they don’t return the URLs of where the content got shared for showing on the page with plugins like Syndication Links: https://wordpress.org/plugins/syndication-links/

Hat tip @ryanboren

@stale stale bot removed the [Status] Stale label Apr 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.