HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kamax-matrix
mxhsd
Java2019–2019
kamax-matrix / mxhsd · Archived

mxhsd

Corporate Matrix Homeserver

2Distinct people
4Mentions
0Explicit recommenders
29GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Corporate Matrix Homeserver

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:03:16 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 6-hour interval4 dated mentions

Observed mentions: 2019-03-18 01:54:09 UTC to 2019-03-24 02:15:39 UTC.

0122019-03-18 00:00:00 UTC to 2019-03-18 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 18, 00:002019-03-18 06:00:00 UTC to 2019-03-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-18 12:00:00 UTC to 2019-03-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-18 18:00:00 UTC to 2019-03-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-19 00:00:00 UTC to 2019-03-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-19 06:00:00 UTC to 2019-03-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-19 12:00:00 UTC to 2019-03-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-19 18:00:00 UTC to 2019-03-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-20 00:00:00 UTC to 2019-03-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-20 06:00:00 UTC to 2019-03-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-20 12:00:00 UTC to 2019-03-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-20 18:00:00 UTC to 2019-03-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-21 00:00:00 UTC to 2019-03-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 21, 00:002019-03-21 06:00:00 UTC to 2019-03-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-21 12:00:00 UTC to 2019-03-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-21 18:00:00 UTC to 2019-03-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-22 00:00:00 UTC to 2019-03-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-22 06:00:00 UTC to 2019-03-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-22 12:00:00 UTC to 2019-03-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-22 18:00:00 UTC to 2019-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-23 00:00:00 UTC to 2019-03-23 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-23 06:00:00 UTC to 2019-03-23 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-23 12:00:00 UTC to 2019-03-23 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-23 18:00:00 UTC to 2019-03-24 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-03-24 00:00:00 UTC to 2019-03-24 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 24, 00: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 18, 00:002019-03-18 00:00:00 UTC2019-03-18 06:00:00 UTC101
Mar 18, 06:002019-03-18 06:00:00 UTC2019-03-18 12:00:00 UTC000
Mar 18, 12:002019-03-18 12:00:00 UTC2019-03-18 18:00:00 UTC000
Mar 18, 18:002019-03-18 18:00:00 UTC2019-03-19 00:00:00 UTC000
Mar 19, 00:002019-03-19 00:00:00 UTC2019-03-19 06:00:00 UTC000
Mar 19, 06:002019-03-19 06:00:00 UTC2019-03-19 12:00:00 UTC000
Mar 19, 12:002019-03-19 12:00:00 UTC2019-03-19 18:00:00 UTC000
Mar 19, 18:002019-03-19 18:00:00 UTC2019-03-20 00:00:00 UTC000
Mar 20, 00:002019-03-20 00:00:00 UTC2019-03-20 06:00:00 UTC000
Mar 20, 06:002019-03-20 06:00:00 UTC2019-03-20 12:00:00 UTC000
Mar 20, 12:002019-03-20 12:00:00 UTC2019-03-20 18:00:00 UTC000
Mar 20, 18:002019-03-20 18:00:00 UTC2019-03-21 00:00:00 UTC000
Mar 21, 00:002019-03-21 00:00:00 UTC2019-03-21 06:00:00 UTC000
Mar 21, 06:002019-03-21 06:00:00 UTC2019-03-21 12:00:00 UTC000
Mar 21, 12:002019-03-21 12:00:00 UTC2019-03-21 18:00:00 UTC000
Mar 21, 18:002019-03-21 18:00:00 UTC2019-03-22 00:00:00 UTC000
Mar 22, 00:002019-03-22 00:00:00 UTC2019-03-22 06:00:00 UTC000
Mar 22, 06:002019-03-22 06:00:00 UTC2019-03-22 12:00:00 UTC000
Mar 22, 12:002019-03-22 12:00:00 UTC2019-03-22 18:00:00 UTC000
Mar 22, 18:002019-03-22 18:00:00 UTC2019-03-23 00:00:00 UTC000
Mar 23, 00:002019-03-23 00:00:00 UTC2019-03-23 06:00:00 UTC000
Mar 23, 06:002019-03-23 06:00:00 UTC2019-03-23 12:00:00 UTC000
Mar 23, 12:002019-03-23 12:00:00 UTC2019-03-23 18:00:00 UTC000
Mar 23, 18:002019-03-23 18:00:00 UTC2019-03-24 00:00:00 UTC202
Mar 24, 00:002019-03-24 00:00:00 UTC2019-03-24 06:00:00 UTC101

What Hacker News says

4 sources
As the author of mxhsd [1] and Gridepo [2], I can sadly confirm Jason's claims that it is STILL necessary to reverse engineer to talk to the existing federation. Synapse doesn't follow the spec, which is a fact I'm experiencing every day. But more to that, there is no desire from its developers to ever comply with the spec, rather than changing the spec on a whim. And that are the reasons why making a HS is not possible: endless moving target. [1]: https://github.com/kamax-matrix/mxhsd [2]: https://gitlab.com/kamax-io/grid/gridepo
In Matrix 1.0 – Are We Ready Yet?
I am the author of the now-frozen mxhsd project [1] and its resurected version, Gridepo [2]. I have contributed several times to the specification, reported issues for the past two years and still, to this day, I can confirm that it is not possible to implement a Matrix server with the current specification that can talk to the reference implementation. Most fundamental problem: synapse doesn't sign the events like the spec tell us to do it, making every event invalid. Whatever you sent that is spec compliant will be refused by synapse. So talking "synapse" is possible. Talking Matrix and be able to federate with the ecosystem is not. I wish people would not blindly believe what a for-profit is saying, especially one that is in full control of the said protocol, and start checking for themselves. [1]: https://github.com/kamax-matrix/mxhs
Read the rest
In Matrix 1.0 – Are We Ready Yet?
It seems like a few folks have been burned by the failure to put the spec before the implementation. Another example: Kamax provides mxisd[1], the only federated identity server (the official identity server is/was controlled by vector, and doesnt openly federate). They had to give up on mxhsd[2], their home server implementation due to spec inadequacies, and ended up forking the spec into Grid[3] [1] https://github.com/kamax-matrix/mxisd [2] https://github.com/kamax-matrix/mxhsd [3] https://gitlab.com/kamax-io/grid/gridepo
In Matrix 1.0 – Are We Ready Yet?

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.