Aaron Parecki

Yep I just discovered that. Could just remove those particular tests...

The thing that stopped me from sending a PR for this is that the Ruby parser doesn't have the updated rules, so it's not possible to create a good test case in Mastodon for the changes. Just removing the class right now will break a bunch of tests that are expecting the name property.

Posts with no CW would end up with just a `content` property. According to the new parsing rules, those look just like normal content-only posts and sites don't see a `name` property and treat them as normal text/microblog/toot/tweet posts.

But what about posts with no CW?

A change in the Microformats parsing spec from [a few months ago](https://github.com/microformats/microformats2-parsing/issues/6) reduced the cases where parsers would auto-generate a `name` property if there wasn't one in the original markup.

Previously, when the `name` was autogenerated, people ended up having to add an explicit `name` property to the HTML in order to avoid weird broken-looking names. Now that this change is approved and implemented in a couple parsers, things are working a lot better. I believe the Ruby parser has not yet implemented this change, but it's in the Python and PHP ones.

Certainly one option is Mastodon could just remove the `p-name` class, since the newer parsers would end up seeing those posts with just the `summary` and `content` properties.

Since afaik no Microformats consumers have the concept of CW/spoiler posts yet, this does raise the issue of how to provide a good fallback behavior for consumers that don't understand spoiler posts. My thought with moving the `p-name` class to the same element as `p-summary` is that the current consumers will see it as an "article", most likely only showing the name of the article. Here's an example of how my site renders comments that have a name (whether or not there is also summary or content)


Similarly, here's what my site shows when I'm replying to a post that has a name:


If the `p-name` class is used only for the CW/spoiler preview text, then my site wouldn't show the full content in either the reply context or as a comment, which seems like the safest fallback behavior.

I read somewhere p-name is no longer necessary?

Another example where a comment that my site received is unable to be displayed well due to the mismatched name/content markup: https://aaronparecki.com/2018/07/05/14/

cf https://github.com/tootsuite/mastodon/pull/1063 and https://github.com/tootsuite/mastodon/issues/965

Here's an example of how a Microformats consumer gets an incorrect `name` value for a Mastodon post: https://aaronparecki.com/2018/07/02/7/