DOI: 10.5281/zenodo.3609250
title: ABOME: A Multi-platform Data Repository of Artificially Boosted Online Media Entities

description: <strong>Motivation</strong> The rise of online media has enabled users to choose various unethical and artificial ways of gaining social growth to boost their credibility (number of followers/retweets/views/likes/subscriptions) within a short time period. In this work, we present ABOME, a novel data repository consisting of datasets collected from multiple platforms for the analysis of blackmarket-driven collusive activities, which are prevalent but often unnoticed in online media. ABOME contains data related to tweets and users on Twitter, YouTube videos, YouTube channels. We believe ABOME is a unique data repository that one can leverage to identify and analyze blackmarket based temporal fraudulent activities in online media as well as the network dynamics. <strong>License</strong> Creative Commons License. <strong>Description of the dataset</strong> <strong>- Historical Data</strong> We collected the metadata of each entity present in the historical data <strong>Twitter:</strong> We collected the following fields for retweets and followers on Twitter: <code>user_details</code>: A JSON object representing a Twitter user. <code>tweet_details</code>: A JSON object representing a tweet. <code>tweet_retweets</code>: A JSON list of tweet objects representing the most recent 100 retweets of a given tweet. https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/user-object↩︎ https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/tweet-object↩︎ <strong>YouTube:</strong> We collected the following fields for YouTube likes and comments: <code>is_family_friendly:</code> Whether the video is marked as family friendly or not. <code>genre:</code> Genre of the video. <code>duration:</code> Duration of the video in ISO 8601 format (duration type). This format is generally used when the duration denotes the amount of intervening time in a time interval. <code>description:</code> Description of the video. <code>upload_date:</code> Date that the video was uploaded. <code>is_paid:</code> Whether the video is paid or not. <code>is_unlisted:</code> The privacy status of the video, i.e., whether the video is unlisted or not. Here, the flag <em>unlisted</em> indicates that the video can only be accessed by people who have a direct link to it. <code>statistics:</code> A JSON object containing the number of dislikes, views and likes for the video. <code>comments:</code> A list of comments for the video. Each element in the list is a JSON object of the text (<em>the comment text</em>) and time (<em>the time when the comment was posted</em>). We collected the following fields for YouTube channels: <code>channel_description:</code> Description of the channel. <code>hidden_subscriber_count:</code> Total number of hidden subscribers of the channel. <code>published_at:</code> Time when the channel was created. The time is specified in ISO 8601 format (YYYY-MM-DDThh:mm:ss.sZ). <code>video_count:</code> Total number of videos uploaded to the channel. <code>subscriber_count:</code> Total number of subscribers of the channel. <code>view_count:</code> The number of times the channel has been viewed. <code>kind:</code> The API resource type (e.g., <em>youtube#channel</em> for YouTube channels). <code>country:</code> The country the channel is associated with. <code>comment_count:</code> Total number of comments the channel has received. <code>etag:</code> The ETag of the channel which is an HTTP header used for web browser cache validation. The historical data is stored in five directories named according to the type of data inside it. Each directory contains json files corresponding to the data described above. - <strong>Time-series Data</strong> We collect the following time-series data for retweets and followers on Twitter: <code>user_timeline</code>: This is a JSON list of tweet objects in the user’s timeline, which consists of the tweets posted, retweeted and quoted by the user. The file created at each time interval contains the new tweets posted by the user during each time interval. <code>user_followers</code>: This is a JSON file containing the user ids of all the followers of a user that were added or removed from the follower list during each time interval. <code>user_followees</code>: This is a JSON file consisting of the user ids of all the users followed by a user, i.e., the followees of a user, that were added or removed from the followee list during each time interval. <code>tweet_details</code>: This is a JSON object representing a given tweet, collected after every time interval. <code>tweet_retweets</code>: This is a JSON list of tweet objects representing the most recent 100 retweets of a given tweet, collected after every time interval. The time-series data is stored in directories named according to the timestamp of the collection time. Each directory contains sub-directories corresponding to the data described above. <strong>Data Anonymization</strong> The data is anonymized by removing all Personally Identifiable Information (PII) and generating pseud-IDs corresponding to the original IDs. A consistent mapping between the original and pseudo-IDs is maintained to maintain the integrity of the data.