[feat] Allow users to generate their own invites #423

New Issue

Open

opened 2023-01-06 05:06:23 +00:00 by ngoomie · 0 comments

ngoomie commented

2023-01-06 05:06:23 +00:00

The idea

If a server is closed for public registrations but has invites on, admins should also be able to allow their users to generate their own invites to invite friends with. Probably admins should be able to set it so this is a privilege they only receive after some amount of time and/or activity on the instance, as well as some sort of limit for how many invites a non-admin user can generate in a given period of time, in case bad actors have already made their way onto the instance (i.e. during a previous open signup period or what have you) so they can't easily continuously invite other bad actors.

The reasoning

Frankly, this is actually what I had assumed would be the default behavior for invite-only instances when I was setting mine up. I remember maybe glitch-soc Mastodon as a whole having this as a feature when I had used I think cybre.space years ago, and it feels like a pretty important and reasonable feature to have. I'd like my users to be able to invite others when open regs are closed, but as it stands now they have to ask me specifically for an invite, and wait for me to see it, then wait for me to be somewhere where I can do that easily. This would simply be more convenient for everyone involved, I think.

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the Akkoma backend specifically, and not pleroma-fe.

### The idea If a server is closed for public registrations but has invites on, admins should also be able to allow their users to generate their own invites to invite friends with. Probably admins should be able to set it so this is a privilege they only receive after some amount of time and/or activity on the instance, as well as some sort of limit for how many invites a non-admin user can generate in a given period of time, in case bad actors have already made their way onto the instance (i.e. during a previous open signup period or what have you) so they can't easily continuously invite other bad actors. ### The reasoning Frankly, this is actually what I had assumed would be the default behavior for invite-only instances when I was setting mine up. I remember maybe glitch-soc Mastodon as a whole having this as a feature when I had used I think cybre.space years ago, and it feels like a pretty important and reasonable feature to have. I'd like my users to be able to invite others when open regs are closed, but as it stands now they have to ask me specifically for an invite, and wait for me to see it, then wait for me to be somewhere where I can do that easily. This would simply be more convenient for everyone involved, I think. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.

ngoomie added the

feature request

label 2023-01-06 05:06:23 +00:00

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#423

No description provided.