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

Add native support for exotic webmentions #40

Closed
peterwilsoncc opened this issue Dec 18, 2014 · 9 comments
Closed

Add native support for exotic webmentions #40

peterwilsoncc opened this issue Dec 18, 2014 · 9 comments

Comments

@peterwilsoncc
Copy link

Follow up to #22.

Support webmentions natively on the following page types:

  • Blog listing (is_home)
  • Archive pages (is_archive)
    • Author
    • Date
    • taxonomies (categories, tags, etc)
    • custom post type full archives

Archives could be considered a single page, even though they can span multiple pages.

Implementation brain storming:

  • Create unlisted custom post type to store mentions against, webmention_exotic?
  • home page post is created on activating the plugin
  • archives, etc have the custom post created on receiving the first web mention
  • Using the standard comment command will need a little work as the first thing it does is check it's on a singular
  • themes would need to be modified to support it, plugin doesn't assume, add_theme_support( 'exotic-webmentions') could be suitable
@singpolyma
Copy link
Contributor

at least mentions on homepage and author pages would be nice.

@dshanske
Copy link
Collaborator

We can also extend the existing support for setting a default page id to be a bit more complex as a simpler measure.

@dshanske
Copy link
Collaborator

There was an idea proposed of having a separate endpoint for these pages that is intriguing.

@dshanske
Copy link
Collaborator

dshanske commented Feb 6, 2017

I think that the recent move of the filter outside the receiver so that it can be called by an external function is the best that will be done for the foreseeable future. I have an idea for an extension that would create a hidden custom post type to store comments for exotic pages. But for now, I would suggest closing this.

@pfefferle
Copy link
Owner

should this still be part of the core plugin?

@gRegorLove
Copy link

I ran into this when manually sending a homepage webmention to @snarfed:
curl -i -d source=https://gregorlove.com/2017/04/snarfed.org-can-you-help-with/ -d target=https://snarfed.org/ https://snarfed.org/wp-json/webmention/1.0/endpoint

Response:
{"code":"source_equals_target","message":"Target and source cannot direct to the same resource","data":{"status":400}}

@tantek
Copy link

tantek commented Jun 7, 2017

This sounds like a multi-part issue that should be broken out into individual issues that have specific use-cases that justify them, and then close this one.

E.g.

What are the use-cases for sending (and receiving) webmentions to archive pages?

@dshanske
Copy link
Collaborator

We have homepage mention support as a feature now. @peterwilsoncc Would you weigh in on original intent, otherwise maybe we should close this.

@peterwilsoncc
Copy link
Author

@dshanske happy for it to be closed off. I can't think of a suitable use case for including it on archive pages.

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

No branches or pull requests

6 participants