SaaS24 Сравнение и обзоры вебсервисов
Логотип SaaS24

Официальный сайт

  1. Главная
  2. Сервисы
  3. Мессенджеры
  4. Gitter

Gitter · обзор, сравнение с аналогами

Звёзд: 1Звёзд: 2Звёзд: 3Звёзд: 4Звёзд: 5 (Пока оценок нет)
Логотип Gitter

Официальный сайт


Скриншот №1 страниц сайта Gitter
Скриншот №2 страниц сайта Gitter

Язык сайта

Интерфейс на русском языкеРусский Интерфейс на английском языкеАнгийский

30 сентября 2020
Gitter is moving to Element!

Yes! Another big move for Gitter! Gitter is being acquired by Element and will become part of the bigger Matrix ecosystem. Don’t worry, all of the Gitter things are staying around and we will continue to support your communities better than ever.

If you’re curious about what Element

04 мая 2020
Threaded conversations and GitLab based communities and rooms

After months of development we are proud to introduce two new major features: Threaded conversations and GitLab based communities and rooms.

Threaded conversations

Multiple conversations in a busy Gitter room can become hard to follow. Up until now the main way of keeping message context has been using Permalinks and

16 июля 2018
Gitter Topics Deprecation Notice

We introduced Gitter Topics in September 2016 as an experiment. Unfortunately, it never gained traction and remained in beta through its life-span. After some consideration, we've decided to deprecate and remove this underused feature, allowing us to focus on the chat application.

Topics will be completely removed from the Gitter

11 июня 2018
Gitter Token Leak Security Issue Notification

Issue Summary

A vulnerability in the Gitter desktop application resulted in an inadvertent leak of your Gitter tokens. This affects v2 and v3 of the Gitter desktop app which we officially distribute for Windows and Linux. This only affects macOS if you manually downloaded v2/v3 (we distribute v1.177

16 февраля 2018
Gitter XSS Crypto Mining Security Issue Notification

Issue Summary

An XSS exploit in our KaTeX parser was used to embed a JavaScript crypto miner in clients via an exploitative message.

The exploitative message was spread across 25 rooms and 146 users read those messages. The messages were available for about 1 hour (minutes after being reported) before

Наверх To top