LoklakBuilding the twitter integration to Distributed tweet search server and endless possibilities

Hello!I am Sudheesh Singanamalla@sudheesh001github.com/sudheesh001

What is Loklak ?1This is a back-end search- and storage-infrastructure for microblog-messages. Make your own search portal! loklak scrapes tweets from twitter html pages (more message sources to come). We+Youcollect and share tweets with a peer-to-peer network.

“Moving towards Open Data and Anonymity.

The twitter API does not allow you to access the public tweet information directly and needs one to be authenticated to use fetch and use the data. We believe that this data is very important for a variety of purposes and needs to be open and available anonymously.

Here’s where Loklak comes into place.

Functionality◇ An amazing and quick search functionality for the tweets◇ Fast response time between posting on twitter and the

information being scraped by loklak (approx. 2 seconds)◇ Peer to Peer architecture and storage.

Why use Loklak ?◇ Collect and store a very, very large amount of Tweets and similar messages

◇ Create your own search engine for Tweets

◇ Omit authentication enforcement for API requests on the Twitter platform

◇ Share Tweets and Tweet archives with other Loklak users

◇ Search anonymously on your own search portal

◇ Create your own Tweet search portal or statistical evaluations

The loklak server does not record client IP-adresses when a search is done, therefore loklak.org, running loklak does also not record or log IP addresses from searchers

You can run loklak yourself which gives you complete control over logged things (where no IP addresses are, but whatever).

Anonymity GuaranteedIf you don't want to search on loklak.org and also don't want to scrape data from Twitter, you can still search in your own index and feed this index with import files from other loklak peers

The built-in short-link de-shortener protects you from tracking by short-link services, including Twitter and bit.ly.

Distributed Peer to Peer

◇Whenever a peer acquires new Tweets, it reports these to the back-end for storage. This means that fresh Tweets are stored at four locations: your own Elasticsearch index, your own message dump file and in the remote back-end-peer in the Elasticsearch index and dump file. This causes that all messages that you find are available for download for other users at the back-end which is by default loklak.org.

◇Whenever a peer starts up, it calls the back-end to announce it's existence. This fills a peer-table in the back-end which everyone can use to retrieve the list of active peers. Therefore everyone can identify peers which may provide message-lists for download.

◇Any topology can be achieved when the user changes the host name of the back-end. You can create your own message-sharing network easily.

Loklak instances can be connected to each other. If you download loklak and run it unchanged, it connects to loklak.org by default as a back-end peer. You can change this if you want to. This is how connected peers work:

Possibilities ?

Twitter is an amazing source of information and can be potentially used for various purposes like◇ Research◇ Customer support◇ Complaint tracking◇ Conference wall tracking◇ Social Media statistics◇ Sentiment analysis of twitter/social media data

170,004,946+Tweets already index my loklak.org and millions more by its peers.

Easy to use APISupports multiple languages.

A use case of Loklak in passive governance through GEAR at the Govt. of Telangana, India

Contribute to Loklak

Fork and Clone the Repo

Build using “ant” or “gradle”

Run the server

Thanks!Any questions?You can find me at:◇ @sudheesh001◇ sudheesh95@gmail.com

https://github.com/loklak