Hi there,
I get the following when I try to access the site. I have tried clearing my
cache to no avail.
Warning: Host 'localhost.localdomain' is blocked because of many connection
errors. Unblock with 'mysqladmin flush-hosts' in
/usr/local/apache/htdocs/w/DatabaseFunctions.php on line 19
Could not connect to DB on 127.0.0.1
Host 'localhost.localdomain' is blocked because of many connection errors.
Unblock with 'mysqladmin flush-hosts'
If this error persists after reloading and clearing your browser cache,
please notify the <mailto:wikitech-l@nupedia.com> Wikipedia developers.
On Monday 11 November 2002 04:00 am, wikitech-l-request(a)wikipedia.org wrote:
> If we set a cookie in the browsers of all Wikipedia visitors, anonymous or
> not, we could the assign them random global user IDs. Instead of banning
> users by IP, we could ban them by GUID, which would eliminate the risk of
> accidentally banning legitimate contributors.
>
> While the majority of users have cookies enabled, a minority does not, so
> "soft bans" as I like to call them would not work for them. Other users
> might be smart enough to turn cookies off to avoid the ban. But I consider
> both beyond the technical understanding of most vandals, so I think soft
> bans might be quite efficient.
>
> What do you think?
>
> Regards,
>
> Erik
This seems like a good idea. However many browsers now have the ability to
easily block cookies so to combat this we would have to require everyone to
accept cookies in order to edit - which I don't think is too Draconian.
It would be great to have this /in addition to/ the current IP blocks but
please keep this functionality -- it is needed to at least temporarily block
the more technically savvy.
-- Daniel Mayer (aka mav)
Since there were no objections, I have committed the patch for the
watchlist checkbox in article edit mode (Magnus has given me CVS
access). I have checked out a second copy and tested it quite
thoroughly, but let me know if there are any problems.
Note that I obviously don't have all translations, so I hope people will
eventually send us the translated strings.
I have also sent a request for further feedback regarding the sidebar
links to wikipedia-l, and will commit that patch as well if there are no
objections.
If anyone actually reads this mail, I would appreciate some advice: Is
there a way to tell CVS to ignore my LocalSettings.php? .cvsignore only
ignores files that are not in the repository.
Regards,
Erik
--
FOKUS - Fraunhofer Insitute for Open Communication Systems
Project BerliOS - http://www.berlios.de
>(assuming we use a bbs)
>
>PHP BB (http://www.phpbb.com ) seems to be the natural BBS system for
>Wikipedia to use, since it's GPLed and PHP+MySQL. It may be more ornate than
>we need, but with a little work to coordinate it with the main code, it
>would be very nice.
It would be great if such a thing could be integrated with a multilingual
meta.wiki (the main mailing list is no longer very useful with so many daily
posts). The encyclopedia wikis should be left alone though (IMO eventually
all encyclopedia projects should be on the same wiki - meta should be a
separate wiki for technical and ideological reasons).
>The only crucial thing we need to do is to have people who have logged into
>Wikipedia (any of the language instances) automatically be logged into the
>BBS.
How about just have it so that anybody logged into meta is also logged into
its integrated bbs?
>....
>
>--tc
--Daniel Mayer (aka mav)
(assuming we use a bbs)
PHP BB (http://www.phpbb.com) seems to be the natural BBS system for
Wikipedia to use, since it's GPLed and PHP+MySQL. It may be more ornate than
we need, but with a little work to coordinate it with the main code, it
would be very nice.
The only crucial thing we need to do is to have people who have logged into
Wikipedia (any of the language instances) automatically be logged into the
BBS.
The simplest way would seem to be to import user info from the current dbs
into the BBS user db, and have code to keep the BBS user db in sync with new
user creation.
Is there a test server on which this could be installed to work on?
--tc
About the cookies... (the digest was truncated...)
The disconnection between the fr and the en does not
happen all the time. It is usually by rows. For
several days, you navigate pretty well, and all of
sudden, for several days, you are no more recognised
when you connect yourself or jump from one to the
other. Even thought it is checked and rechecked in
your prefs. This is true under Opera on Mac.
I think I have *never* been recognised even once on
the meta. Whatever the browser I use (Opera, Mozilla,
Netscape or IE).
On IE (which i usually use for meta), I have two
cookies, one is called WCUserID and the other WCUserName.
__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2
I have become active in the French Wikipedia as well as the English one, and
often when I have been working on one, I find that I am logged out of the
other. I posted a bug report about this (with the German Wiki) some time ago.
I am now somehow logged out of both. Can someone fix this, or do you need
more information?
phma
Hi,
the attached patch adds a checkbox to the edit page that says "Watch
this page", and a preference to have this checkbox active by default.
It can be used both to add and remove watches from articles, which
should make it more convenient to maintain an up-to-date watchlist for
people who want to watch all articles they work on.
As always, all feedback appreciated.
Regards,
Erik
--
FOKUS - Fraunhofer Insitute for Open Communication Systems
Project BerliOS - http://www.berlios.de
There are 4 issues standing between polish wikipedia and phase 3
software.
One is automatic conversion of &#codes; are requires just a small
patch, which has been sent by me already.
Second is support for H1 (don't say that it is reserved for page
titles, CSS already treats H1 and H1.pagetitle different).
Two others are MySQL issues:
* MySQL doesn't search UTF-8 right.
* Wikipedia should be mirrorable and MySQL database dumps are not
really convenient way.
Afair MySQL 4.1 is supposed to fix the first, and there is some
patch already that fixes that, so could you investigate that stuff ?
Mirroring by downloading dumps is very inconvenient,
making nightly patches of dump file available is bare minimum.
But in longer term some better solution should be developed.
Anyway, I'm for setting up final setup instalation as soon as
&#code; and H1 issue is fixed. MySQL issues may be hard to fix
and nothing really critical would happen if they were fixed a few
weeks later.