Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Matrix 2.0: The Future of Matrix

matrix.org

Post reply on HN
Print view View original

191–200 of 283 posts

Re: Matrix 2.0: The Future of Matrix

#191

Post by jwrallie »

abdullahkhalids wrote: post #10

Is Matrix simple enough now that I can invite my grandpa/grandma and they will be able to join? How does ease up sign up and use compare to discord? Assume that I make the choice of which client to direct them to.

It may not be easier than other proprietary stuff, but it is easy enough and probably the easiest you can get from the free software side.

Just install Element on iPhone or Android and make a matrix account from there, then add each other by the selected username.

You will only have to help your grandpa when you start to add secondary devices that need to be authenticated the first time with a QR code (for decryption purposes).

I have been using Element to text my wife for around 6 months (Android to iOS). I took the opportunity when she was getting notification issues with a proprietary app to convince her to use it. She loves it now. Clean interface, no ads, and voice call works just fine for us.

Re: Matrix 2.0: The Future of Matrix

#192

Post by COGlory »

Arathorn wrote: post #127
notsahil wrote: post #124

Synapse already eats up lots of space, adding sliding sync will boost it up and will be difficult to self-host it.

Yup, it's true that sliding sync proxy increases disk space further, although it's not so bad. A big advantage once it's stable and merged into a native homeserver will be reducing the storage duplication between the proxy and the HS. Meanwhile, we really need to get https://github.com/matrix-org/rust-synapse-compress-state/pu... hooked up in Synapse so that it automatically compresses state; I don't know why this ne…

I just went through a HUGE pain in the ass with my homeserver. I was on the Hetzner cloud plan and at the highest storage tier already. I had about 80 GB free, and setup sliding sync. It filled up the remaining space (unbeknownst to me) and my homeserver stopped working. Fortunately I was still able to login, but no disk space was available for the Postgres vacuum. I wound up having to rsync everything over to my desktop, setting up Docker on my desktop, running the compression tools on my desktop, and re-uploading. I now have a 20GB dummy file on that server.

Re: Matrix 2.0: The Future of Matrix

#193

Post by xvilka »

Arathorn wrote: post #146
iptq wrote: post #141

exciting to hear! I only wish i had more time to contribute. Has there been any movement on migrating away from long polling (#475)? I didn't see anything about it in the announcements or comments despite such a big milestone

Low Bandwidth Matrix is the answer to that, and it’s currently on hold unless it gets funded: https://matrix.org/blog/2021/06/10/low-bandwidth-matrix-an-i... It might also get changed as part of Sliding Sync refinement.

Hopefully it will be the default once implemented. Everyone will benefit from compact protocol in the long run. Should have been done from the very beginning.

Re: Matrix 2.0: The Future of Matrix

#194

Post by mcronce »

Twirrim wrote: post #52
geek_at wrote: post #43

Earlier quoted context omitted.

I love the idea of matrix (synapse + element + mobile apps) and I have started moving my family there too but we had so many problems with notifications not being sent to the phone unless you actively open the app. There is a huge discussion about that on git and some can't reproduce, some can't get a single notification even though the apps notification checkmarks were all green. So it had a very very low WAF [1] an…

If any of those are android users, it may be down to the non-android standards friendly battery optimisation the manufacturer ship their devices with (e.g. Samsung, Huawei, OnePlus, Xiamoi, etc.) https://dontkillmyapp.com/ I've had more issues with missing notifications on my OnePlus than I ever had on my Pixel (I have list of reasons why I'll never buy Google hardware again, mostly coming down to their support). Mos…

Not disagreeing you, just adding a point...I self-host Conduit and use FluffyChat on my phone, with ntfy for push notifications. While that works great most of the time, I occasionally have to restrict ntfy because it'll get into some state where it destroys my battery... And push notifications obviously don't work at all in that state.

It's very unfortunate there isn't a privacy-friendly push notification mechanism built into Android that doesn't ruin battery life. Or iOS for that matter; that might actually be a feature that would get me to switch.

Re: Matrix 2.0: The Future of Matrix

#196

Post by cycomanic »

amstan wrote: post #74
xorcist wrote: post #64

Earlier quoted context omitted.

Is it really that simple though? Jabber tried to be smart about which device to ring, and sometimes someone ended up with a missed notification. I always felt gutting that complexity and ring all instead would have been the more robust way.

So you consider your phone vibrating loudly on your desk for every recieved message while you're actively chatting and reading the same message on your desktop a correct implementation?

Well slack doesn't even send me the messages to my desktop continuing to send to my phone (which continues to buzz) despite me writing on the desktop, just because I send a message on my phone 10min ago.

So it might not be that easy (if even slack with their funding can't get it right).

Re: Matrix 2.0: The Future of Matrix

#197

Post by sfink »

dmix wrote: post #169

Does anyone use Matrix/Element for a serious workplace, instead of something like Slack?

We use Matrix (mostly via Element) at Mozilla alongside Slack. It's mainly public stuff on Matrix, and the usage pattern varies between teams: some teams are mainly Slack and barely pay attention to Matrix rooms, other teams (like mine) kick and scream if they're forced to use Slack for anything but internal corporate purposes. New hires in such teams tend to assume Slack initially and gradually notice that they get very slow responses on Slack, and then switch mainly over to Matrix to talk to the rest of us.

It's been good to us. Note that our primary comparison point is IRC, not Slack, mainly because of our project roots of openness and widely distributed contributors. So it's a serious workplace, but an atypical one. Encryption has periodically caused problems. Leaving the company and maintaining access to your communication seems to be a bit painful. Search is not great. Threads are tolerable. Inviting outside people in works well. Abuse is vastly more manageable than it was on IRC. Performance is mostly good. Both Element Web and Element on Android are very usable. Notifications are a little wonky, but I don't rely on them much so I can't really gauge whether they're good enough if you do.

Re: Matrix 2.0: The Future of Matrix

#198

Post by tentacleuno »

Arathorn wrote: post #116
whiterock wrote: post #115

my biggest struggle with matrix, is that, at least in element-ios, messages keep transpositioning, i.e. at some random time a message that is 2 days old is pushed all the way down to the new messages. also the aop frequently crashes with some media. but apart from that I of course love the idea of an „SMTP approach“ to instant messaging :)

this is literally why we rewrote element-ios in rust, in the form of Element X iOS :) https://element.io/labs/element-x

Why not fix the issues with the current implementation as well as rewriting it?

Re: Matrix 2.0: The Future of Matrix

#199

Post by rovr138 »

Arathorn wrote: post #114
rovr138 wrote: post #73

Earlier quoted context omitted.

Until there's an incompatibility, upgrade, exposure, memory overflow, or some other security issue/exploit. Unless you're saying that it's immune to everything and will never experience a change or issue.

I'm pretty sure that all those issues will affect sliding sync whether or not it's integrated in Synapse. In fact, some people might actually prefer the fact they can operate it separately and restart/maintain it separately from their homeserver :)

> I'm pretty sure that all those issues will affect sliding sync whether or not it's integrated in Synapse.

Of course.

My argument isn't that it won't happen, it's exactly the opposite, that it will. My point is that, now you need to manage 2 things vs 1.

> In fact, some people might actually prefer the fact they can operate it separately and restart/maintain it separately from their homeserver :)

Of course. But it's misleading to say that it won't require maintenance (which is what I replied to).

Re: Matrix 2.0: The Future of Matrix

#200

Post by mycall »

Macha wrote: post #188
Arathorn wrote: post #140

Earlier quoted context omitted.

Element X works pretty well on macOS as a desktop client if you have an Apple Silicon Mac. Otherwise, the big Element Web rework is yet to happen. On Android, I can almost guarantee your bug will be fixed: Element X Android doesn’t share any code with Element Android at all, as far as I know (given the former is mainly written in Rust, and the latter is all Kotlin)

This is the second time you've rewritten the Android app with Riot -> RiotX/Element -> ElementX. Just wondering why you throw it away rather than improve it, and if you're at risk of replacing one set of bugs with another?

Probably from too many mistakes and/or new maintainer and/or better ways to do it. Same as it ever was.
Post reply on HN