v0.7 - On branch Privacy
Added a  method to hide users from being shown in <i> Users </i>
	-Appended the database schema in queries
	-Appended the database/db.insert_new_user method
	-Added a new database/db.update_user method to augument the public/private settings
	-Implemented not showing private users in landing.users

Next Version
	-Change landing.view to hide relevant data if the user is private and the self.user has not subscribed to him
v0.7.1 Settings from Branch Privacy
Added a new module which enables people to change specific settings about one's profiles.
Only one of the four mentioned settings work insofar
	-Change the visibility setting of your profile.

Next Version
	-Implement a way to add mentions in a post
v0.7.2	Privacy
Modified the Datastore class to enforce privacy concerns within itself
ie-  The datastore will be responsible to enforce hiding/showing data to the landing and not the other way round
Its a design choice will may have its advantages or disadvantages, as will unfold as time progresses.

Also, modified a line here and there, brushing up the Datastore

Next Version
	-Add another function to find all the user mentions in the post
v0.7.3 Mentions
Implemented a way to add mentions for a post
@<userid> to mention someone in a post.
While this won't send him/her a notification, they will still see your post on their timeline even if they havent subscribed to it
Also, even if their profiles are hidden, you would be able to see their posts mentioning you.
Closing this as of now.
v0.7.4 Mentions integrated
	- database.db: implemented a new function get_mentions_of to fetch a list of mentions of a user
	- Tweaked the landing.view to hide irrelevant details regarding ups
	- Fixed a missing \n in help

Todo -
	- Organize the script to make it more relevant.
v0.7.5 Try and catch errors
Changes
	-Implemented some basic error catching to prevent program crashes due to bad network
	-The server will try to sequentially try for ports while binding to them. And will throw the final port number at the end
	-The server will try to connect to an online website to fetch its (server's) IP address. Will display 127.0.0.1 otherwise
	-The client will try and connect to the server, if fails then will prompt for a new IP and port.
v0.7.6 Exceptions and Long Message
Changes
	-Added method to send messages more than 1024 characters long to the client (UNTESTED)
	-Added method to receive messages more than 1024 characters long from the server
		Both of the above is done by notifying the client by the 'incoming' flag in the prompt and initiating a loop of send-receive on both ends.
	-Added better error handling on client side.
	-Invalid Port numbers can now easily be caught and forced to re-enter
	-A variable name change on server code
Saving the database online. It might be required to fetch values older than one day, for later purposes
v0.7.7 Long messages
After a lot of attempts and peril, finally long messages can be sent from the server to the client.
The same is not true for the vice versa though
Merging the database
Merge pull request #36 from geraltofrivia/Privacy

Privacy