Arathorn

19 ms·

331.
by Arathorn 2y ago
starting to wonder if it should be “Element acceleration libs for Synapse workers” or something instead.
332.
by Arathorn 2y ago
We didn’t rewrite the slow parts in Rust, we rewrote the bits which let large deployments scale (workers) in rust. Normal Synapse perf work will continue as ever, if not faster given it might have more funding. See https://news.y
333.
by Arathorn 2y ago
We stupidly thought they wouldn’t saw off the branch they’re sitting on. But they did.
334.
by Arathorn 2y ago
> It seems to me like this disqualifies Matrix from consideration for "public infrastructure" IMHO. Please don’t conflate Synapse with Matrix. Yes, if a govt has a “we must only spend money on pure open source products” policy
335.
by Arathorn 2y ago
> That the new Element mobile client only supports Synapse was a huge red flag. This is not true. Element X requires Matrix 2.0, which is currently only in Synapse because it has to land somewhere first. But Dendrite is implementing it (
336.
by Arathorn 2y ago
Only in as much as it’s slightly harder to write buggy Rust than buggy Python thanks to Rust’s better type safety and concurrency safety features, and there’s less unsafe native code in Rust libs typically. However FOSS Synapse already uses
337.
by Arathorn 2y ago
Thank you - and to the sibling comments too; the support is enormously appreciated. For what it’s worth, we have been frantically trying to keep all Synapse dev FOSS for the last 10 years - and the FOSS version will always be the primary pr
338.
by Arathorn 2y ago
I think the only reason Red Hat’s model works for them is that Linux distributions are obviously massive sprawling complex things, and maintaining LTS distros which you then sell support for is an incredibly complex and valuable thing that
339.
by Arathorn 2y ago
np, thanks for listening to my explanation and for the apology - sorry on my side for yelling. i’m terrified now that the various blog posts haven’t been clear enough about the plan though - seems like we should have made it much clearer th
340.
by Arathorn 2y ago
Presumably you’re using an overloaded server which is struggling because we have been completely undermanned on synapse maintenance and haven’t been able to do core optimisation work. This is precisely why we’re trying to fund our FOSS work
341.
by Arathorn 2y ago
> Or was Telekom one of many companies that did a similar thing? This. > However, I don't understand why they frame their Pro version in this way and point to failure instead of success. It’s really trying to spell out the risks
342.
by Arathorn 2y ago
You’ve totally misunderstood me - probably my fault; sorry. There is no trickle-down happening here: *these issues will be fixed directly in FOSS synapse, which is the core project*. They are nothing to do with rust worker implementations i
343.
by Arathorn 2y ago
Last I checked they ratelimit push notifications using a proprietary push gateway, unless you’re a paying customer.
344.
by Arathorn 2y ago
> Why bother with that anymore if we're just getting the "broken implementation"? You’re not. All work (other than stuff which primarily benefits scalability for enormous deployments) should land on FOSS Synapse - particu
345.
by Arathorn 2y ago
No, you have this completely wrong. The reason that small servers struggle today is not because their workers are written mainly in Python rather than Rust. Hell, they typically don’t run workers at all. The slowness comes from state res
346.
by Arathorn 2y ago
Matrix is an open protocol published by a non-profit foundation. It has always had both FOSS (eg Element) and proprietary (eg Beeper) implementations. You sound like you are getting Element mixed up with Matrix. Element releases almost all
347.
by Arathorn 2y ago
Matrix is an open protocol and is 100% open. Synapse is a server implementation of Matrix and is open source under AGPL. Synapse Pro is some alternative new worker implementations for Synapse designed to let enormous deployments scale rath
348.
by Arathorn 2y ago
No, not cancelled. Just not being developed with dayjob funding currently (as there is none). This isn’t the first time it’s been in that state, and it returned before: https://github.com/element-hq/dendrite/graphs
349.
by Arathorn 2y ago
The way I’m thinking of it is that Synapse (not to mention Dendrite) has been badly starved of development over the last few years due to the freerider problem nuking the $ available to support our dev as the upstream. By making only optimi
350.
by Arathorn 2y ago
> But it seems like this move incentivizes you to not improve the open source server, at least such that the open source server is always inferior to the pro version. The idea is that we absolutely improve FOSS synapse in all ways - othe
351.
by Arathorn 2y ago
not aware of a double notif bug - do you have a github issue for it?
352.
by Arathorn 2y ago
woah there - hang on a sec > No one's going to be happy running a 500x slower python project knowing there's the real deal running elsewhere, with a hip new runtime they can't get. What if the current python project got 50
353.
by Arathorn 2y ago
It looks like i've done a bad job at explaining this, so i'll try to clarify: Making worker processes go fast has most benefit to enormous deployments, as they won't run out of headroom when running lots of single-core python
354.
by Arathorn 2y ago
I wrote the OP, and this is very much the correct interpretation. I spelt out the problem more clearly here: https://mastodon.matrix.org/@element/113843808583376704 The issue is that large system integrators offer to
355.
by Arathorn 2y ago
Nope, it's not self-sabotage - the worker is sitting there consuming the events from redis, and then pulling in the dependent data from the DB and populating and maintaining its caches (and marshalling & unmarshalling the necessary
356.
by Arathorn 2y ago
Sounds like your homeserver is having problems, or authenticated media wasn't turned on right. If you can chuck a bug into github.com/element-hq/synapse/issues we'll look at it.
357.
by Arathorn 2y ago
> I know that Matrix these days has a lot of the same features but certainly is not there as far as convenience goes. For what it's worth, the whole Matrix community has been solidly plugging away improving convenience and making go
358.
by Arathorn 2y ago
> It's well known that a non-profit sitting close to a for-profit just is often just a structural maneuver at this point. A case in point is the recent WordPress controversy. I agree there. Which is why we have been separating Matri
359.
by Arathorn 2y ago
> There was clear deprioritization of the community, which to me doesn’t sound like good faith, by Matrix Foundation in closing the ecosystem. The Matrix Foundation has not “closed the ecosystem”! The ecosystem is healthier than ever - j
360.
by Arathorn 2y ago
> they built the community of Matrix and Element around a promise of openness but specifically chose a license to make it another Discord or Slack This is really unhelpfully inaccurate. Matrix is as open as ever - and run by the vendor-n

More ›