<samueldr>
oh, is -> the only operator where lhs can be "confused" as an identifier when no spacing is used?
<samueldr>
a->b is a- > b
Lisanna has joined #nixos-chat
obadz- has joined #nixos-chat
obadz has quit [Ping timeout: 256 seconds]
obadz- is now known as obadz
Synthetica has joined #nixos-chat
Synthetica has quit [Quit: Connection closed for inactivity]
<tilpner>
MichaelRaskin - right
thblt has joined #nixos-chat
<MichaelRaskin>
Well, the speed is not the issue
<tilpner>
But I can't help much, so...
<tilpner>
Right now I'm waiting for Dendrite :/
<MichaelRaskin>
The fun part is that I get some connection from matrix.org, but my server dislikes the signature
<MichaelRaskin>
(no problem with a different HS)
<MichaelRaskin>
My HS is behind nginx with 8448 unavailable and with a SRV record, but that shouldn't create differential problems
<tilpner>
If it helps at all, here's the module I used: tx0.co/E
<MichaelRaskin>
(of course my synapse is also not on NixOS)
<MichaelRaskin>
Hm… maybe I should install something from upstream tarball as opposed to pip
<tilpner>
You can still try to emulate what that module does, right?
<MichaelRaskin>
Well, I don't want to open 8448…
<MichaelRaskin>
(because I would need to ask for it)
<tilpner>
Oh :/
<MichaelRaskin>
I can, but I don't want to
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-chat
<MichaelRaskin>
By the way, tilpner, you say you don't run that appservice because you don't run HS — how much integration with HS do I need for AS? (my deep hope is to run TG/Skype AS locally and connect to a remote HS, so that the connection keys stay local)
<MichaelRaskin>
XMPP AS should probably go to the server which runs both XMPP and Matrix instances which I want to bridge
<tilpner>
I'm not 100% sure, but AFAICT you can run them on different machines, but the HS needs to be told about the AS (app_service_config_files)
<MichaelRaskin>
That does sound reasonable; does it need to be able to connect to it, though?
<tilpner>
If you to know for sure, ask #matrix
<tilpner>
*you want to know
<MichaelRaskin>
Or read the spec…
<tilpner>
Well... unfortunately the spec and Synapse don't always agree
<MichaelRaskin>
Ouch
<tilpner>
It bit the Ruma guys a few times
<tilpner>
And #matrix would know about future plans
<MichaelRaskin>
Ouch, pain
<MichaelRaskin>
Apparently AS must be visible
<ekleog>
MichaelRaskin tilpner: I don't have the context for your discussion, but did you do the 0.28.1 upgrade, for your issues of talking with matrix.org?
<ekleog>
MichaelRaskin: you can likely work around that by running a VPN between local and the HS, and having the HS talk to the AS over the VPN?
<MichaelRaskin>
It is my issue, and I did install 0.28.1, and nothing changed
<MichaelRaskin>
ekleog: I did think about it, although without always-on connection on the AS side I might hit exponential back-off
<MichaelRaskin>
With AS actively connecting to HS, the HS would know when AS is available
<ekleog>
oh :/ here we had a similar issue, but 0.28.1 fixed it
<MichaelRaskin>
After 0.28.1 my synapse still complains about invalid signatures from matrix.org
<ekleog>
also, for exponential back-off, I guess it depends on the implementation of the AS? as you want to keep keys local I guess you are the only user of the bridge, so so long as the AS is running messages in the HS->AS direction would only flow when the AS is up anyway
<ekleog>
s/as long as the AS is running/& when you try to use it/
<MichaelRaskin>
No, HS connects to AS, so AS implementation is irrelevant
<MichaelRaskin>
I think
<MichaelRaskin>
I am not sure if synapse would try to update last-seen for me if I just read the backlog with the AS off
<MichaelRaskin>
And whether this triggers the back-off for everything, including my later attempts to get fresh messages