Why not, right?
I shipped a great bug yesterday. A big thanks to Chris Aldrich for catching that and sending me a DM today to let me know.
With all my cleverness around separating comment types for display below posts, I forgot to check for cases where there was some kind of Webmention, but no regular or reply comments. That resulted in an empty array being passed to the
comment__in argument for
get_comments(), which then resulted in every single comment! A conversation, indeed.
In the process of fixing that, I also decided to only show each section—Likes, Mentions, etc…—if that section had at least one action. This makes more sense to me than empty headings. I also added “bookmark” as an accepted type.
There are a handful of other types left via the Semantic Linkbacks plugin and I should probably decide how to manage them.
I kind of like the idea of “read” being something I see in the WordPress dashboard, but not on the front-end. I made that the case for now along with all of the RSVP, invited, watch, follow, listen, tag, and repost actions. I’ll revisit those in the future if I think of something fun to do with them. For now, I’ll still get them in my dashboard.
The idea of “favorite” has become synonymous with “like” for me when I think about it in the context of social networks. I’m going to mirror those for now and continue to think about differences. I could almost see doing the same thing with “bookmark”, but I’ll keep them separate for the time being.
Now that I’ve adjusted what reactions show up, the
get_comments_number() count is not to be trusted. Instead of displaying the number of reactions, I decided to remove the count entirely. For now, I’ll leave the “16 comments” thing alone on archive views just to confuse everyone.
At some point during the day, I was hoping for custom comment statuses in WordPress as a way to separate public and private comments in some kind of workflow. There’s an open trac ticket that’s had some traction in the past and I left some feedback. I was also happy to see a bit of recent traffic on the custom comment types ticket. I’m not sure how I want to chime in yet, but I think they would be very useful.
There is a part of me that things comments need to be approached entirely different. The first thing I would consider doing is creating a
wp_comment_author table that tracks unique authors in some way. I’ve only thought through the good parts of that and not the bad, so it may be a ridiculous idea. But I would like to do things like “mark author as spam” and have that combination of name/email/website never appear again. To do that in the current data structure, you’d have to store data in strange ways to try and match things when a new comment comes in.
I’ve been working on a ridiculous plugin, the Self Sustaining Spam Stopper, to see if every day spam blocking is possible without the use of a centralized service and without having to spend a lot of time. It’s already catching most spam, though some tooling around marking words, phrases, and paragraphs as “always spam” from the WordPress admin will be much more interesting.
Things to dig into next:
- All of these actions are great in the Semantic Linkbacks plugin, but I’ve completely lost track of where they’re standardized. I thought I remembered reading the Webmention spec the other day and not seeing them there. I need to investigate a little bit more and see how they’re created and if there are more specific intentions.
- I’m not completely sure yet, but I don’t think the “approve & whitelist” option via the Webmention plugin is working for me. I’m still finding myself approving things received from the allowed list of domains. I need to verify / troubleshoot this.
- Propose that “approve & whitelist” be changed to something like “approve & allowlist” or “always allow”.
- I think I’d like a “replies” post type I can use to reply to comments on other peoples’ sites. I want to keep my main feed as standard posts without generating a kind of firehose.
- I may extend on that to my own “likes” so that I can notify people when I like their posts.
- And I want to make sure I have a clever way of RSVPing to things. I’m headed to the IndieWeb Summit in June and sending an RSVP from this site will be fun. I’m not even linking to it yet just in case it accidentally handles the RSVP for me. 😂
Responses and reactions
The approve and whitelist functionality in webmentions broke. It does need to be renamed, but the issue at the moment has to be traced through execution of both plugins to figure out why it is causing issues. Since some functionality is being moved from one plugin to the other, it is waiting on that. If you update a webmention it does work, but it isn’t triggering on initial creation.
I am eager to see custom comment types and statuses…I’ve been following those tickets since the beginning
Good to hear! I'll dig for the problem in a different way now. :)
I opened an issue on the Webmentions plugin, I'm happy to start helping with that transition and can spend some time focused on why things aren't working as well. I'll take a look at some of the other PRs to get a bit familiar.
I have a hope that we can do some cool newer things with comments, though I think the focus will remain on Gutenberg for the long-near-term. I'll admit not actually diving into things to see how hacky I can get yet, but I'm reaching that point.
Help is always appreciated.
I concur on the "approve & always allow" phrasing.
The only requirement for your mention to be recognized is a link to this post in your post's content. You can update or delete your post and then re-submit the URL in the form to update or remove your response from this page.
Learn more about Webmentions.