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
Merge Semantic Linkbacks into this plugin #112
Comments
|
dshanske@c23c434 - The original noted reason for removal of microformats support was the specification. The specification now notes that "When a Webmention implementation does support updating (i.e., a "Webmention update implementation"), it MUST support updating data from properties of the primary object of the source. (e.g. properties of the [h-entry] of the page)." This would be an endorsement of microformats within the plugin to a greater degree than now. The biggest issue is that the php-mf2 parser has a PHP 5.3 dependency. But the plugin could be set to degrade in the event that this occurred. The individual files could be loaded separated. I cannot see a scenario where someone would want webmentions and not at least some of Semantic Linkbacks. |
|
As this is a controversial issue, I am expressing a hope for an eventual reunification but accepting that a lot of things that might not be possible at this time would have to be addressed for this to be a reality. I suggest we keep this issue open as a discussion point. |
|
The first question is if separate comment types should be used for like, etc. The comment comment type is the equivalent of reply. |
|
TBH I think this is one of the most important improvements to make for the Webmentions plugin. This is key to how Webmentions (as a protocol, web standard, and ecosystem) are so much better designed and implemented than Pingbacks/Trackbacks etc. that the WordPress plugin by the same name should really reflect the full promise of what Webmentions do in practice on the indieweb, and more importantly what a typical user of Webmentions expects that they will do (provide actual rich reactions like comments, likes, etc. not just junky pingback links) |
|
Some reasons I think they should be merged:
|
|
@pfefferle and I discussed finally addressing this issue. This will require a new data structure as a first step and a migration function. The brainstorming for this is on the wiki at https://indieweb.org/WordPress/Data |
|
friendly nudge. could be a good project for summit! |
|
I do not think it is that easy, because I would recommend to rewrite the SL code! The actual version feels really hacky! |
|
@pfefferle Is it better to merge the code and then rewrite, or only incorporate the new non hacky version? |
|
I would prefer to not merge the code as is, because otherwise it is harder to rewrite it, without the limitations of the old structure... |
|
I will continue with pulling in pieces of infrastructure. |
|
Still seeing confused users file bugs elsewhere due to the bad UX of having these two plugins separate, eg snarfed/bridgy#1355 (comment). Hope the merge refactoring work is coming along ok! |
|
Resolved via version 5.0.0 |
I know there is a reason it was separated, but I want to discuss if that should be revisited.
The text was updated successfully, but these errors were encountered: