[buddypress-trac] [BuddyPress Trac] #8212: Do not use random number for resolve slug group conflict

buddypress-trac noreply at wordpress.org
Thu Jan 16 18:41:30 UTC 2020

#8212: Do not use random number for resolve slug group conflict
 Reporter:  ExoConsult                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  low                            |   Milestone:  Under
                                           |  Consideration
Component:  Groups                         |     Version:  1.0
 Severity:  trivial                        |  Resolution:
 Keywords:  reporter-feedback 2nd-opinion  |
Changes (by johnjamesjacoby):

 * severity:  normal => trivial
 * component:  Core => Groups
 * priority:  normal => low
 * version:   => 1.0
 * milestone:  Awaiting Review => Under Consideration
 * keywords:   => reporter-feedback 2nd-opinion


 > a better choice could be to iterate on a number until a non existing
 slug is found

 Why is an incremental number ''better'' than a random one?

 The reasons random slugs are used is because group slugs can be changed
 later, and random slugs cannot be enumerated through as easily if someone
 is trying to guess whether or not a group exists, either before or after
 it has been finalized by the creator.

 WordPress sites generally have fewer content creators, making incremental
 numbers simpler to manage because authors are usually working together
 anyways. In a Community site, where Group creation is likely to be open to
 all Members, a random number also dramatically reduces the probability of
 a slug collision, in the event multiple Members happen to be attempting to
 create a Group with the same base slug at around the same time.

 Open to hearing different opinions and suggestions here though!

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/8212#comment:1>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list