Well, as outlined in GitHub, these concepts seem to exist already. Number 1
would be called "block" (you could still use the forum, I guess) and (2)
"suspension" (everything hidden).
I would suggest (if not already present) to add an option to block a user from
using the forum or their user
As way of a clarification: the LWG was not proposing to block children
from answering on changeset comments (given these are public and not so
easily misued), but not allowing access to the blog and the internal
message system.
Simon
Am 24.09.2018 um 20:22 schrieb Michael Reichert:
> Hi
Hi Frederik,
Am 24.09.2018 um 17:57 schrieb Frederik Ramm:
> Is the opposite true as well - would/should someone given a cool-off
> period for being a dick in a discussion still be allowed to do mapping?
No. Anyone who is able to edit the map data should be able and has to
answer sensible
There are two common types of account blocks on MediaWiki, which could form the
basis for the proposed reform:
1. A block where a user cannot edit any page except their own talk page.
2. A block where a user cannot edit any page at all.
So on OSM, it would be:
1. Editing block
2. Full block
Hi,
I would like to start a discussion/brainstorming about the technical
aspects and means of blocking OSM user accounts.
First of all, the wider OSM community uses a wealth of communications
channels, most of which are not even controlled by us; here I just want
to discuss the actual OSM
5 matches
Mail list logo
