Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dead clients should be explicitely marked as such, to avoid deception. #533

Open
malespiaut opened this issue Sep 6, 2024 · 5 comments
Open

Comments

@malespiaut
Copy link
Contributor

Hello,

I was looking at your list of IRCv3 compatible clients, and decided to choose HexChat, before discovering that the project has been archived since February 2024.

HexChat isn't the only dead client in the list: BitchX haven't received any code contribution since 2013.

I would like to propose you to either clean the list, or add a "dead" flag to dead clients, as the table of IRCv3 functionality for each client leaves the impression that they all are both in good health and striving for completion.

The goal of that list cleaning/tagging would be to help users making an informed decision when it comes to choosing an IRC client.

Best regards.

@SadieCat
Copy link
Contributor

SadieCat commented Sep 6, 2024

I occasionally will go through the list and remove dead clients but I haven't done it in a while because I've been busy with non-IRCv3 things.

That said I think we can leave HexChat for a while and switch it out when a viable fork actually appears.

@progval
Copy link
Contributor

progval commented Sep 6, 2024

The goal of that list cleaning/tagging would be to help users making an informed decision when it comes to choosing an IRC client.

To be fair, that list is intended for developers, not users.

@malespiaut
Copy link
Contributor Author

Thank you for your fast replies.

I think that it is fair to remove BitchX as it hasn't received any code contribution for a decade.

For the other list aimed at developers, that's a fair point, but doesn't, in my humble opinion, invalidate the point that no one want to loose time going thru each Git repo (when there's one) to make sure that the client is being actively developed or no: hence why I think that cleaning and tagging is necessary.

On that note, but I agree that it's another conversation, I think that, ideally, the list need to include very explicitly, maybe with pictograms, if the app is FLOSS or not, on which platform it runs on, and what is the date of the last stable version.

But that's another topic, and more work as well.

Thak you again for your time.

@jwheare
Copy link
Member

jwheare commented Sep 6, 2024

I get where you're coming from but the list is a reference for ircv3 feature support. It's not a general listing for apps to advertise their features, licenses, releases, etc. That's not our goal or responsibility with IRCv3. Maybe an idea for someone to take on as a separate project though.

@classabbyamp
Copy link

classabbyamp commented Sep 6, 2024

maybe https://en.wikipedia.org/wiki/Comparison_of_IRC_clients could be extended to include ircv3 info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants