1
00:00:00,810 --> 00:00:02,690
- [Instructor] So, one
thing that's commonly done

2
00:00:02,690 --> 00:00:05,390
with the live tweet stream,
is to take those tweets

3
00:00:05,390 --> 00:00:08,210
and actually store them into a database

4
00:00:08,210 --> 00:00:09,630
for later processing.

5
00:00:09,630 --> 00:00:11,600
That's actually something we'll do,

6
00:00:11,600 --> 00:00:14,480
when we get to the big
data lesson later on,

7
00:00:14,480 --> 00:00:18,700
where we'll take a massive
number of live tweets

8
00:00:18,700 --> 00:00:22,290
and store them into a MongoDB database,

9
00:00:22,290 --> 00:00:24,870
and then we'll go back
and process those tweets

10
00:00:24,870 --> 00:00:26,250
after the fact.

11
00:00:26,250 --> 00:00:29,470
So, one of the things that
you have to keep in mind is,

12
00:00:29,470 --> 00:00:34,450
that in the Twitter rules
and regulations, if you will,

13
00:00:34,450 --> 00:00:38,300
if you are storing tweets
locally and you receive

14
00:00:38,300 --> 00:00:40,990
a message from Twitter
that somebody has deleted

15
00:00:40,990 --> 00:00:45,090
a tweet, or deleted location
information from a tweet,

16
00:00:45,090 --> 00:00:49,190
you have to actually take
that information from Twitter,

17
00:00:49,190 --> 00:00:52,020
and you have to delete it locally as well.

18
00:00:52,020 --> 00:00:54,900
So, for example, your
listener's on_delete method

19
00:00:54,900 --> 00:00:59,140
is going to get called if you
have a tweet that you received

20
00:00:59,140 --> 00:01:01,820
that somebody has
subsequently said they wanted

21
00:01:01,820 --> 00:01:03,700
to delete from their account.

22
00:01:03,700 --> 00:01:06,280
So there's a whole bunch of deletion rules

23
00:01:06,280 --> 00:01:08,110
and message details.

24
00:01:08,110 --> 00:01:11,610
So, you are going to
want to go to this URL,

25
00:01:11,610 --> 00:01:14,910
and make sure you that
you are familiar with

26
00:01:14,910 --> 00:01:19,070
the rules and regulations
for deleting information

27
00:01:19,070 --> 00:01:21,490
that you store locally.

28
00:01:21,490 --> 00:01:22,770
That is a requirement,

29
00:01:22,770 --> 00:01:24,950
and if you don't follow that requirement,

30
00:01:24,950 --> 00:01:29,353
you could lose your privileges
for using the Twitter APIs.