| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Wiki access warning? |
| Date: | 2016-01-05 08:51:53 |
| Message-ID: | CA+OCxoxQAg-D0znCsOCyy=nCcdqbkbALNMVEajD_WYszAu3zWw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Mon, Jan 4, 2016 at 10:14 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> On Mon, Jan 4, 2016 at 9:06 PM, Stefan Kaltenbrunner
> <stefan(at)kaltenbrunner(dot)cc> wrote:
>> yeah - but that is not nearly enough, the wiki really is for the wider
>> community and we need to find a more suitable approach...
>
>
> Ah, this explains why I couldn't upload my talks just now.
>
> A slight improvement would be to include anyone who has ever
> registered or submitted for any of the conferences. Presumably
> spammers aren't going to pay actual money or submit an actual talk.
>
> If you have emails then you could allow anyone who has posted to any
> mailing list for an extended period of time on the assumption that
> repeat spammers on the lists get caught out fairly quickly. I'm not
> sure if email is there though.
A fine idea, but right now that would require a PFY to trawl through
the conference attendees and mj2 users to find those people, figure
out what their usernames are and then authorise them in the horrendous
mediawiki UI. Scripting it is feasible, but certainly not simple.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-01-05 17:56:04 | Time to retire -performance? |
| Previous Message | Alvaro Herrera | 2016-01-05 03:07:08 | Re: Wiki access warning? |