Live data from Hacker News

The Matrix Space Beta

matrix.org

91–95 of 95 posts

Re: The Matrix Space Beta

#91
post #61

Earlier quoted context omitted.

I wish Matrix would instead focus on fixing all the existing encryption usability issues instead of these new features: https://github.com/vector-im/element-web/issues?q=label%3AA-... I would love to migrate my family to Element (and also friends, and eventually also recommend it to employers if they're ever choosing something other than Teams) but can't until it's reliable as webmail. I also wrote this comment: http…

So there is a finite number of active contributors to Element, and we have to prioritise what to work on. While E2EE is not perfect (the UX needs another major iteration and we are still hunting rare edge cases where messages cannot be decrypted) in practice it's usable day to day. We consciously chose to prioritise building out Spaces over the last few months over E2EE UX as otherwise there's a risk of Discord becom…

I'll just say; both of these seem like buckets of good priorities. I too wish some aspects of the onboarding were simpler, but I also am very very excited about Spaces, and have a number of communities I'm stoked to onboard once that feature launches.

Kudos to you and the team and I've been really enjoying tracking your progress over the last ~4 years.

Re: The Matrix Space Beta

#92

Earlier quoted context omitted.

Did you maybe post the wrong link? The comment you're linking to says that there are no current plans to change the default request to matrix.org from the login page, and that you explicitly plan to keep the current auto-updating behavior. (also, of course "we will fix that" implies that it is currently still broken, which is what the original commenter was pointing out)

The comment i linked is me saying: > we're going to fix this, and yes, imo, autoupdates need an opt-in. i'm not sure how clearer i can be.

When can I install and run a matrix client without it connecting to you? I want to use your software but want to self-host it and not use any services whatsoever from your organization.

Re: The Matrix Space Beta

#93

Earlier quoted context omitted.

Did you maybe post the wrong link? The comment you're linking to says that there are no current plans to change the default request to matrix.org from the login page, and that you explicitly plan to keep the current auto-updating behavior. (also, of course "we will fix that" implies that it is currently still broken, which is what the original commenter was pointing out)

The comment i linked is me saying: > we're going to fix this, and yes, imo, autoupdates need an opt-in. i'm not sure how clearer i can be.

The comment you linked says:

> As should be pretty clear from #11655 (comment), we're going to fix this, and yes, imo, autoupdates need an opt-in.

The comment #11655 says:

> Auto-updating for default Riot distributions will continue as before to ensure security fixes are delivered quickly

So at this point already it becomes unclear to the reader which of these has precedence.

So, assuming you're asking in good faith, if you wanted to be clearer you should have written something like:

"*Despite* what's written #11655 (comment), I disagree with the product teams assessment and think autoupdates need an opt-in, therefore I will make sure this is implemented."

(not sure if the content is 100% what you wanted to express in the comment, but you get the idea)

Re: The Matrix Space Beta

#94
post #61

For what it’s worth, the thing I find most exciting about Spaces is that they provide a decentralised hierarchical namespace with decentralised access controls for every room (ie pubsub topic) in Matrix. So it’s like we’ve sprouted an openly federated global hierarchical filing system for freeform realtime data streams of all flavours - where people can go crazy defining their own trees, applying their own curation i…

I wish Matrix would instead focus on fixing all the existing encryption usability issues instead of these new features: https://github.com/vector-im/element-web/issues?q=label%3AA-... I would love to migrate my family to Element (and also friends, and eventually also recommend it to employers if they're ever choosing something other than Teams) but can't until it's reliable as webmail. I also wrote this comment: http…

I'd love to see those encryption usability issues fixed, but I do want to say that e2ee on Matrix is less bad than on anything comparable (like OMEMO on XMPP). I like XMPP because of its speed, but you really can't combine OMEMO and multi-device unless you just don't mind having parts of your message history unreadable on some devices. The key backup and session validation in Matrix/Element usually solves this issue.

Unfortunately, the complexity means that even other Matrix clients that support e2ee don't support key backup and session validation, which means you either stick to Element on every platform, or live with the same history issues as on XMPP.

Re: The Matrix Space Beta

#95
post #4

Wohoo! Thanks to Spaces, I feel comfortable using Cactus comments for blog posts (e.g: https://viccuad.me/blog/enabling-cactus-comments ), as I could create a private space containing all the rooms for each blog post comment chain. To me it shows the snowballing effect of features. Also, Matrix's Spaces (even in Beta) seem more flexible and thought out than the second best implementation I know, in Slack.

Based on your comment, I tried this and it is working. Thanks.

Are you adding the each blog post comment room to a private space manually or is there way to automatically add it to that space?

Post reply on HN