HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
HashNuke
mogo-chat
JavaScript2014–2014
HashNuke / mogo-chat · Archived

mogo-chat

Beautiful team chat app written in Elixir & Ember.js

Communication & Social
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
735GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Beautiful team chat app written in Elixir & Ember.js

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2014-03-26 13:48:07 UTC to 2014-03-27 06:59:41 UTC.

012014-03-26 13:00:00 UTC to 2014-03-26 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 26, 13:002014-03-26 14:00:00 UTC to 2014-03-26 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-03-26 15:00:00 UTC to 2014-03-26 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 16:00:00 UTC to 2014-03-26 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 17:00:00 UTC to 2014-03-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 18:00:00 UTC to 2014-03-26 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 19:00:00 UTC to 2014-03-26 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 20:00:00 UTC to 2014-03-26 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 21:00:00 UTC to 2014-03-26 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 26, 21:002014-03-26 22:00:00 UTC to 2014-03-26 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-26 23:00:00 UTC to 2014-03-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 00:00:00 UTC to 2014-03-27 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 01:00:00 UTC to 2014-03-27 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 02:00:00 UTC to 2014-03-27 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 03:00:00 UTC to 2014-03-27 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 04:00:00 UTC to 2014-03-27 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 05:00:00 UTC to 2014-03-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-27 06:00:00 UTC to 2014-03-27 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 27, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 26, 13:002014-03-26 13:00:00 UTC2014-03-26 14:00:00 UTC101
Mar 26, 14:002014-03-26 14:00:00 UTC2014-03-26 15:00:00 UTC101
Mar 26, 15:002014-03-26 15:00:00 UTC2014-03-26 16:00:00 UTC000
Mar 26, 16:002014-03-26 16:00:00 UTC2014-03-26 17:00:00 UTC000
Mar 26, 17:002014-03-26 17:00:00 UTC2014-03-26 18:00:00 UTC000
Mar 26, 18:002014-03-26 18:00:00 UTC2014-03-26 19:00:00 UTC000
Mar 26, 19:002014-03-26 19:00:00 UTC2014-03-26 20:00:00 UTC000
Mar 26, 20:002014-03-26 20:00:00 UTC2014-03-26 21:00:00 UTC000
Mar 26, 21:002014-03-26 21:00:00 UTC2014-03-26 22:00:00 UTC000
Mar 26, 22:002014-03-26 22:00:00 UTC2014-03-26 23:00:00 UTC000
Mar 26, 23:002014-03-26 23:00:00 UTC2014-03-27 00:00:00 UTC000
Mar 27, 00:002014-03-27 00:00:00 UTC2014-03-27 01:00:00 UTC000
Mar 27, 01:002014-03-27 01:00:00 UTC2014-03-27 02:00:00 UTC000
Mar 27, 02:002014-03-27 02:00:00 UTC2014-03-27 03:00:00 UTC000
Mar 27, 03:002014-03-27 03:00:00 UTC2014-03-27 04:00:00 UTC000
Mar 27, 04:002014-03-27 04:00:00 UTC2014-03-27 05:00:00 UTC000
Mar 27, 05:002014-03-27 05:00:00 UTC2014-03-27 06:00:00 UTC000
Mar 27, 06:002014-03-27 06:00:00 UTC2014-03-27 07:00:00 UTC101

What Hacker News says

3 sources
psycr·Mar 26, 2014
It seems that the room message state is synced via a poller, as seen here: https://github.com/HashNuke/mogo-chat/blob/master/assets/jav... I'm curious why you decided to implement this with a poller instead of with a Websocket. There's actually a reasonably detailed answer about how to do this sort of thing with Ember Data in the emberjs.com guides: http://emberjs.com/guides/models/frequently-asked-questions/... Either way, how did you find working with Ember Data in general? What were the main sticking points?
In Show HN: Mogo Chat – open-source team chat app written in Elixir and Ember.js
JangoSteve·Mar 26, 2014
Someone seems to have broken the demo by typing in some JavaScript. Doesn't seem to be sanitizing input completely. EDIT: Looks like it's CSS, not JS. In case it helps, here's what I'm seeing [1], and here's the code from the message: <style>* { float: left; display: block }</style> [1] http://imgur.com/BoZ6lrF EDIT 2: Yup, style tags don't seem to be escaped. Tried changing colors of the room a few times, and it worked: <style>* { color: green; }</style> EDIT 3: Issue filed here: https://github.com/HashNuke/mogo-chat/issues/2
In Show HN: Mogo Chat – open-source team chat app written in Elixir and Ember.js

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.