Win a badge when presenting your halloween custume in the monthly Roundtable Meeting.
Honestly. Do not forget to prepare the guise with your youngest and to explain them what is behind Trick or Treat.
Roundtable at 20th and Halloween at 31st - enough time.
standard - in nothing else is convened/scheduled: Thursday, October 20, 2016 at 18:00:00 UTC time (click for time zone in your city) See most voted time above.
See Roundtable Meetngs for a detailed description.
https://profiles.tiki.org upgrade plan to ease filtering and sorting of profiles?
See the description of the current system in place:
https://tiki.org/How+to+approve+registrations+on+tiki.org
We seemed to have setup the randomstring keyword needed ("Registration page key") in the url for the registration screen to show up in https://tiki.org, but this was blocking users from registering since there was a hand made link to "Register" in the tiki homepage that didn't have that keyword string manually setup in that hand-made link.
Conclusion: users that clicked at the link from the Homepage couldn't register. And the link to "register" frmo the login module didn't work either for me the first time I tried but only after I disabled the feature "Registration page key" and re-enabled it again (caching issue? was that recently setup in tiki.org??? )
Anybody aware of other places were we did setup custom links to "Register" or tiki-register.php?
Regardless of the many thanks we need to give to the person that has been taking care of validating new user requests in tiki.org, we cannot rely in this custom hand-made single-man procedure, since it means a bottleneck and too much pressure and responsability on a single person for such an important entry point of new users, reviewers and developers to the Tiki community.
I did a quick review, and there were plenty of legitimate registration requests to tiki.org (like the ones reminded on irc and through personal emails days ago to some admins), and dozens of others in the last weeks. Even found some legitimate requests from several months ago (4 months ago, 8 months ago, ...) among dozens of spammer registration attemps. So
the man-made work was woprking pretty well, but indeed not well enough. And it's not a single-man responmsibility. Therefore, I propose to change this situation to a more automated process of allowing users to register first, and only when proven that they spam, then we can remove + ban ip, etc.
For instance, validation of new user requests can NOT be done in bulk in the user admin UI (not even easily reviewing theuir user tracker records with a single click from there), but removing and banning ip's can be done indeed in bulk from several places (user admin UI, action log UI, etc).
One page links to Roundtable Meeting 2016 10
1) |
15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
2) |
19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
3) |
Tiki birthday |
4) |
17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
5) |
21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting |
6) |
19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting |