@alexchapman @keao @jackf723 @munchkinbear Why start with a custom solution anyway if the eventual goal was XMPP? Just do that from the start and save everyone any migration hell, because there will be migration hell
@alexchapman @keao @jackf723 @munchkinbear Why start with a custom solution anyway if the eventual goal was XMPP? Just do that from the start and save everyone any migration hell, because there will be migration hell
@munchkinbear @ky0les Not sure how I feel about new messaging service 104296. Seems like this could be rife for drama, leaked info, and god knows what else.
@fireborn @munchkinbear @ky0les That's not gonna happen, its not like Elten and its shitty design and developer who hardly gives a shit.
@alexchapman @munchkinbear @ky0les Certainly an 'I’ll believe it when I see it' moment.
@fireborn @munchkinbear @ky0les Well, I'm not Pajper, I'm Alex, and Stu is working on it with me, so yeah, its not gonna end up like Elten, its actually gonna work in the long term.
@alexchapman @munchkinbear @ky0les Best of luck. I will believe it once it has some traction and documented protocol spec.
@alexchapman @fireborn @munchkinbear @ky0les Well and if it does gain xmpp support, then this will turn into a really well-done multi-provider client such is the likes of Miranda NG (accessible but missing features) and Pigeon (POssibly outdated GTK, because inaccessible on Windows). There are some really good modern re-implementations of XMPP, consider Snikket https://snikket.org/ setup couldn't be simpler.
@jackf723 @fireborn @munchkinbear @ky0les Yeah, definitely considering Snikket and Procidy for XMPP implementation.
@fireborn @munchkinbear @ky0les Oh and yes, I called out Pajper because of how he never bothered to fix the glaring issues Elten has, and he lets it rot in its own shit.
@alexchapman @munchkinbear @ky0les To be clear, I mitht try it just because interesting, but my previous statements apply