~irc/github.com/solanum-ircd/solanum.git/modules, branch ignore_purposehttps://github.com/solanum-ircd/solanumhttps://cgit.space/~irc/github.com/solanum-ircd/solanum.git/atom/modules?h=ignore_purpose2025-05-11T22:40:42ZAdd dedicated hook data type for can_create_channel2025-05-11T22:40:42Zdaemoness2025-05-02T16:30:19Zurn:sha1:b3d3796e690ce2482c1365d99e3329d5587b75d5
hook_data_can_create_channel includes the name of the channel being created,
which is necessary for any non-trivial restriction of channel creation
as well as sending correct error messages.
The new hook data matches the layout of the previous hook data,
taking advantage of a disused pointer field in hook_data_client_approval
as used by callers of the hook (m_join).
modules: remove unused spy code.2024-07-24T05:46:30ZRealKindOne2024-07-24T05:25:01Zurn:sha1:4e89f6603d63b2f8dfdec7a83161fb0343236349m_stats: correct format specifiers and types2024-07-24T05:11:53ZDoug Freed2024-07-24T05:02:01Zurn:sha1:d01a08c31e35011a50bf34eb3218edcce49b90dd
These format specifiers were all wrong. Use the right ones. Musl time_t
is always 64 bits, so promote all rb_current_time usage to 64 bits.
Fixes #437m_whois: restore original multi-prefix behavior2024-06-12T22:23:50ZDoug Freed2024-06-12T22:15:22Zurn:sha1:0c59c5b974a3d255b14d83a0151a5e9f28e197c5
The original behavior has existed since before git history, and has no
known impact on clients that exist today.
This reverts commit 746ced2Revert "Fix WHOIS reply not respecting a lack of the multi-prefix capability"2024-06-11T17:57:07ZAaron Jones2024-06-11T17:53:36Zurn:sha1:746ced2308f606ddaa2781ada5eac4e4364b8f3f
A server handling a remote WHOIS cannot safely use IsCapable() to determine
if the client has multi-prefix enabled or not.
This is because client capabilities are not shared between servers; and the
IsCapable() macro dereferences source_p->localClient which will be NULL if
source_p is not on this server.
Instead rework the commit to always pretend that multi-prefix is not
enabled, to still respect the fact that multiple prefixes should not be
returned in case a client does not have multi-prefix enabled.
This reverts commit 4633665ad62bdfe26529
Fix WHOIS reply not respecting a lack of the multi-prefix capability2024-06-11T01:48:03ZJustAnotherArchivist2024-06-10T20:31:51Zurn:sha1:4633665ad62bdfe26529dfc115b1ba311903ed01
Prior to this commit, RPL_WHOISCHANNELS always contained all channel membership prefixes, even when the client had not enabled the multi-prefix capability. This behaviour predates available commit history. Other ircds only return the highest prefix, as prescribed by the RFCs.
m_starttls: advertise tls cap only if SSL is possible2024-03-12T09:39:52ZDoug Freed2023-02-21T20:47:11Zurn:sha1:dd3355732b392f8be9f326feb1849b2f46c9a1fcMODRESTART/MODRELOAD: Defer reloading more quickly2023-11-20T14:01:33ZAaron Jones2023-11-19T11:47:24Zurn:sha1:a9505057c58ee46c8ef9a51a0e39afcaa250ac17
Commit 41390bfe5fa3895b8dee fixed a bug whereby the processing
of a MODRESTART command could result in a crash. The approach
taken in this fix was to defer the reloading of all modules
so that the call stack does not contain functions located in
modules that are being reloaded. It did this by scheduling a
one-shot timer event for 1 second in the future, in the absense
of any better deferral mechanism at the time. Timers are
processed by the event loop, which is core to IRCd and cannot
be reloaded.
Commit 59ea3c6753e80d051b20 introduced a mechanism to defer the
execution of a function until all events have been processed by
the event loop, in order to fix a REHASH bug that could result
in a crash due to closing and reopening listener sockets with a
pending socket connection event to process after the REHASH was
completed.
Rework commit 41390bfe5fa3895b8dee to use the new deferral
mechanism introduced by commit 59ea3c6753e80d051b20 and do the
same for module reloads.
extensions/invite_notify: make the NOTICE optional, configurable2023-11-08T13:12:49ZAaron Jones2023-01-11T21:16:58Zurn:sha1:4d12e65469c877f8028d5ac40a39457ec96b2f40
This adds a configuration option that determines whether the NOTICE is
sent to clients that do not support the IRCv3 invite-notify capability.
Requested by LiberaChat MGM.
client: refactor del_all_accepts to allow skipping own accept list2023-11-06T17:31:44ZDoug Freed2023-09-03T23:19:00Zurn:sha1:c1b01bf5ec318463ab076ac2d7c0a4b02631f745
This allows reusing this function for other uses that just need to
remove this client from others' accept lists on nick change and not have
duplicates of this code everywhere