• orclev@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Yeah, it was that last point that’s the sticking point. Like you I agree and would expect that when you post to a community you follow that communities guidelines, but since media apparently uploads to your instance not the instance hosting the community now you’re getting a 3rd party involved. If media was hosted on the same instance of the community I don’t think we’d have a problem and you wouldn’t need to worry about violating the posting guidelines of your home instance.

      Personally, while I might create a “normal” account and a porn account, I definitely don’t want to feel like I have to do that. I think you should be able to create your account in any instance you want and post to any community you want (assuming said community isn’t on an instance which has had federation blocked from your home instance) without having to worry about the content rules of your home instance. I definitely think the embedded media handling needs to have a second look given to it.

        • orclev@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          You wouldn’t want instances to automatically store media posted from other servers, because that means that as a server admin you’ll have to deal with purging things like child porn from your server because some dickhead decided to cross post their trash to your community.

          Wouldn’t you need to moderate the contents of the community anyway? Does it fundamentally change things whether the cross posting is done via posting from a different instance or by the poster just switching accounts? In either case the post is ending up in the community and you still need to moderate it. Having media stored in your home instance just makes things really awkward because now as a user I have to contend with both the server wide rules of my home instance and the rules of the community I’m posting in. I just worry we’re going to see things fracture into two nearly completely separate fediverses, there will be the NSFW adult fediverse, and then the SFW fediverse and you won’t be able to subscribe to content from one on the other.

            • orclev@lemmy.ml
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              You’re thinking about this purely from the standpoint of stopping spammers/bad actors, where as I’m trying to approach this from the standpoint of a well meaning user just trying to follow the rules. The current system does stop people from intentionally abusing the system, but it ironically can lead to people unintentionally abusing it. E.G. say I as a “normal” user with no knowledge at all of how the federation is actually implemented (not too far from the truth) decide to post into a community whose content violates the rules of my home instance (but not the instance the community is hosted out of). I would (incorrectly it seems) assume that as long as I was abiding by the rules of the community I’m posting in, that I’d have no problems, however doing so could see my account banned from my home instance.

              In our theoretical example of a lemmy server run by PornHub, if I as a user of lemmy.ml want to post contents to a community hosted on PornHubs server I feel like I probably can’t as lemmy.ml, for reasons of moderation I assume, has a site wide rule against pornographic content. If I did reasonably post in good faith believing that the community rules took precedent I would likely end up in trouble with the admins of lemmy.ml. In order to avoid this situation I feel like I’d need to make an account on the PornHub instance and treat that as my main account. That feels backwards to me.

              I can see where you’re coming from, but while the current solution makes things easy for the admins and moderators, I think it’s going to lead to a lot of confusion when/if lemmy instances that allow porn actually start showing up (I’m not aware of a single one yet). There’s also the question of text content that violates rules. If I post text content into a community in another instance that’s allowed by the rules of that community, but somehow violates the site wide rules of my home instance where does that end up? Does my home instance even know about it? It’s not stored locally I don’t believe. I presume the only way they’d become aware is if the admin/mod of the community being posted into complained.

                • orclev@lemmy.ml
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  edit-2
                  1 year ago

                  Yeah, I’m not sure there’s a good answer to be found here, but clearer messaging about exactly what the rules mean would help avoid confusion.

                  I took “no NSFW content” to mean no creating NSFW communities or posting NSFW content to any of the communities hosted there, but I had not assumed it would mean no subscribing to NSFW communities on other instances, or posting to NSFW communities on other instances. Understanding now the way that embedded media works though I’d now assume you could probably subscribe to NSFW communities on other instances, but not post to them.

                  Personally I have no problem with NSFW content, so I kind of regret signing up on lemmy.ml, but on the other hand there are no lemmy instances that currently allow NSFW content that I could sign up with, and there definitely weren’t any 2 years ago when I created this account.

                  As for self hosting, while I do have the knowledge to do so, it’s a question of motivation and priorities. I simply don’t want the headache of running a server, I’m annoyed enough as it is just keeping my home systems patched and up to date. I used to run some servers for other things, but after not even logging into one for nearly a year (yes, that’s terrible and very risky) I decided to retire them.