• 312@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Especially considering the way twitter counts a “view” is if the tweet shows up in your app’s viewport, at all. So simply scrolling through the timeline consumes “views” - you could run up against this limit in 10-15 minutes of scrolling.

      It’s incredibly stupid.

      • Mog_fanatic@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        This is what I was wondering. I don’t use Twitter so 600 sounds like a lot but I was wondering how much it actually was. Someone else said they blew through it in like 15 minutes

        • Dohnakun@lemmy.fmhy.mlB
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          And sounds like it’s implemented in a api-request=view way. I’m not sure how much requests the JS makes per view but im sure it’s more than one.