Live data from Hacker News

This Year in Matrix

matrix.org

91–100 of 109 posts

Re: This Year in Matrix

#91

This was truly a great year for matrix. Thanks to the whole team for making a dream about decentralized www come true! But I have a great pain with that bug: https://github.com/vector-im/element-web/issues/469 Everytime I’m fighting with myself to not be sarcastic when speaking about this issue, but I want to say I have hard time believing that Element could we a main communication platform for anyone without this be…

Weird; the reason we haven't prioritised it is in that in practice it doesn't seem to be a big problem? You don't get push notifs while you're active in the app itself, and the fact that i get push on my phone while also reading on desktop almost feels like a feature (I often read the msg first via push on phone before then going and hunting on it desktop, especially as Element Web's notification panel needs love).

I can second this, I love being able to answer quickly from my mobile (I type [actually swipe] faster on mobile). It's also amazing how the push notifications clear when read somewhere else, this is not to taken for granted, it's not implemented on most other chat apps and it's a huge advantage of Element imho, sometimes it's buggy¹ but it's easy better than not having it and only Telegram is better in this regard from my experience.

1. https://github.com/vector-im/element-android/issues/4147 and also some other

Re: This Year in Matrix

#92
post #87

I have been through two unsatisfactory home servers (librem and privacytools) and am trying to decide what to do next, maybe even self-host. In the meantime, Signal :--P Whatever I step to, I will need to get my extended family onto it, and that is a big enough hassle I don't want to repeat another move.. I saw that, E2E notwithstanding, your home server has plaintext access to all traffic, which makes me leery of us…

*up

Re: This Year in Matrix

#93

Can I use separate identities in the same Element instance yet? Especially with Spaces I feel like this is an obvious feature where it should be easy for people to protect their privacy by using different accounts for different hobbies or peer groups. I would love to finally be able to use my employer's chatrooms with my real name, the animal rights group with my one pseudonym and the techie chat with the other one.

I'd actually prefer the focus to be having a better UI to change your display name for every space/room. What remains public then is very limited and that should be a much better experience than changing accounts every time (I use this heavily with Telegram Plus - 4 users and it's super annoying). I'm ok with my username being public...

Re: This Year in Matrix

#94

Earlier quoted context omitted.

I use conduit to run multiple rooms, read receipts have been working just fine.

Do bridges such as the discord puppet bridge work?

I'm not sure about that one, but most bridges should work, see https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.m...

Re: This Year in Matrix

#95

I have been using matrix for quite a while now, and managed to get the people I write the most with on it too! Back then I rented matrix hosting with modular.im (now called ems) once I noticed that I did use Riot/Element on a daily basis, and the latency of matrix.org servers was too big for my taste, combined with the lack of online status display. Now that dendrite is starting to finally mature, I will probably swi…

A migration guide would be much appreciated. I'd also like them to name homeserver.yaml in the Synapse Debian package to something akin to homeserver.example.yaml so that updates don't make me have to diff changes to figure out what I need to add (since accepting the package version overwriting my homeserver url is unacceptable). But that's neither here nor there.

I asked about migration guide in the chat a couple weeks ago. Found 2-3 on random internet sites that made it sound too easy - so I was expecting some gotchas to be mentioned, but got crickets.

I will be trying to migrate to a new server at different host/data center in about a week - hope it's as simple as the base guides I bookmarked make it sound.

Definitely would love an official guide and some kind of check things script maybe - but we'll see, maybe it's not too hard - dunno yet.

Re: This Year in Matrix

#96
post #81

I still can't believe there's been no response to the nickname colour proposal. This has been sitting in the queue for 2!!!! years now. It's ridiculous.

This has been high on my priority list as well.

Last I checked we needed a git account o upvote things or something - but even then I'm not sure we'd get a change in the roadmap / prioritization... I've considered hiring some peeps to make the code and offer it up to the community ti merge it or whatever. This and a few other important to me/my users, but really kind of superficial things in general that needs to attention imho.

Re: This Year in Matrix

#97

Earlier quoted context omitted.

I want to voice strong agreement with kevincox. I use an encrypted Matrix room daily and had no idea that reactions, relations (does that mean that edits are in cleartext??), etc are completely unencrypted. I've read a little bit of the spec (though clearly not very much), I've written a bot, I've patched the Element desktop client, I've even been working with a JSON export of my message history and didn't notice—per…

Is it really that surprising that the act of reacting to a message with an emoji isn't E2EE, given the server needs to count the number of reactions? One could encrypt the emoji itself, but it doesn't seem like a massively sensitive datapoint in its own right. (That said, we will encrypt them eventually, but it's just not very high priority given the fact it doesn't practically feel very high impact, relative to all…

Yes, this is very surprising to me. I would've thought that all stuff I do in chat is end-to-end encrypted.

Is this not the case for e.g. Signal reactions?

Re: This Year in Matrix

#98
post #10

I tried to adopt matrix for our small business and here is summary of my experience. - Synapse is very resource hungry even for a small server - Synapse creates a gazillion of TCP connection and keep them open, it was a real problem for my ISP router (SOHO router for 1gbit/s) and it took a very long time to debug, be sure to limit the number of TCP connection on the server - Synapse is hard to get a good idea of the…

Synapse is bloated and mostly good for very large organisations. Use conduit.rs or dendrite. I use conduit and it takes a couple of MB ram even while I’m in large rooms

Heads up for anyone thinking about trying out a homeserver or two. To my knowledge there is no way of moving from one piece of homeserver software to another. So for example if you start with conduit you're stuck with it. I think there are a bunch of plans all over the place to mitigate this, but I don't think they're there yet.

Re: This Year in Matrix

#99
post #42
post #31

Earlier quoted context omitted.

> federation issues > gazillion TCP connections We’ve been running a Synapse server with quite a bit of federated rooms, even larger ones like you mention. Never noticed a single issue like this that I recall. I wonder if the reason is that we’re doing whitelisting, instead of federation with everyone by default. The whitelisting is quite liberal; I’ll add a server as soon as I’m in a conversation thread with someone…

I didn't whitelist anything, maybe that was a source for issue. > Disagree. Sure, UX can be improved, but compromising here defeats the purpose of why we’re doing this in the first place. The thing is, as I ran my own server in my office, SSL (with no E2E) is already a good privacy. And even with that setup, the server users got "harassed" by the UI asking them to sync devices keys. For many users, a single prompt ab…

> I didn't whitelist anything, maybe that was a source for issue.

Should have mentioned: I think my approach works fine for single-user or small-closed-community servers. Nobody should do this on servers with public rooms and/or open registration as it will lock out minority servers and cause further centralization.

Re: This Year in Matrix

#100
post #69

Earlier quoted context omitted.

Tried Matrix (and Synapse) the 3rd time a couple of months ago and gave up after a few days. Joining any larger federated room took days or did not complete at all. And then the messages were also delayed for quite a while. That must be the stupidest design I have seen. If it was not so messed up, Matrix probably would have become huge by now. I agree with others in comments, devs should have probably improved the fe…

It might be worth reading the actual post to see how we're fixing slow joins. In terms of the language: it's not Python's fault at all. Instead, Synapse baked in a bunch of naive assumptions (being originally a prototype) which we have been steadily fixing... while also adding features, which pulls in the opposite direction. Given a choice between a featureful server that's resource-heavy (which we can then make go f…

Sorry, it was not clear from my comment. I do not blame Python. Of course it was design/code issue.

I just think that having a single binary would improve adoption. I like projects that provide a single binary. Without the need for docker, or setting up complex environments.

Post reply on HN