flancian

@liaizon @wikipedia @FediverseChick do we have any hint thus far for who is actually behind the FC?

@Melatonin @CoderSupreme good questions!

I hadn't heard of Sharkey but I have [[Misskey]] filed under the same category as Mastodon: microblogging/blogging oriented. It comes from Japan and its community is Japanese-first last I checked. It's got several cool features that Mastodon lacks.

@copygirl @Dirk yes, I also get the feeling this would not work in a compliant setup but it seems like a good idea to test this in e.g. a federation test suite.

Maybe @evanprodromou would know how this should work, or would know of someone who might be testing this kind of scenario.

@Dirk @xelar thanks for your view, question: defederating with threads seems reasonable, but why would you defederate "second level" like this? I ask as the instance I'm in decided not to defederate with threads for now and I'm personally OK with that.

@lagomorphlecture @Oppawaifu what is the best lemmy client you think? or overall [[fediverse]] client?

@CrazyDuck of course moving to a proprietary protocol doesn't mean that federation must die. Indeed we kept federation alive for users for a while by bridging gTalk (legacy, still supporting federation) and Hangouts (proprietary). It was the dream of at least a few (myself included) to open up the Hangouts API and/or build federation on top of it, but it was not prioritized -- I take part of the responsibility for that, even if I was just an individual contributor: I could have done it as a 20%.

@CrazyDuck

3. XMPP was, back then, considered unfit for the transition to mobile as it was a very 'chatty' protocol and that kills battery on mobile devices. I've heard this has been solved/worked around since? But I haven't looked into how this was achieved, if at all, and whether we could have taken that route instead back then.

@CrazyDuck

2. Developers in the chat space in G had decided to implement their own protocol for Hangouts, the "next generation" chat app. The consensus seemed to be that going with an in-house protocol would provide enough extra freedom to allow G to implement and ship features faster (whereas innovation on top of XMPP was deemed relatively hard).

@CrazyDuck Yes, I believe so :) Of course this is just how I remember it, it reflects my opinions and not of my employer's, etc.

From my rough memory, around the time this happened in 2013 the following was true:

1. Federation was considered to be already languishing due to relatively little usage aside from big instances like AOL (who were going down in any case). Actual people running their own individual/community instances were relatively few, and a significant fraction were spammers :(

@CrazyDuck @confluence ahoy!

No, I don't think so? As far as I can tell all extensions were public, in particular Jingle: https://en.wikipedia.org/wiki/XMPP, https://en.wikipedia.org/wiki/Jingle_(protocol)

Disclosure: I worked on gTalk towards the end of its lifetime and was the person responsible for (sadly) turning down federation.