We wanted to address some security and privacy feedback related to Fleets. Here’s a technical breakdown of what we’ve heard and what we’ve done to address it:

 906  279  218


@doktorp777 Profile picture Pedro Girondi


 2 months ago
 0  0  0

@TwitterSupport My Twitter account I need help getting it bck y’all are no help

 2  1  0
@mrcarlos36 Profile picture Carlos figueroa


 2 months ago

@TwitterSupport Carlos is on Twitter today

 0  0  0

We don’t believe this is a security or privacy concern because Fleets (from accounts without the "protected" setting) are public. We updated our systems today to require an authenticated session before requesting Fleets metadata, to add more friction to use these APIs.

 158  6  31

The edge cases that can result in a mismatch between the “Seen by” list and the actual people who saw your Fleet are uncommon, but we realize that this may not have aligned with expectations. We’re taking this feedback seriously and considering how we can improve.

 265  43  43

Finally, we heard concerns that people can see Fleets without showing up in the “Seen by” list. Our goal is to show a list of people who've seen your Fleet, but we don’t guarantee completeness for technical and experience reasons. For example, we cap the list when it gets long.

 188  26  34

We hope this thread provides helpful context on the concerns and feedback that were shared. As always, we appreciate you sharing your concerns and apologize for any confusion or frustration this may have caused.

 343  246  55

This meant that developers could save a Fleet URL during the 24h the Fleet was active. Due to our queue backlog, that URL may have still been accessible after the Fleet expired. The queue is now caught up and we’ve updated our systems to reduce the likelihood that this reoccurs.

 166  6  33

We also heard concerns that Fleets may be visible to people who aren’t logged in. To clarify, people using Twitter apps can only see Fleets when logged in. But it’s possible for developers to make API calls to return Fleets metadata through a common behavior called “scraping”.

 157  8  38

First, we heard concerns about expired Fleets still being viewable. Fleets are *not* viewable in Twitter apps after 24h. However, our backend system has a queue that deletes Fleets media after 24h –– this system fell behind on Friday morning PST due to scaling problems.

 195  13  35

Your wish has been granted 👍🏾 ⁦@PatrickMahomes⁩ 🏆 ⁦@TomBrady⁩ 🏆🏆🏆🏆🏆🏆 #ChiefsKingdom 🏆🏆 #RunItBack #SBLV

 0  0  0  Download


 1  0  1

@engel3313 @PSchrags @ArrowheadPride It was characteristic of how they played when they played the Chiefs
Last 3 years for the Chiefs has been literally unheard of.
Chiefs are a young team & they will be back #RunItBack

 0  0  0

This “We’re going to the Super Bowl” high is a feeling I never want to lose. Savor it #ChiefsKingdom #RunItBack

 0  0  0

And @ESPNNFL talking about your record-setting night without throwing the Cheetah on the graphic. SMH #RunItBack

 0  0  0  Download