I occasionally come across content in my feed that I think would be of interest to one of the small communities that I participate in. Think photo or article, not something personal. Is it appropriate for me to crosspost the content? Without asking the OP? What about if I ask but the OP never responds?

Thanks in advance for your thoughts.

    • ℕ𝕖𝕞𝕠@slrpnk.net
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Linking between instances is kinda weird right now, apparently. There’s no good way to link to a specific post in a way that’s accessible for users across instances.

      • OldFartPhil@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        I would be linking to the thread. Does the cross-post button not work as expected?

        • can
          link
          fedilink
          English
          arrow-up
          7
          ·
          1 year ago

          Accessible as in viewable. But I can’t comment.

            • JackbyDev@programming.dev
              link
              fedilink
              English
              arrow-up
              7
              ·
              edit-2
              1 year ago

              No, it’s not a federation issue. What we need is some syntax to link to posts/comments in an instance agnostic way. When you click something like [email protected] your UI will take you to your instance’s version of it. Clicking a URL will take you to that URL always. As expected, post A in community X hosted on instance blah will have a different URL than post A in community X viewed from instance foo. You can share a URL to the actual post on its actual home instance or you could share a URL to your instance’s view of the post. That second one is useful to you and members of your instance but not members from any other instance.

              Short of your UI intercepting and redirecting URLs (a very bad thing to do in my opinion, links should go where they say they go without interference) this cannot be solved with URLs. That’s why we need some way to specify something like ! community@instance/post.

              A big caveat is that I mean HTTP URLs. If there was a custom URL scheme like lemmy: then the rules can be different.