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

Publish to Wordpress comments and likes #271

Open
kylewm opened this issue Aug 28, 2014 · 3 comments
Open

Publish to Wordpress comments and likes #271

kylewm opened this issue Aug 28, 2014 · 3 comments
Labels

Comments

@kylewm
Copy link
Contributor

kylewm commented Aug 28, 2014

Companion issue to #270, Publish support to a wordpress blog's comments. "Suggested" by @tantek in http://indiewebcamp.com/irc/2014-08-27/line/1409163311923

@tantek
Copy link
Contributor

tantek commented Aug 28, 2014

Would this be different for Bridgy Publishing a reply to a wordpress.com blog post vs. Bridgy Publishing a reply to a "generic" WordPress install on some other site? Should this be two issues?

@snarfed
Copy link
Owner

snarfed commented Aug 28, 2014

good question! no, not different. bridgy technically currently supports both wp.com and self-hosted WP sites (with jetpack) using the same code. it detects and discourages self-hosted users, though, because the experience is much better if you use pfefferle's indieweb plugins instead.

however, it definitely makes sense to support publishing comments to both, and the code will be the same.

@snarfed snarfed removed the maybe label Sep 4, 2014
@snarfed snarfed changed the title Publish to Wordpress comments Publish to Wordpress comments and likes Jan 12, 2015
@snarfed snarfed added new silo and removed publish labels Nov 2, 2015
@snarfed
Copy link
Owner

snarfed commented Dec 8, 2015

if anyone's interested in tackling this, i've written up comprehensive instructions on how to add a new silo to bridgy. feel free to jump in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants