3 ms·

I don't see any image when I click that link. The only things I see are a login box, some links and an empty "conversation" panel

ColinWright 4y ago
Ah ... HN is doing it's usual thing of trying to find a canonical URL, and not posting the URL actually submitted. I submitted this one: https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665... Does that work for you? A more comprehensive comment along with the original content can be found here: https://news.ycombinator.com/item?id=32949695 https://news.ycombinator.com/item?id=32949695
- dang 4y ago
  The issue in this case is not a canonical URL but rather that https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665... redirects to https://retr0.id/notice/ANqlvFZD1eIqjmRiFc https://retr0.id/notice/ANqlvFZD1eIqjmRiFc. Our software has followed the redirect. This seems correct? I wonder if something has changed since you posted this?
  - ColinWright 4y ago
    The first of those (https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665...) does not redirect when I load it in my browser. The link we have in the submission is now behaving differently from how it behaved when I first submitted it. Certainly when I first submitted it, the URL it got changed to loaded to, as dark-star describes, a login box, some links and an empty "conversation" panel. Next time something like this happens I'll document and include screenshots. It's impossible to reconstruct or recreate. Doesn't really matter, no one has upvoted it. Whether that's because (a) people didn't see it, (b) people don't care, or (c) people don't realise how amazing this is, is anyone's guess.
    - pvg 4y ago
      It might be doing something with user agents or you have a funny browser but it's a straight redirect otherwise: curl -i https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 HTTP/2 302
      - ColinWright 4y ago
        But the point here, I think, is that when I first submitted link A it was changed to link B, and then a commenter noted that link B took you to a login page. Then subsequently link C (which may or may not be the same as link B) works as expected. Too late to track down exactly what happened, I'll make more detailed notes next time.
        pvg 4y ago
        Right but I think your theory of the case is backwards - it's not something clever or complicated HN is doing, the too-clever-by-half and weird things seem to come from mastodon/pleroma. The original link leads to two separate redirects and then ends up on a very dynamic, js-heavy page which could have easily screwed up and not displayed fully for that other commenter. In fact, if you look at it in the Chrome debugger, the first warning it gives you is 'fix your code to not depend on navigator.userAgent', which it apparently does. The share/link thing on that page is the final link itself so the real oddity is the original link. Maybe you remember where you got it because it's a strange one - it's a double-redirect to a shorter and more direct link, sort of like using one of those jokey URL longeners (elongators?).

ColinWright 4y ago

Ah ... HN is doing it's usual thing of trying to find a canonical URL, and not posting the URL actually submitted. I submitted this one: https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665... Does that work for you? A more comprehensive comment along with the original content can be found here: https://news.ycombinator.com/item?id=32949695 https://news.ycombinator.com/item?id=32949695

dang 4y ago
The issue in this case is not a canonical URL but rather that https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665... redirects to https://retr0.id/notice/ANqlvFZD1eIqjmRiFc https://retr0.id/notice/ANqlvFZD1eIqjmRiFc. Our software has followed the redirect. This seems correct? I wonder if something has changed since you posted this?
- ColinWright 4y ago
  The first of those (https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665...) does not redirect when I load it in my browser. The link we have in the submission is now behaving differently from how it behaved when I first submitted it. Certainly when I first submitted it, the URL it got changed to loaded to, as dark-star describes, a login box, some links and an empty "conversation" panel. Next time something like this happens I'll document and include screenshots. It's impossible to reconstruct or recreate. Doesn't really matter, no one has upvoted it. Whether that's because (a) people didn't see it, (b) people don't care, or (c) people don't realise how amazing this is, is anyone's guess.
  - pvg 4y ago
    It might be doing something with user agents or you have a funny browser but it's a straight redirect otherwise: curl -i https://mathstodon.xyz/web/@retr0id@retr0.id/109046752062665710 HTTP/2 302
    - ColinWright 4y ago
      But the point here, I think, is that when I first submitted link A it was changed to link B, and then a commenter noted that link B took you to a login page. Then subsequently link C (which may or may not be the same as link B) works as expected. Too late to track down exactly what happened, I'll make more detailed notes next time.
      - pvg 4y ago
        Right but I think your theory of the case is backwards - it's not something clever or complicated HN is doing, the too-clever-by-half and weird things seem to come from mastodon/pleroma. The original link leads to two separate redirects and then ends up on a very dynamic, js-heavy page which could have easily screwed up and not displayed fully for that other commenter. In fact, if you look at it in the Chrome debugger, the first warning it gives you is 'fix your code to not depend on navigator.userAgent', which it apparently does. The share/link thing on that page is the final link itself so the real oddity is the original link. Maybe you remember where you got it because it's a strange one - it's a double-redirect to a shorter and more direct link, sort of like using one of those jokey URL longeners (elongators?).