Gitter is a communication product for communities and teams on GitHub. Find out more at gitter.im.

Navigation

Gitter + GitLab = win

Hello everyone, amazing news today, Gitter has been acquired by GitLab. Wow! Before getting into the details, we’d like to thank the 800,000+ people who make up the Gitter community for your enthusiasm and support for everything we’ve done. You’ve inspired our tiny team to keep shipping and making the open source and developer community a better place to connect to one another. Gitter will continue to operate as a standalone network…

Join the Dark Side

Today we are rolling out some changes to our UI. For those that haven't already played with it, you'll notice it's very white. We appreciate that a lot of developers like working in darker environments and so we've introduced a dark theme. In order to enable the new theme go to the Profile menu - click on your display picture in the top right section and toggle Dark Theme. Try it out for yourself. The new…

Say Hello to the new look Gitter

Hi there. Today we're launching an updated look for Gitter. It's cleaner, simpler and makes the popular All conversations view and direct messages more obvious and usable. TLDR: Try it out here. It's only the web and desktop versions that have changed, the mobile application and mobile web bits are still exactly the same. You can switch it off here. To enable it for your desktop version, take a look at this Topic. After reworking the…

Introducing Gitter Topics

We all 💜 a good chat - but do you ever feel there’s a little something missing from the conversation? We've decided to fill this gap, and over the coming weeks we’re enabling a new feature - Topics. Topics brings more structured conversations and content to your community. You can use it for forum-like questions and answers, FAQs that allow users to interact and discuss together - or whatever else you like! Whenever you've got…

Drop Database Migration in Core Data

Core Data supports migrating persistent stores (databases) from one model (schema) to the next without losing the existing content. It involves keeping versions of your model and the required mappings between them. However if you have a REST based app, then you are probably fine with not having to migrate the user's content as you can just fetch it all again from the server. You can do this in a surprisingly simple way (just make sure…