Can you support limit on pending requests. This could be very useful to prevent spam. So if you have 3 requests pending , you can't request more till you either cancel those or people accept your request.

Comments

mrf’s picture

mrf commented

You can add pending to the total count currently but this isn't separated out.

Do you mean having a separate limit count for pending and a different number for active relationships?

ajayg’s picture

ajayg commented

I mean this. I have N relationship. But at a time I can only have 3 requests pending. Unless I hear back from those 3 or I cancel one of the pending request, I can not request more. Once I have N+1 active, that 1 is also available for more request. This will guarantee someone won't just send request to 200 people at a time. He/She can do that but will need to be part of site for a long time. This is how linked in requests are managed too. It allows you X pending free and if you pay more you can have X+5 pending free at any given time.

mrf’s picture

mrf commented

Ok, I see where you're coming from.

A way to get close with this right now would be to click the check box for "include pending in the count" and then make a small limit for authenticated users. Then vetted non-spammers would get promoted to a different role without a limit or a much larger one. Not ideal because the authenticated user could only have 3 relationships total either pending or approved, but might cover the case in the mean time.

It's definitely a good use case and I'll look into adding it once I find some time and would be happy to look at patches in the meantime.

ajayg’s picture

ajayg commented

This won't cover the use case. Because
1. I am autheticated user. I have 100 relationships. If I reduce the limit to 3 for total (authenticated+pending) then every autheticated user can have only 3 total relatipnships. What we need is a seperate limit for pending altogether. The use case required the pending limit (even for non-spammers). Why that helps slowly build up your relationships over time, which has far better user experience. Or you can charge different roles for different levels.
Thanks for listening and considering the request.

mrf’s picture

mrf commented

Whichever role you have with the biggest limit is the one that applies, so user 1 might be the only issue, I haven't tested for that, but as soon as the user has another role with a higher limit the 3 for authenticated will get ignored.