Gitter is open source

Post by l2dy » Tue, Jul 04, 2017, 1:52 PM UTC

unhammer wrote: post #86

kronos29296 wrote: post #70

Earlier quoted context omitted.

IRC is not going anywhere but projects like neovim use gitter primarily while IRC is linked using a bot. They view the IRC chat in gitter. Dunno if Gitter is better than IRC as I have only used for help and support (for me) but Gitter was far easier to use than IRC. Just Login and start chatting. I don't think IRC is going anywhere either... We just have alternatives to freenode now in Gitter

Apropos, does anyone know of a hosting provider with one-click installs of Weechat? It would be nice to have something slightly more self-hosted than irccloud to recommend to the GsoC/GCI students who keep disconnecting from freenode :) (You'd think with all the Wordpress one-click-installs that this would exists, but I can't find any yet at least.)

Post by sandGorgon » Tue, Jul 04, 2017, 2:01 PM UTC

suprememoocow wrote: post #48

corney91 wrote: post #33

Earlier quoted context omitted.

They probably do have some sort of automation, but it's likely specific to their environment.

We use Ansible / packer & terraform. Open sourcing this repo will be fairly complicated but it may make more sense for us to publish a k8s helm chart or more complete, production-ready docker-compose.yml

Post by sandGorgon » Tue, Jul 04, 2017, 2:02 PM UTC

suprememoocow wrote: post #57

e12e wrote: post #40

Earlier quoted context omitted.

This is actually the first real project I've come across that uses neo4j - thank you for pointing that out. Given the requirements, I actually think this project looks rather clean between the docker-compose-file and the npm dependencies. I very much doubt it can compete with Mattermost or Rocket.chat for self-host for small organizations - but I'm really happy to see this thing open sourced! I much prefer it to be o…

(Gitter Co-founder here) Unfortunately our neo4j setup as it stands really doesn't scale. At an application-level we're built error-handling to gracefully handle the frequent outages we experience running it. These are probably our fault, rather than a failing in the product, but I've wanted to replace the current neo4j-based suggestion algo with a new one that uses batching/clustering for a while. As soon as I get a…

Post by onlinemantas » Tue, Jul 04, 2017, 2:08 PM UTC

mydigitalself wrote: post #60

richardknop wrote: post #50

Gitlab UI is truly horrid compared to Github. When I go to a repository page on Gitlab, the navigation and whitespace takes around 80% of my screen. On Github I can immediately see the directory structure. Also the colour scheme is bad IMO, everything is a light shade of grey, hard to quickly navigate the page as things look all the same while scrolling. Try using some darker shades and more contrast to make differen…

We're actually completely overhauling the GitLab's UI https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

Post by suprememoocow » Tue, Jul 04, 2017, 2:20 PM UTC

scaryclam wrote: post #88

suprememoocow wrote: post #73

Earlier quoted context omitted.

Gitter co-founder here: we use neo4j for suggesting rooms. So, if you're in room A and room B, and most people in those two rooms are also in room C, then we suggest that you join room C. As I mentioned elsewhere, we also use some non-neo4j based methods for suggestions (including your GitHub graph). One of the problems we've had with neo4j is that we haven't been able to make it scale. It frequently burns up from be…

Sounds like you're going to be doing a lot of writes, which neo4j isn't designed for. While I get why you're using it, I'd suggest that it's not really the right tool for that job, which is possibly why you're having problems with it. Do you really need persistance at all? If the application crashes everyone would be kicked out of the channels anyway no? I think making an in memory graph and ditching the graph DB ent…