Improve Hypermedia-Support #144
Comments
|
we have the |
There are more potential clients that aren't browsers. What about crawlers? Google recommends to implement both link types. |
|
And how to get to the previous page if you followed a link to the second one? |
|
Talking about crawlers: crawlers are not supposed to index the timeline/ listing pages at all! They should only use the links on those pages to index the page of a specific update/ post as this is the real content of the application. But for sure you're right and I agree that we're not doing a good job in expressing this clearly and should therefore add correct semantic meaning to the content! It'd probably make sense to look into
@mvitz I'm not sure I get your question. What would be the use-case of a linking to page 3 of the timeline? The contained posts changes over the time which means, you will probably not get the same content if you come back at a later point in time. That's why I said a crawler should only index permanent links like e.g. a specific update (which now contains the whole conversation). /cc @tloist |
|
You should not assume that because you know that linking to page 2 doesn't make sense anybody else does, too. ;-) |
|
👍 That's why I said
|
The statuses listing uses pagination but lacks
<link rel="prev">as well as<link rel="next">. Strictly for the<head>:)The text was updated successfully, but these errors were encountered: