search

innoq / statuses

statuses
Apache License 2.0
13 stars 14 forks source link

Improve Hypermedia-Support #144

Open youngbrioche opened 9 years ago

youngbrioche commented 9 years ago

The statuses listing uses pagination but lacks <link rel="prev"> as well as <link rel="next">. Strictly for the <head> :)

aheusingfeld commented 9 years ago

we have the rel="next" on the "Next" link. We don't have a rel="prev" as luckily every browser has a back button. ;)

youngbrioche commented 9 years ago

luckily every browser

There are more potential clients that aren't browsers. What about crawlers? Google recommends to implement both link types.

mvitz commented 9 years ago

And how to get to the previous page if you followed a link to the second one?

aheusingfeld commented 9 years ago

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

And how to get to the previous page if you followed a link to the second one?

@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

mvitz commented 9 years ago

You should not assume that because you know that linking to page 2 doesn't make sense anybody else does, too. ;-)

aheusingfeld commented 9 years ago

:+1: That's why I said

But for sure you're right and I agree that we're not doing a good job in expressing this clearly