indieweb / indieweb/indiewebify-me
rel="in-reply-to" is deprecated
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 188
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
The section on federated comments says "When marked up with h-entry and rel=in-reply-to and/or class=u-in-reply-to, your reply can show up as a comment on the original post." The rel="in-reply-to" property is deprecated and beginners may struggle to distinguish the difference between the class and rel implementations.
I was confused when seeing the rel value. It has not been adopted nearly as much as the in-reply-to class, which is documented extensively on the wiki (https://indieweb.org/reply) and in dozens of field examples.
@tantek said on Nov. 9th 2021 "It should be dropped from that completely or maybe given a warning to stop using it" in the IndieWeb Chat, recommending instead to "use u-in-reply-to instead on the actual h-entry reply" (cite: https://chat.indieweb.org/dev/2021-11-09#bottom).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the federated comments section that mentions h-entry, rel="in-reply-to", and class="u-in-reply-to". Compare its wording with the reply guidance on the linked IndieWeb wiki and chat reference; done means the section no longer presents the deprecated rel property without the requested clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100