Giter Site home page Giter Site logo

Make CTCP handlers optional about girc HOT 3 CLOSED

lrstanley avatar lrstanley commented on May 28, 2024
Make CTCP handlers optional

from girc.

Comments (3)

lrstanley avatar lrstanley commented on May 28, 2024

Those handlers can be disabled, by overriding them (registering something on top of it). There are no plans to remove the defaults, for a few reasons. It's a courtesy to folks running irc servers. With this information, they can better target malicious users, better understand the user-base connecting (and the clients they are using). It's also much like http servers sending the software name and version as a http response header, or (almost all) http clients sending their user-agent when making calls.

All of these things are a courtesy, as well as a credit to the library. Yes, there will always be a security concern when you are providing even the smallest of information about the host machine (if this is what you were getting at). If someone doesn't want to expose these, they can override them, much like you can override the user-agent header using the curl cli.

from girc.

nmeum avatar nmeum commented on May 28, 2024

There are no plans to remove the defaults […]

I am not proposing a change of the defaults. I am just saying: It would be easier to disable all CTCPs handlers through an additional configuration option (in the Config struct) instead of forcing users to overwrite all 6 default handlers manually.

If you really object adding an additional configuration option I would at least suggest adding a method for removing all registered CTCP handlers (CTCP.ClearAll() unfortunately readds the default handlers). That would make it way easier to disable them and would also be a more reliable way of doing so in case new handlers are added in the future etc.

from girc.

lrstanley avatar lrstanley commented on May 28, 2024

It would be easier, but I don't want to promote the option to remove defaults, only override. No defaults should be added in the future, unless a new spec defines CTCP's that should be used by default for clients. The reason I don't, is again, courtesy -- much like browsers, http clients, etc. They rarely have the option to remove, only update. If you don't want them, feel free to change them to something else -- I would recommend at least giving some information so servers can identify the origin.

from girc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.