~steering/inspircd++.git/src/modules.cpp, branch v4.0.0rc1 Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/src/modules.cpp?h=v4.0.0rc1 2024-06-07T09:37:56Z Update copyright headers. 2024-06-07T09:37:56Z InspIRCd Robot 2024-06-07T09:37:56Z urn:sha1:ae3e2db109eecaea25032e218c39a257e736174a Allow mutating the status message type in OnUserPre(Tag)Message. 2024-05-06T16:18:07Z Sadie Powell 2023-11-15T22:17:18Z urn:sha1:4b6af49b435d213d94221ac210293f4a2e7ef66f Rename some of the Module member variables. 2024-03-04T13:18:04Z Sadie Powell 2024-03-04T13:18:04Z urn:sha1:5f6bf286847550f386324e1e2db6c909cbd9f318 Rename the error log level to critical. 2023-08-11T11:39:49Z Sadie Powell 2023-08-11T11:39:49Z urn:sha1:f73e9e606b61324f4ac34d3f506b7cbaf87713c7 "ERROR" is apparently defined by more than just Windows. Let's pick a different name which is less likely to cause collisions. Simplify the codes that InspIRCd can exit with. 2023-07-13T13:07:26Z Sadie Powell 2023-07-13T12:31:06Z urn:sha1:b4e3e973297db456f0ba8d7fdb8bbfc9c8426ea7 The custom codes that InspIRCd exits with are not very useful and can confuse init systems like systemd which assume that certain exit codes mean certain things. INSPIRCD_BINARY_EXIT was a workaround for this in v3 but considering thatsers have to check the logs anyway so we may as well just use EXIT_SUCCESS and EXIT_FAILURE. Remove rang and use fmtlib for printing coloured messages. 2023-07-12T01:29:04Z Sadie Powell 2023-07-12T01:04:57Z urn:sha1:f0d817cf39987e7b7548863c86beac29440ab7c6 This supports more platforms (e.g. Haiku) and is actually still maintained unlike the former. All of this code should really be cleaned up for release (maybe by adding something like Anope's LOG_CONSOLE) but for now I've just replaced it with the fmtlib equivalent. Avoid culling DLLManager instances twice. 2023-07-05T13:44:52Z Sadie Powell 2023-07-05T13:44:52Z urn:sha1:2f59014b79ec4f876bb542227629e67fa6e60f55 Remove OnPreChange{Host,RealName} events and deboolify methods. 2023-06-29T21:52:07Z Sadie Powell 2023-06-29T21:29:34Z urn:sha1:1d96baaf774eacd5eacd357500a01af693aad654 These have not ever been used as far as I can see. Retain the "real" username properly like we do for hostnames. 2023-06-29T16:01:25Z Sadie Powell 2023-06-29T15:29:56Z urn:sha1:29705306f21d713c2928d8896f48a3cbb640eacc This introduces the concept of a real username. This value comes from either the initial USER message or from an ident lookup. Doing this allows us to use it for bans through vidents and cloaking web client users using their remote username. While changing this I also changed all of the uses of "ident" other than RFC 1413 lookups and some compatibility cases to refer to usernames as user(name) instead of ident. Our use of ident in these places was incorrect as that only refers to the RFC 1413 response and is not commonly used in the way we used it by any other IRC server implementations. Fix casing of metadata in function and event names. 2023-05-30T01:38:25Z Sadie Powell 2023-05-30T01:38:25Z urn:sha1:ea85c0c6bad664e241e9d407e8ae10c7971a66c2 Metadata is one word not two so it shouldn't be capitalised like this.