Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
We Distribute
  1. Home
  2. Technical Discussion
  3. RE: https://neuromatch.social/@jonny/115343246885448739

RE: https://neuromatch.social/@jonny/115343246885448739

Scheduled Pinned Locked Moved Technical Discussion
fep1580fedidevmoveallposts
21 Posts 6 Posters 659 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • tokyo_0@mas.toT tokyo_0@mas.to

    @jonny .... Really, if a target instance isn't going to accept a user's content that should be flagged at the start, not once the account has been migrated but the moderator is later considering whether to accept the content as well. (Am I misunderstanding the proposed sequence of events?)

    In general, while I appreciate there needs to be a way to prevent abuse and accommodate admin's concerns about problem content, admins are a big part of why this feature doesn't exist, and I'm concerned ...

    tokyo_0@mas.toT This user is from outside of this forum
    tokyo_0@mas.toT This user is from outside of this forum
    tokyo_0@mas.to
    wrote on last edited by
    #12

    @jonny ... giving them the ability to accept only part of people's content and/or make that decision after the user has otherwise migrated is going to empower them to basically torpedo what you're trying to do, by causing bad experiences for users (whether or not intentionally), demanding the ability to moderate and then not being willing to handle the moderation traffic, or just hindering people's ability to move their content. ...

    tokyo_0@mas.toT 1 Reply Last reply
    0
    • tokyo_0@mas.toT tokyo_0@mas.to

      @jonny ... giving them the ability to accept only part of people's content and/or make that decision after the user has otherwise migrated is going to empower them to basically torpedo what you're trying to do, by causing bad experiences for users (whether or not intentionally), demanding the ability to moderate and then not being willing to handle the moderation traffic, or just hindering people's ability to move their content. ...

      tokyo_0@mas.toT This user is from outside of this forum
      tokyo_0@mas.toT This user is from outside of this forum
      tokyo_0@mas.to
      wrote on last edited by
      #13

      @jonny ... There's also privacy concerns. Few admins will read posts or people's DMs unless something is flagged as abuse, but it looks like what's proposed here puts all of people's content in front of admins and asks them to review it, which is much more invasive than typical use of the instances otherwise.

      If instances accept people signing up and posting without review, I question the grounds on which they want to be able to review all of someone's posting history before allowing migration.

      tokyo_0@mas.toT 1 Reply Last reply
      0
      • tokyo_0@mas.toT tokyo_0@mas.to

        @jonny ... There's also privacy concerns. Few admins will read posts or people's DMs unless something is flagged as abuse, but it looks like what's proposed here puts all of people's content in front of admins and asks them to review it, which is much more invasive than typical use of the instances otherwise.

        If instances accept people signing up and posting without review, I question the grounds on which they want to be able to review all of someone's posting history before allowing migration.

        tokyo_0@mas.toT This user is from outside of this forum
        tokyo_0@mas.toT This user is from outside of this forum
        tokyo_0@mas.to
        wrote on last edited by
        #14

        @jonny ...To cut a long thread short, my personal feel is that while abuse should be prevented and migration should be managed in a way that respects rate limits and doesn't overload instances, a lot of other instance admin concerns are more fear than reality, and may lead to a solution that raises privacy concerns and the risk of unexpected user data loss, while empowering admins to hinder a process they basically don't want to happen, undermining the whole concept of content portability.

        tokyo_0@mas.toT 1 Reply Last reply
        0
        • lisarue@mastodon.geekery.orgL lisarue@mastodon.geekery.org

          @benpate @jonny
          These are very consistent in the stuff that both do - it is clear that ActivityPub is already *almost* able to do content portability just by serving up content the way it does. We have a task force within the SocialWebCG working on account portability - jonny would you join a call if we schedule one soon?

          benpate@mastodon.socialB This user is from outside of this forum
          benpate@mastodon.socialB This user is from outside of this forum
          benpate@mastodon.social
          wrote on last edited by
          #15

          @lisarue @jonny

          If you get something scheduled, I'll do my best to attend 🙂

          jonny@neuromatch.socialJ 1 Reply Last reply
          1
          • benpate@mastodon.socialB benpate@mastodon.social

            @lisarue @jonny

            If you get something scheduled, I'll do my best to attend 🙂

            jonny@neuromatch.socialJ This user is from outside of this forum
            jonny@neuromatch.socialJ This user is from outside of this forum
            jonny@neuromatch.social
            wrote on last edited by
            #16

            @benpate @lisarue thanks for reminding me to respond to that email 🫣

            julian@activitypub.spaceJ 1 Reply Last reply
            0
            • jonny@neuromatch.socialJ jonny@neuromatch.social

              @benpate @lisarue thanks for reminding me to respond to that email 🫣

              julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.space
              wrote on last edited by
              #17

              jonny@neuromatch.social lisarue@mastodon.geekery.org please keep in mind that simplicity is key. I think that's Jonny's FEP's strength.

              The more complicated it is, the less buy-in, and you need all the buy-in you can get!

              1 Reply Last reply
              0
              • jonny@neuromatch.socialJ This user is from outside of this forum
                jonny@neuromatch.socialJ This user is from outside of this forum
                jonny@neuromatch.social
                wrote on last edited by
                #18

                @julian
                @lisarue
                Thank you for saying so! I tried to keep it as simple as I could and take care to carve out space for low-resource authors to implement gradually, though when all the necessary considerations were on the table it feels more complicated than I would like. Glad it still feels simple to others 🙂

                1 Reply Last reply
                0
                • tokyo_0@mas.toT tokyo_0@mas.to

                  @jonny ...To cut a long thread short, my personal feel is that while abuse should be prevented and migration should be managed in a way that respects rate limits and doesn't overload instances, a lot of other instance admin concerns are more fear than reality, and may lead to a solution that raises privacy concerns and the risk of unexpected user data loss, while empowering admins to hinder a process they basically don't want to happen, undermining the whole concept of content portability.

                  tokyo_0@mas.toT This user is from outside of this forum
                  tokyo_0@mas.toT This user is from outside of this forum
                  tokyo_0@mas.to
                  wrote on last edited by
                  #19

                  @jonny Hi there. Just looked at this again and saw the line "Actors must have some means of changing their mind about a move if the terms of moderation are unacceptable to them after the target instance reviews any imported content."

                  Not sure if that's new or if I missed it before (sorry if I did! 🙇‍♀️), but it could take care of a lot of the concerns I mentioned. Was thinking too maybe instances could say on their about pages about policies for migrated content ("we strip all media" for example).

                  tokyo_0@mas.toT 1 Reply Last reply
                  0
                  • tokyo_0@mas.toT tokyo_0@mas.to

                    @jonny Hi there. Just looked at this again and saw the line "Actors must have some means of changing their mind about a move if the terms of moderation are unacceptable to them after the target instance reviews any imported content."

                    Not sure if that's new or if I missed it before (sorry if I did! 🙇‍♀️), but it could take care of a lot of the concerns I mentioned. Was thinking too maybe instances could say on their about pages about policies for migrated content ("we strip all media" for example).

                    tokyo_0@mas.toT This user is from outside of this forum
                    tokyo_0@mas.toT This user is from outside of this forum
                    tokyo_0@mas.to
                    wrote on last edited by
                    #20

                    @jonny What happens with this now? Sorry if I'm asking you something that's already documented elsewhere (if it is, am happy to read there instead) - I don't know how these kinds of proposals typically progress, but it would be good to see this keep moving forward. Appreciate all the work you've put into it 👍

                    jonny@neuromatch.socialJ 1 Reply Last reply
                    0
                    • tokyo_0@mas.toT tokyo_0@mas.to

                      @jonny What happens with this now? Sorry if I'm asking you something that's already documented elsewhere (if it is, am happy to read there instead) - I don't know how these kinds of proposals typically progress, but it would be good to see this keep moving forward. Appreciate all the work you've put into it 👍

                      jonny@neuromatch.socialJ This user is from outside of this forum
                      jonny@neuromatch.socialJ This user is from outside of this forum
                      jonny@neuromatch.social
                      wrote on last edited by
                      #21

                      @tokyo_0 sorry i must have missed your replies before - that's a thing i had wanted in the spec but didn't have the time to write immediately, so added it shortly after publishing it. the idea to me is that you should propose moving and know if you wouldn't want to move (and in any circumstance be able to go off grid with your backups and pop up later if it takes you awhile to hunt for an instance)

                      what happens now is that i'm going to implement it and PR into glitch and masto, and revise it along the way 🙂

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups