You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current hook-based design of this extension means it can only show actions that trigger a hook, and data accessible via that hook (see #23, #28, #30, probably other things no one's noticed or bothered to file an issue for). I'm assuming this won't be a straightforward drop-in replacement, so definitely more of a wishlist item than anything.
The text was updated successfully, but these errors were encountered:
You're right - this won't be a straight-forward change.
Moving to a system where we instead pipe the RC feed output into a Discord channel is not a terrible idea - in fact, there is an alternative extension that already does this - but it doesn't feel like it's currently worth the investment in doing so for this extension. I understand that there will be some functionality that is missing because we're working directly with MediaWiki's hooks, which is a shame. Recently, hooks integrated into MW core have started getting better at providing more information to third-party extensions, so hopefully more things become possible using hooks only.
I think what I like most about the approach that we take in this extension is that it doesn't really require much configuration at all, which makes it perfect for shared hosts, farms, and people who aren't very knowledgable in server administration. It basically just requires a vanilla PHP setup. In contrast, using $wgRCFeedsrequires the sockets PHP extension to be enabled.
The current hook-based design of this extension means it can only show actions that trigger a hook, and data accessible via that hook (see #23, #28, #30, probably other things no one's noticed or bothered to file an issue for). I'm assuming this won't be a straightforward drop-in replacement, so definitely more of a wishlist item than anything.
The text was updated successfully, but these errors were encountered: