Project 1: Who consumes the tweet stream and historic tweet sentiment analysis?

[phdowling]

Hey @gyachdav and @sacdallago ,

We implemented the live streamed sentiment analysis, users can request (via websockets) twitter streams by location and pokemon name. However, we are not sure what project should actually use this data in the frontend - is this also for the @PokemonGoers/pokemap-1 and @PokemonGoers/pokemap-2 teams, or maybe @PokemonGoers/catch-em-all ? In the same vein, who is consuming the output from our historic tweet sentiment analysis project ?

Example client code for the twitter stream:

var socket = io('http://localhost:8888/sentiment');
socket.on("connect", function(){
    socket.emit("settings",
            {
                mode: "geo", // or "all" for no specific location but getting all tweets
                lat: 1, lon:1, radius: 50000000, 
                pokemonName: "Abra" // or leave out for getting all pokemon-related tweets
            }
    );
});

socket.on("tweet", function (data){
    console.log(data);
});

[sacdallago]

For the streaming bit, it's either A or E. It's a decision that has to be taken, maybe @PokemonGoers/catch-em-all and @PokemonGoers/pokedata would like to participate.

I would put everything together in project A, because it makes more sense (to me). Your project is though not in the right format to be "digested" by project A (or E, for the matter). I wouldn't create separate services that expose ports independently. You should create something small/modular enough that project A can npm require it and expose a route. Maybe via express middle layers.

Sentiment analysis should definetly go to project A. Something in the fashion: pokemob.sentiment(tweet) --> {twitterId: xyz, sentiment: 1.23} and then the guys from project A will decide what to do with the object (ideally, store it in a collection :D )