waartaa / waartaa Goto Github PK

A modern web based communication service on top IRC.

License: MIT License

JavaScript 49.38% Python 39.35% CSS 9.46% Smarty 1.81%

waartaa's Introduction

waartaa

A web IRC client written on top of React and Pyramid. It is aimed towards being an intuitive, collaborative IRC client across multiple devices of the user along with centralized logging.

System dependencies

# Dependency for crossbar
sudo dnf install -y libsodium libsodium-devel

Development

Install the system-level dependencies
sudo dnf install python-virtualenvwrapper libsodium libsodium-devel
Create a virtualenv
mkvirtualenv waartaa
Install the required packages
pip install -r dev_requirements.txt
Waartaa runs on top of ircb. So follow the instructions to setup ircb.
Run the ircb stores
IRCB_SETTING=ircb.settings.py ircb run server -m allinone --port 9999
Run the development server
python waartaa/app.py
Move to a different terminal and start
cd waartaa/client/
Build JS assests
npm start

Contribute

Setup and run waartaa locally.
Report bugs or submit feature requests at https://github.com/waartaa/waartaa/issues/new.
Feel free to pick up open issues from https://github.com/waartaa/waartaa/issues?state=open. Don't hesitate to ask for help.

Comunicate

Mailing list: https://groups.google.com/forum/#!forum/waartaa
IRC: #waartaa on Freenode

waartaa's People

Contributors

Stargazers

Watchers

Forkers

rtnpro sanketsaurav sunu darkowlzz birajkarmakar kaushikgandhi ramaseshan hardfire aavrug codenamesubho heteroscedastic kenzo450d mjnovice shashankgroovy ryansb anistark akifkhan shilpita-nag bogdanciobanu rupojs debjeetsarkar suchetaghoshal dennyscott dandandan rahul91 d-ne0 vireshas gggodhwani otwstephanie kumarrishav jacksonisaac prashantjha arjitc xobs jayunit100 gopesht sheeshmohsin shiminsh harsha345 harshadptl gsbprojectx butteredtoast pratik217 bnprk jee1mr payingattention d3cryptor iyogeshjoshi ashishmit14 viiicky langdon sanbornsen sanjayankur31 artogn pshenoy-uc mohammedzee1000 mudithkr rotron sapanajadhav abdul tkuennen iq-scm

waartaa's Issues

PM by someone else disconnects the user

When another user tries to PM me, I get disconnected.

Remove "insecure" package

Is there a reason it is still included?

The insecure package defaults to read/write access to collections with no rules.

The Meteor documentation also recommends removing the package.

Implement nick autocomplete via AJAX

Something similar to http://jqueryui.com/resources/demos/autocomplete/remote-jsonp.html can be used. A router needs to be added in the server code for this which will return the list of matching nicks.

Convert URLS to links

Convert URLS to links with target="_new".

/me command

The command /me not working

Fix scrollbars

Scrollbars sometime come and sometime doesn't. This issue lies with

updateHeight: https://github.com/waartaa/waartaa/blob/master/waartaa/client/chat.js#L1

and

highlightChannel: https://github.com/waartaa/waartaa/blob/master/waartaa/client/chat.js#L38

in waartaa/client/chat.js.

Don't scroll to bottom for non chatlog scrollbars on entering new channel message

Bug location: https://github.com/waartaa/waartaa/blob/master/waartaa/client/chat/chat_input.js#L61

Proposed fix:
Replace $('.nano').nanoScroller({scroll: 'bottom'}); with $('.chat-logs-container').nanoScroller({scroll: 'bottom'});.

Don't post '/' command to channel.

When typing commands in a channel/pm room, we should not post the message to the room. It should be logged if required only for the particular user.

Porting waartaa as an android application

Hey Guys ~!
I took a look at waartaa and i must tell you its a great application. I have an idea of making a mobile extension of waartaa. This is what will globalise waataa to a greater extent. My idea of making waartaa it very user-friendly, easy to use through mobile phones.

I would like to propose an idea of writing a native android application for it.

Thanks & Regards
Sunny Sharma

side users bar not populated

npm install meteorite Failed

npm http GET https://registry.npmjs.org/meteorite

npm ERR! Error: failed to fetch from registry: meteorite
npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
npm ERR! at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
npm ERR! at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
npm ERR! at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR! at Request. (/usr/lib/nodejs/request/main.js:212:58)
npm ERR! at Request.emit (events.js:88:20)
npm ERR! at ClientRequest. (/usr/lib/nodejs/request/main.js:412:12)
npm ERR! at ClientRequest.g (events.js:156:14)
npm ERR! at ClientRequest.emit (events.js:67:17)

Scaling waartaa

Issues:

Duplicate logs per user per channel
As MongoDB size grows, read and write is becoming costlier.

Proposed solutions:

Use capped collection for log collections and replicate old data to another db.
Store only single log per channel for all user.

Change GitHub app name from waartaa-alpha to waartaa-beta

This matches with the Waartaa Beta logo on the website.

You should be able to search the logged in users list

nginx could not be found in Centos Vagrant box

TASK: [nginx | Install nginx] *************************************************
failed: [default] => {"changed": false, "failed": true, "item": "", "rc": 0, "results": []}
msg: No Package matching 'nginx' found available, installed or updated

FATAL: all hosts have already failed -- aborting

Online users get emails when mentioned

Users get emails when mentioned even if they are online

Prevent multiple click issue during joining servers

Currently, when the user submits the join server form multiple times (due the UI not being responsive), multiple nicks for the same user join the server. This is a bug and we need to fix this.

Optimize rendering channel nicks list

Currently, switching to a server channel with a lot of nicks (e.g., 150) is slow. It takes time to compute and render the nick list for the channel.

I see two solutions for this:

Always keep channel's nick list rendered and just display and hide it as needed.
Non blocking rendering of channel's nick list.

I am in favour of the 1st solution. Please feel free to share your suggestions.

Autoselect the first channel when joining new channel(s)

Waartaa allows joining multiple channels in one go. The desired behaviour will be to auto select the first channel room from the list of newly joined channels.

vagrant: turn off firewall on boot

Handlebar not rendering text between <>

The following characters could interfere with an HTML or JavaScript parser and should be escaped in string literals: <, >, ", ', , and &. Though all the special characters are being escaped but immediate text between < and > is not rendering by the handlebar.

Change the placeholder for channels list

When adding a new server, the placeholder for channels list is "Channels...". Something like "#channel1, #channel2, #channel3" is more intuitive, just like when adding new channels to an existing server.

Find the optimal amount of data to be rendered on client side based on viewport size

Currently, we have hard coded the number of chat logs, channel nicks to render by default on the client. This is not optimal: sometimes we display more data than visible (for small screens) and sometimes less (for large screens). We need to calculate these values dynamically on page load taking viewport size into account.

This will help make page load and chat room transition snappy for most screen sizes and also allowing us to display more data for large screens in a descent (if not fast) way.

Audio notification not working properly

There seems to be some issue with audio notifications from Waartaa with update to Meteor 0.8.

Probable bug location:

Notify user on mention when browser/tab is not active

Currently, the user is notified on mention on a channel/pm which is not active. But what if he's mentioned on the active chatroom and the browser or waartaa's tab is not in focus. The user needs to be notified in this case too.

"try" takes an enormous amount of time to load (10+ mins)

Deploy on openshift

Hello:
Has anyone succeeded in installing waartaa on OpenShift?, Looks like a good place to run an instance

Disable nick options dropup in chat input box when no room is selected

When no chat room is selected, we are still able to click the nick options dropup to display the nick options form. This should not be allowed. The dropup link should be disabled.

Sort server logs by date (from old to latest)

Currently server logs are shown in the chat interface in reverse order, I mean, from newest to old. This is a silly mistake and an easy fix.

Please feel free to pick it up and fix it.

freezes at Signup

In the front page ( first time run ), when pressed the button Configure GitHub Login, the app freezes.

Forwards always to localhost

I installed waartaa on a shell space, i let it listen on localhost:59520 and let apache pass the requests through via
RewriteRule ^waartaa/(.*) http://localhost:59520/$1 [P]

It always forwards! me to https://localhost/.
I tried changing the rule to
RewriteRule ^waartaa/(.*) https://localhost:59520/$1 [P]
what gives me an internal server error.

I start meteor with ROOT_URL="https://domain/waartaa/"

Any idea what could be wrong? I'm new to the meteor/nodejs stuff so i imagine i missed some config parameters.

Please update the dependencies doc

tried to install Waarta on my VPS but due to so many dependencies which I was able to figure out on seeing the error messages and still wasnt able to run it.
So may be please someone list all the dependencies needed. even Mongo DB was not listed and I figured it out after so much time.

Connection to server fails.

On submitting server name, nick and channel name, there seems to be continuous attempts to connect which fails with the following errors in paste.

https://pastebin.mozilla.org/3860338

Fix selecting server rooms.

When waartaa is loaded first time, at least a server room (preferably the first channel room > pm room > server room) should be auto selected.

When a selected server room is closed, the previous server room (if not available, then the next room) should be selected.

Update README & add docs

Chat logs loader message does not disappear on a channel with no log.

Bug location: https://github.com/waartaa/waartaa/blob/master/waartaa/client/chat/chat_logs/_helpers.js#L7

last_log_id is the _id of the latest channel log for the selected channel. If no channel log exist for the selected channel, last_log_id is undefined. We need to fade out the chat logs loader if last_log_id is null/undefined.

channel nicks not updating when user has left channel

even after the USERS have logged off the we are able to click on the unavailable user names and perform user operations like whois and pm
the username and dropup should be removed when the user has logged off .
refference to
https://github.com/waartaa/waartaa/blob/master/waartaa/server/lib/02_irc.js#L53

Chat and User List does not remove after removing the Server

Sending /me messages does not get saved in DB

When a user sends /me messages, it reaches the IRC server, but does not get saved in the DB. Hence, it does not appear on the screen.

Bug location:

https://github.com/waartaa/waartaa/blob/master/waartaa/server/perms.js#L12

Seems like we are not saving any RAW commands entered by user for privacy reasons to DB. However, we need to add an exception for /me commands.

Adblock Plus doesn't allow wãrtã to work on Firefox and Chrome.

With Adblock Plus enabled, wãrtã fails to render on browser.

Setup docker environment for Waartaa

Let's setup a docker environment for waartaa and see how it helps us.

We also need to consider vagrant + ansible option as well.

nick doesn't changes if someone changes his nick

If someone join IRC using 'foo' nick(using different IRC client, say hexchat), waartaa says foo joined the channel.
But now, if 'foo' changes his nick to 'bar' using his IRC client(/nick bar), the right column still shows the nick as foo. So here comes the problem that there is no nick as 'foo' at present but waartaa shows there is a nick 'foo' and there is a nick 'bar' at present but waartaa do not shows 'bar'.

See this image: Here is a nick paidn0de(After changing the nick from iamsudip)

But waartaa do not show the update:(It still shows my previous nick)

Debian install instruction in README

In README file:

For Debian/Ubuntu install only node.js and it will include npm as:

sudo add-apt-repository ppa:chris-lea/node.js sudo apt-get update sudo apt-get install nodejs

Do waartaa depends on specific version of node.js? In Debian, simply installing node.js like,

sudo apt-get install nodejs

should work!

/msg command

Can you add this command, i have probleam to identify without this. Thanks

Errors after install

Can you help me?
SO Fedora 20

Traceback:

[pablo2m@localhost waartaa]$ ./setup.sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0Downloading Meteor distribution
100 4223 0 4223 0 0 2432 0 --:--:-- 0:00:01 --:--:-- 2434

################################################################# 100,0%

Meteor 0.7.0.1 has been installed in your home directory (~/.meteor).
Writing a launcher script to /usr/local/bin/meteor for your convenience.
This may prompt for your password.

To get started fast:

$ meteor create ~/my_cool_app
$ cd ~/my_cool_app
$ meteor

Or see the docs at:

docs.meteor.com

[email protected] postinstall /lib/node_modules/meteorite
sh ./completions/postinstall.sh

npm WARN unmet dependency /lib/node_modules/block-stream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream-ignore requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream-npm requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/glob requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/npmconf requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/tar requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
[email protected] /lib/node_modules/meteorite
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
✓ jquery-ui-bootstrap
tag: https://github.com/TimHeckel/meteor-jquery-ui-bootstrap.git#v0.1.2
✓ observatory
tag: https://github.com/jhoxray/observatory.git#v0.3.21
✓ irc
tag: https://github.com/Pent/meteor-irc.git#v0.2.2
✓ handlebar-helpers
tag: https://github.com/raix/Meteor-handlebar-helpers.git#v0.0.9
✓ require
tag: https://github.com/tomconnors/meteor-require.git#v0.1.0
✓ presence
tag: https://github.com/tmeasday/meteor-presence.git#v0.3.0
✓ bootstrap-3
tag: https://github.com/mangasocial/meteor-bootstrap-3.git#v0.3.7
✓ accounts-ui-bootstrap-3
tag: https://github.com/mangasocial/meteor-accounts-ui-bootstrap-3.git#v0.2.4
✓ nodetime
tag: https://github.com/subhog/meteor-nodetime.git#v0.2.0
✓ moment
tag: https://github.com/acreeger/meteor-moment.git#v2.2.1
✓ winston-loggly
tag: https://github.com/tomrogers3/meteor-winston-loggly.git#v0.0.3
✓ winston
tag: https://github.com/tomrogers3/meteor-winston.git#v0.0.3
✓ assert
tag: https://github.com/peerlibrary/meteor-assert.git#v0.2.2
✓ nprogress
tag: https://github.com/zhouzhuojie/meteor-nprogress.git#v0.0.3
✓ GAnalytics
tag: https://github.com/datariot/meteor-ganalytics.git#v0.1.0
✓ jquery-ui
tag: https://github.com/TimHeckel/meteor-jquery-ui.git#v1.9.2
✓ observatory-apollo
tag: https://github.com/superstringsoftware/observatory-apollo.git#v0.3.2
✓ observatory-galileo
branch: https://github.com/superstringsoftware/observatory-galileo.git#master

Done installing smart packages
[pablo2m@localhost waartaa]$ cd waartaa
[pablo2m@localhost waartaa]$ meteor
[[[[[ ~/waartaa/waartaa ]]]]]

Initializing mongo database... this may take a moment.
nodetime: updating npm dependencies -- nodetime...
winston-loggly: updating npm dependencies -- winston, winston-loggly...
winston: updating npm dependencies -- winston...
=> Errors prevented startup:

While building the application:
error: no such package: 'router'
error: no such package: 'HTML5-History-API'
error: no such package: 'page-js-ie-support'

=> Your application has errors. Waiting for file change.