Collect Twitter mentions of the specific topic: Security, positive sentiment - 25$

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 15:54

The goal for this issue is to collect a minimum of 200 tweets in response to the security at crypto custodians (you can find one of the exchanges lists here, and examples of the events that are of our interest in this file).

A suggested way to deal with the issue is the following:

1. Find relevant to the topic events - hacks, vulnerabilities, bugs, etc - anything that relates to security breaches at crypto custodians. You may use Google News for this (the search query could be ${Exchange Name} + ${Topic}). Example: “binance service outage”
2. Use the search results to figure the dates of the event (example: the exchange was on the hacked on Nov 26th)
3. Filter Twitter results by date close to the event
4. For this issue, look for the tweets, negatively commenting on the security of custody-providers services
5. If you think the Tweet is relevant, add this to a CSV, using the following format: “username, date, tweet-content, topic”

To better understand if the Tweet addresses the necessary topic, you can find examples of the security-related tweets here

Important note:

Do not Twitter-search for the topic-related keywords, such as “security” - instead, make sure to follow the steps, as described above. With that, filter Twitter search by dates and Exchange names only. (Example: search for “binance”, Nov 26-28 because the hack happened on Nov 26)

To start the task:

1. Leave a comment in this GitLab issue.
2. In the comment, let us know you’ve started the task and mention the amount of time you will need to finish it.

Upon completion of the task:

1. Upload your CSV file to Google Drive and share it with alina.park@inca.digital
2. Leave a comment in the issue, saying you’re done
3. Send an email to alina.park@inca.digital with the info on the preferable payment method

Feel free to take a look at the issues on the rest of the topics below

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 15:54

changed due date to June 30, 2020

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:12

marked this issue as related to #54

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:12

made the issue confidential

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:12

marked this issue as related to #52

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:13

marked this issue as related to #54

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:13

marked this issue as related to #50

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:13

marked this issue as related to #51

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:14

removed the relation with #52

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:15

marked this issue as related to #52

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:15

removed the relation with #52

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:15

marked this issue as related to #52

[evgenydmitriev]

In GitLab by @alina.park on Jun 8, 2020, 16:16

marked this issue as related to #49

[evgenydmitriev]

In GitLab by @alina.park on Jun 9, 2020, 15:15

removed the relation with #54

[evgenydmitriev]

In GitLab by @alina.park on Jun 16, 2020, 14:21

made the issue visible to everyone

[evgenydmitriev]

In GitLab by @nur_yernur on Jun 28, 2020, 18:24

Got the task, will finish in 8 hours.

[evgenydmitriev]

In GitLab by @alina.park on Jul 13, 2020, 23:29

closed