AntiCompositeNumber (2023-06-06 01:01):
In case it was unclear: I do not intentionally store usernames. The
Toolforge infrastructure, in its default configuration, stores
usernames.
To my knowledge storing IP addresses and URLs (typical access logs) is
fine, because it is required by some
In case it was unclear: I do not intentionally store usernames. The
Toolforge infrastructure, in its default configuration, stores
usernames. Toolforge also does not provide tools to easily clean up
logs.
This is not an individual developer problem.
AntiCompositeNumber
(he/him)
On Mon, Jun 5,
AntiCompositeNumber (2023-05-27 05:29):
I am disappointed that these Terms went into effect immediately,
without any chance for review or comment by the community. This is
counter to how Wikimedia processes should run, and flies in the face
of the values of the Wikimedia movement.
I am
I'm sorry, but that response is unacceptable.
The resources of volunteer developers are also limited. Enacting an
unclear policy without recent consultation with the groups affected
places an unreasonable burden on the volunteers WMCS exists to serve.
AntiCompositeNumber
(he/him)
On Fri, Jun 2,
Xover, ACN, and others,
I’m sorry for my slow response – much of the WMCS staff was off for some
of this week.
In 2016 there was an initial public consultation about new terms of
use[0]. The fact that we only now have a document to show for it should
give you an idea of how difficult this
I agree with ACN's points, especially the lack of community review and
discussion.
For example, in section 4.1 on prohibited uses it refers to "Do not break
the law", but fails to specify which law, so as written it applies to all
laws anywhere enacted by a competent legislative body.
I am disappointed that these Terms went into effect immediately,
without any chance for review or comment by the community. This is
counter to how Wikimedia processes should run, and flies in the face
of the values of the Wikimedia movement.
I am concerned about some of the provisions of these
