View Issue Details

IDProjectCategoryView StatusLast Update
0005474Composrpointspublic2024-03-30 03:24
ReporterPatrick SchmalstigAssigned ToPatrick Schmalstig 
SeverityFeature-request 
Status assignedResolutionopen 
Product Version 
Fixed in Version 
Summary0005474: Add point sending limits
DescriptionAdd configuration options to set limits as to how many points members can send to other members:

* Maximum points per period
* Period time in hours
* Whether gift points should be excluded from the limit (yes by default because the sole purpose of gift points is to give them to other members).

When set, members cannot send any more than X points to the same member within X hours. This operates per-member, not globally, so even if member A reaches the limit on sending points to member B, they can still send points to member C.

This can also act as a cap per transaction... members can never send any more than the defined number of points to another member in a transaction.

This should not apply to escrows.

A new privilege should be added that enables bypassing of these limits. Or, perhaps consider implementing this as a group/rank restriction.
TagsRoadmap: Over the horizon
Time estimation (hours)
Sponsorship open

Activities

Patrick Schmalstig

2023-11-27 04:19

administrator   ~0008072

The main reason for this is to help prevent abuse of the points system for artificially inflating each other's life-time points count. It is also essential for the upcoming karma non-bundled addon as karma could be awarded when receiving points from other members.

Chris Graham

2024-03-24 20:01

administrator   ~0008423

This is not all that straight forward. You're saying everyone should be subject to limitations to prevent abuse, but I say if I want to give some huge number of points to someone, I should be able to do so.
If that means then I need to have some special approval, or permissions, then that's making this feature much more complex. The abuse problem is currently solved via notifications and point transaction moderation.
I don't think we should be slipping stuff in that isn't completely trivial based on a non-bundled addon that isn't a part of the development process.

Patrick Schmalstig

2024-03-25 17:08

administrator   ~0008441

Last edited: 2024-03-25 17:09

View 3 revisions

I'm confused... points is a bundled addon. What non-bundled addon are you talking about? (EDIT: Oh you meant karma; I still think it's an important feature to reduce life-time points abuse since life-time points are used for ranks etc. But perhaps not something we implement; maybe a sponsored feature)

Chris Graham

2024-03-27 13:43

administrator   ~0008460

Okay perhaps a reasonable compromise would be to require staff APPROVAL for transactions above a certain amount. And make that amount a group setting for Conversr, and a config options for non-Conversr.

Patrick Schmalstig

2024-03-27 14:05

administrator   ~0008466

That could work. It would add some additional complexity (new privilege, new notifications, new column on the ledger table for "validated"... perhaps we use the validation (renamed from unvalidated) addon instead? And make a points ledger item a resource that supports validation). So not something I'll do for 11.0.

Chris Graham

2024-03-28 14:07

administrator   ~0008473

I think I'd want to keep validated for content only, otherwise it becomes complex in the UI, to explain, etc. We already have approval for new members that doesn't use the validated addon.

Patrick Schmalstig

2024-03-28 16:23

administrator   ~0008477

Noted. I'll use something like "approved" then with a separate privilege and notification.

Issue History

Date Modified Username Field Change
2023-11-27 04:17 Patrick Schmalstig New Issue
2023-11-27 04:19 Patrick Schmalstig Note Added: 0008072
2023-11-27 04:21 Patrick Schmalstig Description Updated View Revisions
2023-11-27 04:22 Patrick Schmalstig Description Updated View Revisions
2023-11-27 04:24 Patrick Schmalstig Description Updated View Revisions
2023-11-27 04:25 Patrick Schmalstig Assigned To => Patrick Schmalstig
2023-11-27 04:25 Patrick Schmalstig Status non-assigned => assigned
2023-11-27 04:25 Patrick Schmalstig Tag Attached: Roadmap: v11
2024-03-24 20:01 Chris Graham Note Added: 0008423
2024-03-25 17:08 Patrick Schmalstig Note Added: 0008441
2024-03-25 17:08 Patrick Schmalstig Note Edited: 0008441 View Revisions
2024-03-25 17:09 Patrick Schmalstig Note Edited: 0008441 View Revisions
2024-03-27 13:43 Chris Graham Note Added: 0008460
2024-03-27 14:05 Patrick Schmalstig Note Added: 0008466
2024-03-27 14:05 Patrick Schmalstig Tag Attached: Roadmap: Over the horizon
2024-03-27 14:05 Patrick Schmalstig Tag Detached: Roadmap: v11
2024-03-28 14:07 Chris Graham Note Added: 0008473
2024-03-28 16:23 Patrick Schmalstig Note Added: 0008477
2024-03-30 03:23 Patrick Schmalstig Project Composr alpha bug reports => Composr
2024-03-30 03:24 Patrick Schmalstig Category General / Uncategorised => points