User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Hello.
II want to ask you to support IRCv3 on Next Thunderbird Generation. I couldn't see Thunderbird as member of IRCv3 WG. Look at https://ircv3.net/

Actual results:

Current version of Thunderbird(68) don't support all of IRC v3 features.
For compare Thunderbird with other IRC clients in IRC v3 Support area, look at https://ircv3.net/software/clients.html

Expected results:

Thunderbird should support most of IRC v3 features.
Thunerbird/Tb-Council or Even Mozilla Foundation as Current parent of Thundrebird should join to IRC v3 WG as a Participant Organization.

Hey Amir, thanks for filing a bug on this... I do participate in the working group on behalf of Thunderbird.

I do not believe we should "support all of IRCv3 features" blindly, however. Is there a particular feature from IRCv3 you think is missing?

It would probably be more action if a separate bug was filed on each IRCv3 feature that is useful to Thunderbird -- although we could use this as a metabug if that's useful.

Hello Patrick. Thanks for your answer.
However i think next generation of Thunderbird, should suppport all of(Or at least 80%) of IRC v3 features; but i think we should discusee in Thunderbird team about features of IRC client of Thunderbird.
In addition, I'm a person with my personal preferrals. I think you should show list of IRC v3 features to E ask end from users of Thunderbird IRC client to have a list of most popular IRC v3 features.
I suggest to create a survey on Thunderbird web site and ask end users about most perreferd IRC v3 features.
In addition, you can send your suervey for Mozillians in first step. Most of them are using IRC cleints ecvery day.

Yours.
Amir

I don't think it is useful to set a threshold without discussing the impact of each feature for users.

I'm going to morph this into an IRCv3 metabug. If there are particular features that it makes sense for Thunderbird to support, please file blockers against this!

Updating this with some more legacy bugs where support was implemented.

I've gone ahead and filed most of the things I have on an ancient todo list of IRCv3 things that would be neat. I've mostly left out the specs that are still marked as darfts for now (replies, labeled-responses, setname), and the related specs that only make sense when there's a CAP actually using them (client side tags, message ids).