• Draghetta@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    And what’s stopping these people and these instances from spreading that content using just the publicly available link? Instead of just clicking “share” they’ll have to open an anonymous browser window and copy paste the link from there, the horror!

    • aroom@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      11 months ago

      define these people. define these instances. etc etc

      what’s your point? anyone can do a screen shot and share it too.

      if you want to have a conversation about the content of my post, please keep it on topic : without authorised fetch and a domain blocked at the instance level, the content is pushed.

      if you have technical knowledge to add to this or can correct me about the protocol I’m glad to hear it. if not I’m not interested.

      • Draghetta@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        That was exactly my point. Blocking instances because “that way my content can’t be seen there” doesn’t make sense, because it’s trivial to bypass it. Yes, even a screenshot will do the job if nothing else, so why talk about protocols in the first place?

        Somebody (maybe you maybe not, can’t check while replying) said that blocking instances was useful so that “my content doesn’t get seen / shared / pushed / etc to people and instances I don’t want”. That doesn’t make sense because of the line above. If you need clarification on who are those people and what are those instances ask them, not me.

        I hope I’m somehow conveying my message. If there is a subtlety in the subject that I didn’t catch feel free to help me understand.