element-

Discover this repository through its Hacker News conversations.

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 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 hour2 dated mentions

Observed mentions: 2021-01-17 17:53:07 UTC to 2021-01-17 18:14:21 UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jan 17, 17:00	2021-01-17 17:00:00 UTC	2021-01-17 18:00:00 UTC	1	0	1
Jan 17, 18:00	2021-01-17 18:00:00 UTC	2021-01-17 19:00:00 UTC	1	0	1

What Hacker News says

2 sources

interestica·Jan 17, 2021

> If anyone in the "I tried Matrix and it was awful" camp could give detailed feedback (either here, or on github.com/vector-im/element-{web,ios,android}/issues) then it would be genuinely useful for prioritising our work. At the moment the vast majority of negative feedback on HN has been "it sucked" without giving a hint of what actually went wrong. Your two modes of suggested contact (HN, GitHub) ensure only a certain type of user will contact (both require tech skills and a login). If there really are UX issues, you might want to encourage different types of users to give feedback (and if the fear is that the feedback won't be detailed/useful, maybe a guided form can help).

In We can do better than Signal

Arathorn·Jan 17, 2021

Speaking as project lead for Matrix (and Element), I'm trying to understand the mixed feedback we've had this week, and somehow channel all the negativity into improving things. While some folks are clearly using it successfully and seem to like it, another bunch of people say "it was a huge pain in the butt to get E2EE working, and if it two software engineers struggled this much..." etc. When did this E2EE failure happen (so I know if these are current bugs or ones fixed months/years ago)? What platforms was this (web, iOS & Android are entirely separate codebases)? What actually went wrong? The simple case of signing up and DMing someone should just work, and the E2EE should be transparent. The main possible failure modes I'm aware of right now are: * Risk of undecryptable messages during federation outages (due to messages being sha

Read the rest

red separately from their keys) * Risk of verifying another user getting stuck if there are weird failures/edge cases we haven't spotted yet * Verifying yourself when you log in on a new device has confusing UX, and there's a known bug that can stop keys being synced to the new login even once verified. If anyone in the "I tried Matrix and it was awful" camp could give detailed feedback (either here, or on github.com/vector-im/element-{web,ios,android}/issues) then it would be genuinely useful for prioritising our work. At the moment the vast majority of negative feedback on HN has been "it sucked" without giving a hint of what actually went wrong.

In We can do better than Signal