Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Kush Trivedi
@kushthedude
Loklak build is failing?
Pratyush Singh
@singhpratyush
@kushthedude It is failing on dev but passing on master branch.
lfrisch
@lfrisch
api.loklak.org -> bad gateway. Is this just temporary or is it related to Kush's comment above?
Michael Christen
@Orbiter
The server was out of memory
I am restarting it
Michael Christen
@Orbiter
its running again
Rupesh Krishna Jha
@Rupeshiya
Hi everyone, Is there any MEAN stack or MERN stack related projects , where I can contribute ?
pulkit
@kpulkit29
@praveenojha33 I want to claim issues you had put up.Kindly look into it.
pulkit
@kpulkit29
The issues are quite old if no on else is taking them I would like to take them up
Kush Trivedi
@kushthedude
@kpulkit29 You may drop a comment on the issue and begin working on them
Jesstern Rays
@jsstrn

Hi folks! I'm new to loklak and would like to get some help getting started.

I'm trying to get tweets for the hashtag #CRISPRbabies. When I try this on loklak.org I don't get any results.

I am lead to believe that I have to start my own server to harvest these tweets. I followed the instructions to run a docker image locally and have gotten it up and running successfully.

Here is where I am stuck. I do not know how to instruct the server to harvest specific tweets. All I get is got 0 suggestions for harvesting from 0 in backend.

My questions are:

  • How do I instruct the server to start harvesting specific tweets?
  • How do I collect that data?

Sorry if these are noob questions. I did try to read the documentation before asking here, but since I'm not getting anywhere I am asking for help. Any help is much appreciated. Thank you.

Mario Behling
@mariobehling
@jsstrn I think we need to update the scraper to the new twitter design.
There might be some tweets left out after twitter changed its design.
Pratyush Singh
@singhpratyush
Jesstern Rays
@jsstrn
@mariobehling @singhpratyush thanks for the info.. I'm not too familiar with Java though
Michael Christen
@Orbiter
Hi Mario, bin gleich fertig hier, bist du zuhause?
pulkit
@kpulkit29
getting this error while running npm install
ERROR in Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Can't find any solution
Pratyush Singh
@singhpratyush
@kpulkit29 Is that from loklak search?
pulkit
@kpulkit29
Yes
Solutions on stackoverflow not working for me
pulkit
@kpulkit29
Can pls someone help me out with this
Pratyush Singh
@singhpratyush

Hi @kpulkit29,

I just tried a fresh install and it worked completely fine.

Please make sure you are using node@8.11.3 and @angular/cli@6.0.5. Here is the flow to get into that config -

$ sudo npm i -g @angular/cli@6.0.5
$ npm i

To get your node to the desired version, you can use n -

$ sudo npm i -g n
$ sudo n 8.11.3

After you are done with all this, you can simply ng serve the application and go to http://localhost:4200/ to see it. If there are more problems, try completely removing node_modules and reinstalling (rm node_modules -rdf).

pulkit
@kpulkit29
@singhpratyush thanks a lot
Pratyush Singh
@singhpratyush
@kpulkit29 No problem :). Please let us know here if you still face issues.
pulkit
@kpulkit29
subhahu
@subhahu123
How can i apply for gci mentor
Bram Borggreve
@beeman
Hey all ! I just found Loklak and it seems like a very useful tool for a project I'm working on. I was wondering if I could configure loklak in such a way that it only downloads/indexes a few hashtags and usernames?
I checked the docs but could not really find anything that points in that direction. Any ideas?
Pratyush Singh
@singhpratyush
Hey @beeman! From what I know, it would not be possible to crawl for specific hashtags/usernames. You can trigger searches for those terms in order to get the data related to them in the index/dump. Keep in mind that Tweets older than a month will get deleted from index.
Bram Borggreve
@beeman
Thanks for your reply @singhpratyush
Michael Christen
@Orbiter
@beeman loklak ‚just‘ scrapes twitter and it cannot foresee what comes from twitter as a search result. However, you can do specific searches, like for specific hashtags and specific user names. You can use the same search operator syntax as twitter provides, please see search.twitter.com -> operator
Bram Borggreve
@beeman
@Orbiter thanks! So in order to get a database with only the hastags/user-feeds I want, I'd create a simple app that listens to those on loklak and store those, instead of customizing my own loklak instance
Michael Christen
@Orbiter
Yes!
In some way loklak already does this itself: once you searched for something, loklak will repeat the search again and again. Internally. It pauses between searches according to the tweet frequency as observed so far.
For all searches.
You get a json dump for that.
In data/dump/own
It accumulates all tweets from one day in one file.
Leo Treasure
@songproducer_twitter
Hi, I need some help running the elastic server to connect with lok lak
Leo Treasure
@songproducer_twitter
i'm trying to look at the localhost:9100 but it shows cluster health: not connected
I made a config folder and a config/elasticsearch.yml file with
http.cors.enabled: true
http.cors.allow-origin: "localhost"
http.cors.allow-headers: Authorization
Leo Treasure
@songproducer_twitter
also struggling with kibana:
No living connections
log [12:21:56.811] [warning][admin][elasticsearch] Unable to revive connection: http://localhost:9200/
Leo Treasure
@songproducer_twitter
should the config/elasticsearch.yml file be in the kibana or loklak folder?
Pratyush Singh
@singhpratyush
@songproducer_twitter The elasticsearch HTTP server listens on port 9201 (see https://github.com/loklak/loklak_server/blob/development/conf/config.properties#L180). So you should connect to it on http://localhost:9201/.
Leo Treasure
@songproducer_twitter
Thanks Pratyush I'm running Kibana but getting this error:
No living connections
log [13:42:19.427] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/
Pratyush Singh
@singhpratyush

log [13:42:19.427] [warning][admin][elasticsearch] Unable to revive connection: http://127.0.0.1:9200/

Have you tried switching the port from 9200 to 9201?

Pratyush Singh
@singhpratyush

I was able to get Kibana working with the deployment -

$ sudo docker run --net host --init  --name kibana -e ELASTICSEARCH_URL=http://localhost:9201 blacktop/kibana:4.6
WARNING: Tini has been relocated to /sbin/tini.
Please update your scripts to use /sbin/tini going forward.
/usr/bin/tini has been preserved for backwards compatibility in Alpine 3.4,
but WILL BE REMOVED in Alpine 3.5.

[WARN  tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper.
        Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
        To fix the problem, use -s or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:kibana@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:elasticsearch@1.0.0","info"],"pid":8,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:kbn_vislib_vis_types@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:markdown_vis@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:metric_vis@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:spyModes@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:elasticsearch@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:statusPage@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["status","plugin:table_vis@1.0.0","info"],"pid":8,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-11-25T15:34:49Z","tags":["listening","info"],"pid":8,"message":"Server running at http://0.0.0.0:5601"}

Please make sure you are using Kibana version 4.6 for compatibility with ES 2.4.