A Hugging Face employee made a huge dataset of Bluesky posts, and it’s already very popular.

A machine learning librarian at Hugging Face just released a dataset composed of one million Bluesky posts, complete with when they were posted and who posted them, intended for machine learning research.

Daniel van Strien posted about the dataset on Bluesky on Tuesday:

“This dataset contains 1 million public posts collected from Bluesky Social’s firehose API, intended for machine learning research and experimentation with social media data,” the dataset description says. “Each post contains text content, metadata, and information about media attachments and reply relationships.”

The data isn’t anonymous. In the dataset, each post is listed alongside the users’ decentralized identifier, or DID; van Strien also made a search tool for finding users based on their DID and published it on Hugging Face. A quick skim through the first few hundred of the million posts shows people doing normal types of Bluesky posting—arguing about politics, talking about concerts, saying stuff like “The cat is gay” and “When’s the last time yall had Boston baked beans?”—but the dataset has also swept up a lot of adult content, too.

  • FaceDeer@fedia.io
    4·
    11 hours ago

    From the Bluesky TOS:

    Bluesky Social is available as a desktop application at bsky.app and bsky.social (each a “Site”) and a mobile application (“Bluesky App” or “the App”).

    …

    These terms only apply to social networking that happens on Bluesky Social services, including the Sites and Bluesky App. If you’re using another social networking application on the AT Protocol that isn’t Bluesky Social (we call this a “Developer Application”), the developers of the other service will provide the terms and conditions that govern your experience.

    So looks like the Bluesky TOS simply doesn’t apply. Create a developer application and give it whatever training-friendly TOS you want.

    • Bilb!@lem.monsterEnglish
      1·
      9 hours ago

      It looks like they’re considering adding some equivalent of a robot.txt to express consent or non-consent for posts on ATProto, but of course as they say:

      “Bluesky won’t be able to enforce this consent outside of our systems. It will be up to outside developers to respect these settings.”