Programming Bob: Social Media; The Struggles of Data Manipulation.

Data Manipulation with Python:

One of the major struggles of Programming Bob to date has been thinking in term of memory. I want Bob to handle memories differently than anything that has been programmed before. The main factor being Bob should be able to recall important information from conversations with the end user.

This idea sounds simple enough, right? Simply figure out what key information should be saved and save that to a file and all done. Than you have to think about how Bob can easily access the information he stored into the file and make sense of that information as well.

While Programming Bob to handle Twitter I had to think of the information that an average Twitter user wants anytime access to, also the information an influencer would want anytime access to. Along with how other parts of Bob will access the information while posting/cross posting.

The end user should be able to access any aspect of Twitter with a simple voice command, "Hey Bob, Give me the stats on my last twitter post" should return all the engagement information provided by twitter.

"Hey Bob, tweet: Happy 420 to all! #420" Then you have the following come back to Bob.

Than when you look at Twitter you see:

Bob initially stores the tweet ID along with the Tweet text from Twitter. Bob takes the local system time to produce a time stamp also counts each post after successfully saving the posting information to the data file.

The memory this far has been using JSON to store information. Most of the memory at this current stage is still unencrypted since I am still programming. Once Bob is ready for initial release all obtained memory will be encrypted upon saving and decrypted when loading.

The encryption on memory files should help secure end users data further.

What Part of Bob is Next?

Now we are adding posting support for another social media site that is similar in nature to Twitter. The goal as of now is to get 6 different post live with a single command. As of now we currently support posting to two different sites which isn't close to the number Bob will be at in future versions.

To avoid duplicate post we take the text from the user and we see if matches the text from all other post, if the post matches the function returns True else return False. This allows us to check our new post against post we have made in the past.

As of now we don't download data from social media accounts. After phase 1 of Bob's Social Media packages are completed, Bob will than be upgraded to download all historical post data. Anyone into analyzing data knows the more data you have the picture you get.

I feel it is important at this stage in development to focus a lot of time on the "Main Modules" which ideally will be the main selling points of Bob. Although Bob isn't for sell at this point.

Summary:

Now that we can successfully post to twitter using Bob, I want to look at another Social Media site to post all of our Twitter post to. I am going to program Bob to go the extra mile. I.E let's say you only have a twitter account. When Bob's starting to cross post he will recognize this and offer to create an account on twitter or other platforms for you as well.

One person can spend hundreds of hours posting and monitoring every social media platform that they use which leaves out major potential for those platforms the user should be using as will. Bob opens the door for the end-users to have more free time for content creation, family and leisure activities.

While not losing track of balancing your social media channels. I personally know the struggles of raising 4 kids while trying to stay active during the summer time and to still make time for friends and family is near impossible.