20 Apr 2022 |
nephele | => unsuited for mobile connections | 15:00:54 |
nephele | I know the reference implementation for the ircv3 server in go (forgot the name...) also supports this | 15:01:14 |
val | that's Ergo (formerly Oragono) | 15:01:39 |
nephele | but still, that you can spin up a server in theory that has /almost/ all things to be suited for mobile does not imply that irc generally is suited for a mobile connection | 15:01:41 |
val | and I did say that "you don't need a persistent connection with modern server + client" | 15:01:54 |
nephele | > that's Ergo (formerly Oragono)
Huh? why does it say you need to talk to nickserv then? I just enabled that in the config when i used it... | 15:02:16 |
nephele | > and I did say that "you don't need a persistent connection with modern server + client"
it's not any less or more modern because it implements it differently | 15:02:34 |
nephele | since there is no ircv3 spec to mandate this stuff (atleast none i can find) it is not any functionality that can be relied on | 15:02:58 |
val | fair | 15:03:29 |
nephele | for now I'm using biboumi... which is the other way around, exposing irc networks to xmpp :) | 15:03:58 |
nephele | although iOS mobile clients for xmpp are also pretty bad | 15:04:07 |
nephele | well, so are the matrix clients... everything sucks i guess | 15:04:20 |
val | ircv3 is working on it, but it's really slow because almost everyone involved is a volunteer | 15:04:47 |
nephele | Yeah, i like ircv3 | 15:04:59 |
nephele | it's nice. | 15:05:04 |
nephele | It also pisses me off that matrix-appservice-irc seems to implement the lowest possible subset of irc only | 15:05:22 |
nephele | probably to make the bridge annoying enough to force people to migrate, i guess | 15:05:34 |
val | that's a policy decision, they don't consider it a priority | 15:05:40 |
val | (can't remember the exact link, but they told me on github they don't have time for it) | 15:05:59 |
nephele | sure they don't... | 15:06:08 |
val | I prefer to assume good faith | 15:06:19 |
nephele | For beeing a protocol to bridge everything matrix sure is terrible at bridging though | 15:06:30 |
val | yeah | 15:07:08 |
Nico | In reply to @nephele:nheko.im For beeing a protocol to bridge everything matrix sure is terrible at bridging though Not really, Matrix has much more and better bridges than other protocols imo | 15:07:16 |
Nico | All the irc <-> something other bridges are terrible | 15:07:34 |
nephele | turns out mapping stateless protocols to a statefull one doesn't really work out to well | 15:07:34 |
val | message length and forbidding newlines limits would go a long way toward making bridge users not so annoying to IRC users, but they refused to do that: https://github.com/matrix-org/matrix-appservice-irc/issues/701#issuecomment-430655719 | 15:07:37 |
val | (I am told they may be reconsidering this policy, though) | 15:07:47 |
nephele | > In reply to @nephele:nheko.im > For beeing a protocol to bridge everything matrix sure is terrible at bridging though > Not really, Matrix has much more and better bridges than other protocols imo I don't know any good relevant bridge honestly | 15:07:51 |
Nico | In reply to @val:e2e.zone message length and forbidding newlines limits would go a long way toward making bridge users not so annoying to IRC users, but they refused to do that: https://github.com/matrix-org/matrix-appservice-irc/issues/701#issuecomment-430655719 They have planned to add that for a while now, but it isn't a high priority | 15:08:32 |