> Instead of re-inventing the wheel building your own interface, why not just spend that time working on the FOSS project in question? Hu? Because they won't t

> Instead of re-inventing the wheel building your own interface, why not just spend that time working on the FOSS project in question? Hu? Because they won't take my contribution that rips out all of the web interface and replaces it with EMACS? I mean, what does this even have to do with FOSS? Developing stuff as protocols instead of as user interfaces does not in any way prevent FOSS, very much to the contrary. There are FOSS IRC clients in all shapes and forms: Web interfaces, X GUIs, Windows GUIs, mobile clients, terminal UIs, EMACS modes, XMPP bridges, Matrix bridges ... how is any of that "reinventing the wheel", and how would we be better off if all those clients had to be part of one "IRC FOSS project" rather than independent projects with standards-based interoperability?