I’m not 100% certain that’s the cause, but my testing so far suggests it’s probably that. Basically if you have a URL that doesn’t point to the original resource, but some copy of it on another instance, it won’t resolve. So far I’ve only tested that on a third instance, but from my experience with the same bug on pleroma, this will occur even if you do it on the resource’s origin instance. (fse post referred to from poa.st can’t be resolved on fse.) As example: https://lemmy.perthchat.org/api/v3/resolve_object?q=https://lemmy.ml/post/472799. It’s possible that this is actually just a federation block, but https://beehaw.org/post/125367/comment/32382 also fails, (and fetching that post works,) which I’m pretty sure isn’t.

  • @[email protected]OP
    2•2 years ago

    Why do you open Lemmy in your browser I don’t.

    you can directly connect with your client to the API of any instance The complexity is necessary for this. When given a link, I need to translate it into an API link so I can load the object and grab the ap_id.

    If that isnt rendered properly in your browser Lynx. I’ve detailed the problem in the matrix room, basically for some reason it’s in a title element so lynx correctly sets the page title to “fedilink” 100 times.

    • @[email protected]OP
      1•2 years ago

      Thinking about this more, I realised it’s impossible: The link might not even be a lemmy link at all! How am I meant to guess the other node’s API? I’d use federation API, I guess, which I still haven’t found nice docs for.

    • @[email protected]
      1•2 years ago

      You are wrong, it uses the title attribute which is valid html, and not the title element. Maybe Lynx doesnt support that attribute on a elements, I dont know.

      Btw you need to add a newline after each quote so that its rendered correctly as markdown.