Current problem
I recently encountered an issue on my self-hosted Fluxer instance.
I created an admin-issued registration URL with no expiration and linked it to a community invite so new users would automatically join a community after registration.
However, I accidentally left the community invite at its default 7-day expiration. I simply wasn't aware of this setting and overlooked it when creating the invite. I later realized that Discord uses similar default expiration settings, which I hadn't been aware of either.
After 7 days, the community invite expired while the registration URL remained active.
As a result, users could still register successfully, but they were no longer automatically added to the community. I only discovered the issue after someone reported it.
This was ultimately my own oversight, and I understand that both links have independent expiration settings.
However, it made me realize that administrators could benefit from optional notifications when community invites or registration URLs are about to expire or reach their maximum number of uses.
Without such reminders, it's easy to lose track of links that are no longer usable as intended, especially when managing multiple invitations or registration URLs with different expiration dates and usage limits.
Proposed change
I'd like to suggest an optional email notification system for community invite links and admin-issued registration URLs.
Ideally, administrators could choose to receive notifications for the following events:
1. Upcoming expiration
- Receive an email before a community invite or registration URL expires.
- For example, 24 hours before expiration.
- Ideally, the notification timing could be configurable.
- Receive an email when a community invite or registration URL reaches its configured maximum number of uses.
- Linked invite: Active (expires in 2 days)
- Linked invite: Never expires
- Linked invite: Expired
Platform
Web, Self-hosting
Additional information
This is intended as a quality-of-life improvement, not necessarily a bug report.
After discovering my mistake, I created a new community invite with "Expiration: Never" and linked it to a new registration URL. Everything appears to be working correctly again.
Now that I understand how the expiration settings interact, I can avoid this situation in the future.
However, I imagine other administrators might encounter similar situations, especially when managing multiple invites or registration URLs with different expiration dates and usage limits.
An optional email notification system could make managing these links easier without changing their existing behavior.
If email notifications would be too complex to implement, a clear warning or status indicator in the admin panel could also be a useful alternative.
Thanks for considering this suggestion! :)
Comments
No comments yet.