Does IRCv3 need new leadership to continue to drive it forward? Over at Parley/Ahoy (https://git.mills.io/prologic/parley https://git.mills.io/fastidious/ahoy) we've managed to create a federated decentralized IRC chat experience with a Discord/Slack-esque feel but true to both IRC / IRCv3 (Ahoy being a fully featured IRCv3 client).

▲

WhyNotHugo an hour ago | parent | next [-]

Rather than claim a Discord-esque feel, you should point out the features you're referring to explicitly. Discord is infamous for its absolutely awful UX and hostility to open source ecosystem. I'm sure you're referring to neither of those aspects, but consider that those reading your reference might be entirely unfamiliar with the (presumably) positive aspects that you're actually imitating.

▲

prologic an hour ago | parent [-]

You are right. To be perfectly honest, the only thing I took from Discord at all (it's UI is generally awful yes, I agree!) is the support for multiple servers. But now that I think about it some more, that's not really even a unique feature.

Anyway, you are right. But that's more about Ahoy and less about Parley. Parley was just answering the question of "What if IRC was federated, and what if it borrowed some ideas from Salty.im -- DNS discovery + WKID".

▲

itintheory 24 minutes ago | parent [-]

Wasn't IRC always federated? There were different networks, but each network was a federation of independent servers.owmed by independent operators as far as I understand...

	▲	prologic 11 minutes ago \| parent [-]
		I don't believe so, not in the strictness sense. > A federated network is a system where independent networks, servers, or organizations agree to follow common standards so they can talk to each other without giving up control to a single central company. In traditional IRC networks, you end up forming a spanning tree of servers that belong to a common name, "the network". However control remains in the hands of the operators of that network.

▲

SaberUK 39 minutes ago | parent | prev | next [-]

IRCv3 isn't a corporate body, its a semi-formal group of IRC developers. There's nothing prohibiting you from proposing protocol extensions if they are within the scope of the working group.

▲

obsoleszenz 2 hours ago | parent | prev [-]

parley and ahoy both look quite interesting! Retrofitting irc into a real federated protocol is cool. Also like the idea of picking up discords ui/ux. How did you manage to get avatars for ahoy? Is there a ircv3 protocol i missed?

	▲	prologic 2 hours ago \| parent [-]
		It's part of the IRCv3 Metadata spec: https://ircv3.net/specs/extensions/metadata -- It just isn't very well documented or prominently displayed on the spec's page(s) I think. Took me a while to find it too.