Hi All,
Welcome to the monthly MediaWiki Insights email!
Enable more people to know MediaWiki and contribute effectively
In the last MW insights email
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Reports/October_2…>
we shared more about our approach to helping people contribute effectively
to MediaWiki
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Contributor_reten…>.
A few interesting data points:
The number of contributors to MediaWiki core who have more than > 5 patches
continued to grow: We just hit for the first time the goal of 20% since the
start of the Foundation’s fiscal year in July, compared to the
July-November time period last year. This is exciting to see - now it’s
about keeping the momentum and continuing on that path.
Many thanks to all the people who have contributed to MediaWiki core!
The average and median time to first review for patches in MediaWiki core
decreased significantly in the period July 1st to Nov 30 compared to the
same time period one year earlier.
- Average time to first review dropped from previously 16.5 days to 4.5
days
- Median time to first review dropped from previously 1.2 days to 0.6
days
Many thanks to all the code reviewers of MediaWiki core patches!
Keep in mind that this data is only one data point. There are many factors
that play into the experience of contributors; a helpful comment may be
more relevant than a fast +1/-1, etc.
Over the past weeks, we have been spending some time with planning
initiatives to further support people in onboarding and contributing to
MediaWiki:
- We are preparing for a WMF internal MediaWiki code jam in December to
try out a few things and focus specifically on the needs of teams.
- One thing we wanted to test in practice at the code jam is the “MediaWiki
Quick Install <https://phabricator.wikimedia.org/T347347>” guide. This
has been a collaboration between the Tech Docs team and the MediaWiki
Platform team - you can find the latest version of this experiment here:
https://www.mediawiki.org/wiki/Local_development_quickstart
- We discussed a possible focus project in the next quarter on improving
first time MediaWiki (core) contributors’ experience. We’re exploring a few
simple, small ideas that we could implement/try out in the next quarter
(ticket follows!).
Project snapshot: Analysis of MediaWiki execution timings, fixing issues
with logging in on Mobile, progress on RESTBase deprecation and more!
Performance: Piotr and Timo conducted an analysis of MediaWiki execution
timings <https://phabricator.wikimedia.org/T350593> and identified areas
for improvement. One of the fixes promises a 50ms improvement
<https://phabricator.wikimedia.org/T351807>! Timo and Derick worked on
bagOStuff improvements <https://phabricator.wikimedia.org/T336004> (cache
layer), shipped on MW-1.42. This work aims to lower the barriers for
contributors by making interfaces leaner and more intuitive and is reducing
storage access cost from 10ms to ~1 ms. Thank you for your work!
More highlights:
MediaWikiIntegrationTestCase now automatically tracks what database tables
get touched during the integration test, removing the need for developers
to keep track (T342301 <https://phabricator.wikimedia.org/T342301>). Many
thanks to Daimona and others for their work on this!
Work towards PHP 8.2 support continues, with one helpful outcome being a
new DynamicPropertyTestHelper feature (T326466
<https://phabricator.wikimedia.org/T326466>). Many thanks to TK-999 and all
reviewers!
Gergö worked on solving a variety of problems with logging in on mobile
(see https://phabricator.wikimedia.org/T257852#9347008 and below). Many
thanks to Gergö and everyone who provided support!
RESTBase sunset: Wikifeeds now calls the Parsoid endpoint in MediaWiki core
rather than RESTBase. Many thanks to Yiannis and Daniel for their hard work
on making this happen! Cxserver is preparing a deployment to the same soon
<https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/977983/>
(thank
you, Language team!).
Upcoming:
There is an OutputTransform
<https://www.mediawiki.org/wiki/Parsoid/OutputTransform> pipeline that is
being introduced to replace ParserOutput::getText(). This pipeline
initially targets content that comes from the ParserCache before it is
rendered (as a 1:1 getText() equivalent ). The team is likely going to
introduce another layer of cacheability of this output so that we can store
richer canonical Parsoid content and use this pipeline to transform it for
final rendering. Many thanks to Isabelle, CScott and Daniel for this work
in progress (Gerrit:967449
<https://gerrit.wikimedia.org/r/c/mediawiki/core/+/967449>)!
As one puzzle piece of our product research efforts and platform design
explorations, Moriel and others have been working on mapping high level
essential user workflows such as edit and patrol against platform
components to explore workflow patterns and potential architectural
opportunities in the platform. One outcome of this is going to be to
describe the key challenges when trying to model our system. Many thanks to
Moriel for leading on this work, and Daniel, Timo, Subbu, James, Cindy,
Emanuele and Amir S for their support, great questions and ideas!
Up next: Presentations at Semantic MediaWikiCon
Semantic MediaWikiCon
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023#Program> is
coming up, virtual and in person from Dec 11-13. We shared about the
updates to the rdbms library in the last MW Insights email - if you want to
learn more about this work, check out Amir’s presentation at Semantic
MediaWikiCon
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023/Major_changes_on_i…>!
Subbu and C.Scott are also going to give their yearly update on the parser
unification work
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023/Updates_from_the_W…>,
Chris will be talking about Codex
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023/Codex,_the_Design_…>,
and Stef about automated testing for complex MediaWiki topologies
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023/Automated_Testing_…>.
Since the theme of this edition is MediaWiki in the age of AI, Mike will be
presenting on the recent experiences with the experimental Wikipedia
ChatGPT plugin
<https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023/The_Wikipedia_Chat…>.
Keynote speaker of this years’ Semantic MediaWikiCon is Markus Krötsch
<https://www.korrekt.org/page/Short_biography>.
That’s the last insights email for 2023. The deployment train pauses for
the end of the year break, and so does the monthly MW Insights email!
We’ll be following up with a double-edition in January.
Thanks all for reading,
Birgit
--
Birgit Müller (she/her)
Director of Product, MediaWiki and Developer Experiences
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello (Semantic) MediaWiki users, maintainers, software developers, consultants, researchers!
The SMWCon in fall 2023 https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023 will be held on location in Paderborn, Germany from December 11-13.
On three days there will be talks, tutorials and hackathons.
This conference addressed everybody interested in wikis and open knowledge, especially in Semantic MediaWiki, e.g. users, developers, consultants, business or government representatives, and researchers.
This conference aimed to:
. inspire/onboard new users,
. inform on where and how MediaWiki is used,
. convey and consolidate best practices,
. initiate/foster/integrate application and development and
. strengthen the community of stakeholders and its service portfolio.
Learn how to "do" MediaWiki in order to assume your responsibilities regarding your organization's knowledge management.
Please not that early-bird ticket sale ends today!
Call for Contributions
----------------------------
We are looking for use cases and best practices that provide insight in issues like
* How does AI change the way we use MediaWiki
* How do semantic wikis fit in and be combined with AI tools
* How can we use Semantic MediaWiki in research and organizations
* How do we develop and deploy MediaWiki and extensions
Your experience is valuable for all of us! So please share and propose a talk, tutorial or other contribution.
Go to the Conference Page (https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_20223)
and hit the 'Propose a talk here' button.
Please propose a contribution if you plan to have one, even if you don't have the details yet. For us it is important to know what we can expect.
We look forward to your contribution!
Sponsoring
----------------
Thank you to the sponsors of SMWCon 2023!
* http://www.archixl.nl/ - Specialists in enterprise architecture, knowledge management, and semantics
* https://bluespice.com - The company behind BlueSpice, the open-source enterprise wiki software
* https://mywikis.eu - GDPR compliant (Semantic) MediaWiki hosting from the heart of Europe.
* https://wikibase-solutions.com/ - Specialist in business solutions with MediaWiki
Organization
------------------
The organizers of SMWCon 2023 and https://mwstake.org
* Bernhard Krabina, https://km-a.net (General Chair)
* Ad Strack van Schijndel, https://www.juggel.com (Program Chair)
* Tobias Oetterer, https://www.uni-paderborn.de/en/ (Local Chair)
Mediawiki 1.39.4, PHP 8.1.25, MariaDB 11.1.
When #get_db_data is constructed like this (using SQL JOIN):
{{#get_db_data:
db=test
|from=t1
|where=t1.c1='test'
|join on=t1.c1=t2.id
|data=t1c1=t1.c1
}}
the resulting query is
SELECT t1.c1 FROM t1 WHERE t1.c1='test'
i.e. missing 'JOIN t2 ON t1.c1=t2.id'.
Tested with ExternalData 3.1, 3.2 and Git master.
Thanks for any attention to this.
Šarūnas
Hi All,
Welcome to the monthly MediaWiki Insights email!
Enable more people to know MediaWiki and contribute effectively
In the last MW insights email
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Reports/September…>
we gave a preview into the work that is underway to help people feel more
comfortable touching MediaWiki, enable teams and volunteers to contribute
effectively, and retain and grow the number of contributors to MediaWiki in
Wikimedia production (WMF Annual Plan, WE3.2
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/…>).
We’ve used the first quarter to invest in code improvements, consultancy
and code review, explore and test approaches and defined three main focus
areas:
1. Design low-entry-level initiatives for contributions to MediaWiki
core and a set of extensions, enriched by workshops, improved
documentation, code review and support to enable more people to feel
confident contributing to MediaWiki.
2. Provide consultancy for Wikimedia’s teams in projects that touch
MediaWiki core domains to help sustain current contributors and to enable
more people to contribute to MediaWiki effectively.
3. Invest in code improvements, logging, monitoring and test coverage in
specific areas to make it easier to debug issues and ease onboarding in
MediaWiki.
Target audiences are Wikimedia staff and volunteers. For example, as part
of the work above and as a practice from early on, the MediaWiki Platform
team provided code review for around 200 patches submitted by volunteers in
the first quarter (https://w.wiki/7qa3).
The goal is both retention, and growth (a 20% increase in the number of
authors who have submitted >5 patches to a selected set of MediaWiki
repositories in Wikimedia production).
Currently the numbers are trending positive: We can observe a 17% increase
in the number of people who have submitted >5 patches to MediaWiki core
from July 1st - October 30th, 2023 compared to the same time period last
year. However, we’re still at the start of this and it’s too early to cheer
:).
A draft overview on approach, baselines and work underway can now be found
on this page
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Contributor_reten…>
.
Project snapshot: New database features, new security feature, and Source
Maps now live on all Wikimedia wikis + default in MediaWiki
The Data Persistence team (lead: Amir Sarabadani) is currently
undertaking several
improvements <https://phabricator.wikimedia.org/T343098> to the MediaWiki
Rdbms <https://www.mediawiki.org/wiki/Rdbms> library’s interface to make it
easier for developers to get database connections and perform common
queries. One improvement is a new database feature that allows extension
developers to specify more cleanly when they need special external
databases (T330590 <https://phabricator.wikimedia.org/T330590>). As part of
phasing out accepting and passing around raw SQL in the MediaWiki rdbms
library (T210206 <https://phabricator.wikimedia.org/T210206>), there is now
also a new basic expression builder for use in conditions. This work is
done to improve security, readability and to ease onboarding in MediaWiki.
The team will soon create tickets for extensions that build raw SQL to ask
to migrate to expression builders (see this change
<https://gerrit.wikimedia.org/r/c/mediawiki/core/+/967554> for an example).
If you have questions or already want to get started, T350075
<https://phabricator.wikimedia.org/T350075> is the ticket to coordinate the
work and get in touch. Amir Sarabadani, Timo Tijhof and Bartosz Dziewonski
can help with questions.
More on security: There is a new security feature that allows developers to
set the language as x-xss to help find potential cross-site scripting
vulnerabilities. See T340201 <https://phabricator.wikimedia.org/T340201>for
more information. Many thanks to Lukas Werkmeister for the idea and work on
this! <3
Finally, Source Maps <https://phabricator.wikimedia.org/T47514> (already
highlighted in the last MW Insights email) is now live on all Wikimedia
wikis and shipped by default in MediaWiki.
Part of the initial work done by the new MW group is about setting the
teams up to be effective stewards. One upcoming focus of the MW Platform
team is on improving logging, monitoring and test coverage for the
authentication-related components to make it easier to debug issues,
respond to incidents and enable periodic health checks and alerts. See
T348206 <https://phabricator.wikimedia.org/T348206> for an initial
assessment of the situation and possible improvements.
MediaWiki within Wikimedia’s ecosystem. Next: WikiCon NorthAmerica
Conversations with staff and volunteers on their experiences with
contributing to MediaWiki, challenges and opportunities around MediaWiki
within Wikimedia’s ecosystem are still ongoing. Next “stop” is at WikiCon
North-America from Nov 9-12 <https://wikiconference.org/wiki/2023>: We’re
hoping for many hallway-track conversations and possibly an unconference
session on topics like: “What does core functionality mean to you?” - which
is one of the questions we’re exploring on the way to develop a strategy
for MediaWiki. Hope to see some of you there - reach out to me if you want
to connect!
We expect to wrap up the first round of interviews and explorations by mid
of November and publish the outcome (first “Product Insights report”)
around the beginning of December (which is a small delay from the original
plan to have this ready to share in November).
Thanks for reading!
Birgit
--
Birgit Müller (she/her)
Director of Product, MediaWiki and Developer Experiences
Wikimedia Foundation <https://wikimediafoundation.org/>
We would like to announce the release of MediaWiki Language Extension
Bundle 2023.10. This bundle is compatible with '''MediaWiki >=
1.39.0''' and requires '''PHP >= 7.4.0'''.
The next MLEB is expected to be released in 3 months. If there are
very important bug fixes, we will do an intermediate release. Please
give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.10.tar…
* sha256sum: 8b3f356014f1bfdf8c08ec8778c200f1e25567c210d1ee93ba7b7e3f894947ab
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.10.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.…
* Report bugs to: https://phabricator.wikimedia.org/project/view/1464
Release notes for each extension are below.
== Highlights ==
* Translate extension: Removed <code>mirrors</code> option when
providing configuration for translation memory.
== Babel ==
* Localisation and maintenance updates.
== CleanChanges ==
* Localisation and maintenance updates.
== cldr ==
* Localisation and maintenance updates.
== Translate ==
* Removed <code>mirrors</code> option when providing configuration for
translation memory. See
[[Help:Extension:Translate/Translation_memories#Configuration|related
documentation]].
* Translate extension no longer uses jQuery.ui ({{phab|T323332}}).
* Added an option to leave a redirect when moving a translatable page
({{phab|T62920}}).
* Improve compatibility between syntaxhighlight and translate when
using Parsoid ({{phab|T341009}}, {{gerrit|957761}}).
* Special:PagePreparation: Improve error handling, and message
displayed to the user. ({{phab|T342628}}).
* Special:AggregateGroups: Replace previous group selector with a more
user-friendly group selection tool.
* Made UI tweaks to search translations page to break long words to
avoid breaking the layout ({{gerrit|968673}}).
* Localisation and maintenance updates.
== UniversalLanguageSelector ==
* Added AwamiNastaliqBold font ({{gerrit|957266}}).
* Removed all TTF font files ({{gerrit|957273}}).
* Added Tiro Bangla font for Bengali Language ({{phab|T343658}}).
* Updated Junicode font to 2.100 ({{phab|T253006}}).
* Save preferred languages for named users only ({{phab|T337780}}).
* Fixed an error that would cause ULS to not open when clicked if the
wiki is configured to allow anonymous users to change their language
({{gerrit|969342}}).
* Localisation and maintenance updates.
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
Hello - does anyone know why Wiki-site.com is down? Any ideas when/if it might return? And finally is there a way to recover any of the data from the wiki I hosted on there?
Thank you!
Tiger
Hi,
I just want to let you know that I've started a topic[0] on the talk page
of the category "Audio player extensions".
I would appreciate your opinions, it definitely needs a cleanup. :)
Thank you for your understanding and time!
Best regards,
Zoran
[0] https://www.mediawiki.org/wiki/Category_talk:Audio_player_extensions
ブロック依頼にいて In block request 2
---------- Forwarded message ---------
From: cdr65820(a)gmail.com <cdr65820(a)gmail.com>
Date: 2023年10月9日(月) 23:51
Subject: 利用規約に反する行為及びユーザの通報 Reporting users who violate the terms of service
To: <info(a)wikimedia.org>
Hello. I'm Keiichiro Kato
my Talk page
https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85%E2%80%90%E4%BC%9A…
問題のある管理者の裁量ブロックや、ブロック依頼で困っています。
I'm having trouble with discretionary blocks and block requests from problematic administrators.
現在の私に対するブロック依頼 Request to block me now
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use This policy is approved by the Wikimedia Foundation Board of Trustees. It may not be circumvented, eroded, or ignored by Wikimedia Foundation officers or staff nor local policies of any Wikimedia project. Please note that in the event of any differences in meaning or interpretation between the original English version of this content and a translation, the original English version takes precedence. Lawful Behavior — You do not violate copyright, post illegal content, or violate other applicable laws that follow human rights principles. 日本語版Wikipediaのコミュニティを消耗させる利用者(Users who drain the community),の項目違反で会話ページ（Talk page）をブロックするのは、"Policy:Terms of Use"に反する。 It is against the "Policy: Terms of Use" to block the talk page for violating the Japanese version of Wikipedia's "Users who drain the community" section. 会話ページ（Talk page）をブロックは、ブロック解除依頼を困難にしてブロック議論に巻き込まれた編集者が犠牲になっている。 私も近いうちにそうなる。 Blocking talk pages makes it difficult to request unblocking, and the editors who get caught up in the blocking debate are the victims. I will be like that soon too.
ーーーーーーーーーーーーーーー
方針:利用規約 https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use/ja 「合法的な行動 — 著作権法に違反したり、違法なコンテンツを寄稿したり、人権の原則に従った、その他の適用法に違反してはなりません。」 https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use Lawful Behavior — You do not violate copyright, post illegal content, or violate other applicable laws that follow human rights principles. wikimedia利用規約に「人権」の文字がはっきりと書いてあります。しかしながら、その元となったと考えられる「世界人権宣言」を会話ページに掲載することは目的外利用だと考えているようで、私に対するブロック依頼で明白に表明しています。 The word "human rights" is clearly written in the Wikimedia Terms of Use. However, he seems to think that posting the Universal Declaration of Human Rights, which is thought to be the source of this, on the conversation page is a use for other purposes, and he clearly expressed this in his request to block me. Wikipedia:投稿ブロック依頼/Keiichiro Kato 20231007 Translation: Wikipedia:Post block request/Keiichiro Kato 20231007 https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…
ブロック依頼内容 Block request details "会話ページに於いて明らかな目的外利用となる「世界人権宣言」などの書き込み" Translation: "Writing such as the ``Universal Declaration of Human Rights'' on the conversation page, which is obviously used for purposes other than its intended purpose."
ーーーーーーーーーーーーーーー
方針:利用規約 礼節 — 礼節ある環境を支持し、他の利用者に嫌がらせをしないでください。 https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use/ja Policy:Terms of Use https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use Civility — You support a civil environment and do not harass other users.
利用規約違反（Policy:Terms of Use）の賛成票 Upvote for violation of terms of use (Policy:Terms of Use) 追放を以って事態を収束するしか術がない状況を認めるに十分であると同意します。--Rhcnisoll（会話） 2023年10月8日 (日) 14:14 (UTC) I agree that this is enough to warrant a situation where expulsion is the only way to resolve the situation. --Rhcnisoll (conversation) Sunday, October 8, 2023 14:14 (UTC) 残念ですが、現状のままではウィキペディアからお引き取りいただくほかないでしょう。 Mt.Asahidake（Talk） 2023年10月8日 (日) 11:07 (UTC) Unfortunately, in its current state, we have no choice but to take it back from Wikipedia.
同時に現段階での暫定ブロックも必要です。投稿ブロック依頼は相手を封じる道具ではありません。--Mee-san（会話） 2023年10月7日 (土) 10:00 (UTC) At the same time, a temporary block is also required at this stage. A post block request is not a tool to block the other person. --Mee-san (conversation) Saturday, October 7, 2023 10:00 (UTC)
ーーーーーーーーーーーーーーーー
管理者・被依頼者がブロック依頼を削除。報復依頼であることを正当化するために私のブロック依頼を削除 The administrator/requestee deletes the block request. Deleted my block request to justify it being a retaliation request
https://ja.wikipedia.org/w/index.php?title=Wikipedia%3A%E7%AE%A1%E7%90%86%E…
* {{UserAN|Prefuture}}[[利用者‐会話:Keiichiro Kato]]でルールの提示なしに[[Wikipedia:署名]]付発言を削除した。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 02:11 (UTC) * {{UserAN|Korail7409}}[[利用者‐会話:Keiichiro Kato]]でルールの提示なしに[[Wikipedia:署名]]付発言を削除した。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 02:11 (UTC) *:{{AFD|コメント}} '''投稿ブロック依頼は報復のための手段ではありません。'''もう一度方針を見直してみてください。--[[利用者:Korail7409|Korail7409]] <small>[[利用者‐会話:Korail7409|話]]/[[特別:投稿記録/Korail7409|歴]]</small> 2023年10月7日 (土) 05:34 (UTC) *::「[[Wikipedia:署名|署名]]付き発言の削除」に対してのブロック依頼です。よくお読みください。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 06:40 (UTC) *::'''サブアカウント'''ではないですよね？'''「複数のアカウントで同一ページの編集や議論に参加すること」、「方針違反回避や制裁回避」'''等は'''「多重アカウント使用が禁止される行為」'''になります。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 07:54 (UTC) *:::{{AFD|コメント}}何を根拠にしてそのように思われたのですか？あとこれ以上はあなたの会話ページでお願いします。--[[利用者:Korail7409|Korail7409]] <small>[[利用者‐会話:Korail7409|話]]/[[特別:投稿記録/Korail7409|歴]]</small> 2023年10月7日 (土) 08:04 (UTC) *::'''「管理人によるブロック」'''について言っているのであれば、'''なぜ「管理人に対するルールがあるか」'''について考えた方がいいです。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 08:14 (UTC) * {{UserAN|Daraku K.}}会話ページで「[[Wikipedia:荒らし|荒らし]]」と発言するものの、該当する項目を提示できなかった。方針とガイドラインを「[[WP:悪用|悪用]]」した安易な報告。コミュニティを消耗させているため、また、会話ページ及び本ページへの署名付き発言に対する改竄行為が認められたため、[[Wikipedia:論争の解決]]に抵触する。ブロックが必要。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 04:57 (UTC)--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 05:04 (UTC)--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 05:19 (UTC) *: {{コメント}} 明白な報復行為です。寧ろブロックされるべきは報告者です。-- [[利用者:Daraku K.|Daraku K.]]([[利用者‐会話:Daraku K.|Talk]]/[[特別:投稿記録/Daraku K.|Contributions]]) 2023年10月7日 (土) 05:01 (UTC) *::「依頼中の会話ページ内容の削除」をしていい理由にはなりません。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 05:02 (UTC) *::: {{コメント}} 被報告者による[[特別:差分/97290525]]の編集は適切でない（他者発言除去が認められる条件には該当しない）とは思いましたが、ここで既に互いを管理者伝言板に報告したり、投稿ブロック依頼を出していたりする状況で、本件に関してお二人がこれ以上何か行ってもウィキペディア日本語版に資することはないと思います。即時ブロック相当と考えるなら管理者がブロックするでしょうし、他の一般利用者もブロック相当と考えるならそれぞれの投稿ブロック依頼に賛成票を述べるでしょう。これ以上発言を積み重ねても、第三者にとっては経緯を追うのが大変になり、投稿ブロック依頼等での投票・コメントを行ううえでの支障になるように思います。少なくとも今日は、他の案件のみに関わるか、あるいはウィキペディアの編集は休むかしたほうが建設的かと思います。--[[利用者:郊外生活|郊外生活]]（[[利用者‐会話:郊外生活|会話]]） 2023年10月7日 (土) 07:03 (UTC) *:::: 全く仰せの通りで、報告者発言の除去を「rv/v」として除去したりここでの私の報告を「報復行為」として除去したのは少々やり過ぎでした。一先ず本日は本件に関しては静観します。ご迷惑をおかけして大変申し訳ありませんでした。-- [[利用者:Daraku K.|Daraku K.]]([[利用者‐会話:Daraku K.|Talk]]/[[特別:投稿記録/Daraku K.|Contributions]]) 2023年10月7日 (土) 07:15 (UTC) *:[[Wikipedia:投稿ブロックの方針#コミュニティを消耗させる利用者]]の項目に[[Wikipedia:署名]]は含まれます。よくお読みになってください。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 10:10 (UTC)<br> * {{UserAN|Mt.Asahidake}}[[Wikipedia:投稿ブロックの方針#コミュニティを消耗させる利用者]]の項目の[[Wikipedia:署名]]該当。[[利用者‐会話:Keiichiro Kato]]での私の[[Wikipedia:署名|署名]]の削除行為。及び、報復ブロック依頼。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 10:23 (UTC) Translation * {{UserAN|Prefuture}}[[User-Conversation:Keiichiro Kato]] deleted comments with [[Wikipedia:Signature]] without presenting rules. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 02:11 (UTC) * {{UserAN|Korail7409}}[[User-Conversation:Keiichiro Kato]] deleted comments with [[Wikipedia:Signature]] without presenting rules. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 02:11 (UTC) *:{{AFD|Comment}} '''A request to block a post is not a means of retaliation. '''Please reconsider your policy. --[[User:Korail7409|Korail7409]] <small>[[User-Conversation:Korail7409|Talk]]/[[Special:Posted record/Korail7409|History]]</small> October 7, 2023 (Sat) 05:34 (UTC) *::This is a block request for "deletion of comments with [[Wikipedia:signature|signature]]". Please read well. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 06:40 (UTC) *::'''It's not a subaccount'', right? ``Editing or participating in discussions on the same page using multiple accounts,'' ``avoiding policy violations or sanctions,'' etc. are classified as ``acts that are prohibited from using multiple accounts.'' Become. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 07:54 (UTC) *:::{{AFD|Comment}}What made you think that? For more information, please use your conversation page. --[[User:Korail7409|Korail7409]] <small>[[User-Conversation:Korail7409|Talk]]/[[Special:Posted record/Korail7409|History]]</small> October 7, 2023 (Sat) 08:04 (UTC) *::'''If you are talking about ``blocking by admins,'' you should think about ``why there are rules for admins.'' --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 08:14 (UTC) * {{UserAN|Daraku K.}} Although he said "[[Wikipedia:Trolls|Trolls]]" on the conversation page, the corresponding item could not be presented. Easy reporting of "[[WP:abuse|abuse]]" of policies and guidelines. It violates [[Wikipedia:Dispute resolution]] because it is draining the community, and because it has been observed that the conversation page and signed comments on this page have been altered. block required. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 04:57 (UTC)--[[User :Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 05:04 (UTC)--[[User:Keiichiro Kato|Keiichiro Kato ]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 05:19 (UTC) *: {{Comment}} This is an obvious act of retaliation. Rather, it is the reporter who should be blocked. -- [[User:Daraku K.|Daraku K.]]([[User-Conversation:Daraku K.|Talk]]/[[Special:Contributions/Daraku K.|Contributions]]) October 2023 Mon 7th (Sat) 05:01 (UTC) *::This is not a good reason to "delete the contents of the requested conversation page." --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 05:02 (UTC) *::: {{Comment}} I thought that the editing of [[Special:Difference/97290525]] by the person being reported was inappropriate (it does not fall under the conditions for allowing deletion of other people's comments), but here Since both of you have already reported each other to the administrator message board and requested to block posts, I don't think anything further done by the two of you regarding this matter will help the Japanese version of Wikipedia. If the administrator considers it to be equivalent to an immediate block, he or she will block it, and if other general users also think it is equivalent to a block, they will vote in favor of each post blocking request. I think that even if more comments are made, it will be difficult for third parties to follow up on what happened, and it will be a hindrance to voting and commenting in requests to block posts, etc. At least for today, I think it would be more constructive to work on other projects or take a break from editing Wikipedia. --[[User: Suburban life | Suburban life]] ([[User-Conversation: Suburban life | Conversation]]) Saturday, October 7, 2023 07:03 (UTC) *:::: It's exactly as you said, but the removal of the reporter's statement as "rv/v" and the removal of my report here as "act of retaliation" were a bit excessive. First of all, I will wait and see about this matter today. We apologize for any inconvenience caused. -- [[User:Daraku K.|Daraku K.]]([[User-Conversation:Daraku K.|Talk]]/[[Special:Contributions/Daraku K.|Contributions]]) October 2023 Mon 7th (Sat) 07:15 (UTC) *: [[Wikipedia:Signature]] is included in the [[Wikipedia:Post blocking policy #Users who drain the community]] item. Please read carefully. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 10:10 (UTC)<br> * [[Wikipedia:Signature]] corresponds to the item {{UserAN|Mt.Asahidake}}[[Wikipedia:Post blocking policy #Users who drain the community]]. Deletion of my [[Wikipedia:Signature|Signature]] on [[User-Conversation:Keiichiro Kato]]. And a retaliatory block request. --[[User:Keiichiro Kato|Keiichiro Kato]]
([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 10:23 (UTC)
ーーーーーーーーーーーー
User 利用者:Dragoniez 管理者。自分自身で自分に対するブロック依頼を方針やガイドラインにない単語（異常依頼）を使用して削除 User User: Dragoniez administrator. Delete a block request for yourself using a word that is not in the policy or guidelines (abnormal request) https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Dragoniez 「Wikipedia:管理者伝言板/投稿ブロック」の版間の差分 Differences between versions of "Wikipedia:Administrator message board/post block" https://ja.wikipedia.org/w/index.php?title=Wikipedia:%E7%AE%A1%E7%90%86%E8%… * {{UserAN|Dragoniez}}利用者ページで「この利用者は現実世界で忙しいので、すぐにはお返事できません」とあり、必要な対話ができない利用者。「ブロックされているユーザの個人攻撃に繋がるスクリプト[[利用者:Dragoniez/subpages]]を利用者ページで配布」[[Wikipedia:個人攻撃はしない]]、同スクリプトを利用してると思わしきユーザが[[Wikipedia:投稿ブロック依頼]]で議論にみせかけて議論対象ユーザや、ブロック中のユーザ等に対して、攻撃的な発言がある。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 01:00 (UTC)管理者権限ブロックし会話ページで会話せず、[[Wikipedia:礼儀を忘れない]]に反する--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 01:03 (UTC)ウォッチリストとスクリプトで事務的に管理者権限ブロックすることは[[Wikipedia:礼儀を忘れない]]に反する--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 01:30 (UTC)管理人に対しての会話に、会話ページで会話せず、他の管理人が管理者権限ブロックで会話ページ編集をブロックするのは[[Wikipedia:腕ずくで解決しようとしない]]に反する--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 01:30 (UTC)会話ページで会話せず、管理者権限ブロックを行うのは[[Wikipedia:説明責任]]に反する--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 01:44 (UTC)[[利用者:Korail7409]]と[[利用者:Prefuture]]によるルールの提示なしに[[Wikipedia:署名]]付発言を削除を容認した。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 02:11 (UTC)私のブロック中に議論当事者であった、[[Wikipedia:削除依頼/ジュピター (楽器メーカー)]]の削除依頼を承認した。[[Wikipedia:腕ずくで解決しようとしない]]に反する--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 02:14 (UTC)管理者権限ブロックした後、会話ページで会話せず、他の管理人に管理者権限ブロックさせた疑い。[[Wikipedia:論争の解決]]に反する。--[[利用者:Keiichiro Kato|Keiichiro Kato]]（[[利用者‐会話:Keiichiro Kato|会話]]） 2023年10月7日 (土) 02:38 (UTC) * {{UserAN|Dragoniez}}The user page says, ``This user is busy in the real world, so we can't reply right away,'' and the user is unable to engage in necessary dialogue. "A script [[user:Dragoniez/subpages]] that leads to a personal attack on a blocked user is distributed on the user page" [[Wikipedia:I do not make personal attacks]], a user who seems to be using the same script [[Wikipedia:Post block request]] is made under the guise of a discussion, with offensive comments being made towards the users being discussed and the users who are being blocked. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 01:00 (UTC) Block administrator privileges and chat Do not talk on the page and go against [[Wikipedia:Remember courtesy]] -- [[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) October 2023 Monday, 7th (Sat) 01:03 (UTC) Blocking administrative privileges using watchlists and scripts is against [[Wikipedia:Remember courtesy]] -- [[User: Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) October 7, 2023 (Sat) 01:30 (UTC) When talking to the administrator, do not talk on the conversation page, etc. It is contrary to [[Wikipedia:Do not try to solve problems with skill]] for the administrator to block conversation page editing with an administrator privilege block. Person - Conversation: Keiichiro Kato|Conversation]]) October 7, 2023 (Sat) 01:30 (UTC) It is [[Wikipedia:Accountability]] to not talk on the conversation page and block administrator privileges. Contrary--[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 01:44 (UTC)[[User: Korail7409]] and [[user:Prefuture]] allowed the deletion of comments with [[Wikipedia:signature]] without presenting any rules. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 02:11 (UTC) Discussed during my block Approved the deletion request of [[Wikipedia:Deletion request/Jupiter (musical instrument maker)]], who was a party to it. Contrary to [[Wikipedia:Do not try to solve problems with skill]] -- [[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) October 7, 2023 (Sat) 02:14 (UTC) After blocking administrator privileges, he did not talk on the conversation page and is suspected of having other administrators block administrator privileges. Contrary to [[Wikipedia:Dispute resolution]]. --[[User:Keiichiro Kato|Keiichiro Kato]] ([[User-Conversation:Keiichiro Kato|Conversation]]) Saturday, October 7, 2023 02:38 (UTC)
ーーーーーーーーーーーーー
方針:利用規約 礼節 — 礼節ある環境を支持し、他の利用者に嫌がらせをしないでください。 https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use/ja Policy:Terms of Use https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use Civility — You support a civil environment and do not harass other users. 利用規約違反（Policy:Terms of Use）の管理者 Administrator of Terms of Use violation (Policy:Terms of Use) User Administrator 利用者:Dragoniez https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Dragoniez 管理系に顔を出す時は、基本的に100%現実作業での別作業の傍ら、ウォッチリストを眺めていた際のついでに行っています。 When I appear in management, I basically do it 100% of the time while doing other work in real life, or as an incident when I'm looking at my watch list.
ーーーーーーーーー
方針:利用規約 礼節 — 礼節ある環境を支持し、他の利用者に嫌がらせをしないでください。
合法的な行動 — 著作権法に違反したり、違法なコンテンツを寄稿したり、人権の原則に従った、その他の適用法に違反してはなりません。 https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use/ja Policy:Terms of Use https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use Civility — You support a civil environment and do not harass other users. Lawful Behavior — You do not violate copyright, post illegal content, or violate other applicable laws that follow human rights principles.
利用規約違反（Policy:Terms of Use）の管理者、ユーザ Administrator of Terms of Use violation (Policy:Terms of Use) Users who violate the Terms of Use (Policy:Terms of Use) User Administrator 利用者:Dragoniez https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Dragoniez 利用者:Dragoniez/導入をお勧めするスクリプト User: Dragoniez/Script recommended for installation https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Dragoniez/%E5%B0%… スクリプト関連 User:Dragoniez/導入をお勧めするスクリプト ブロック中のユーザーを取り消し線表示したり、曖昧さ回避ページへのリンクをオレンジで表示したり。 Script related User:Dragoniez/Scripts recommended for installation Display blocked users as a strikethrough, display links to disambiguation pages in orange, and more. 利用者:Mt.Asahidake/sandbox/利用者への注意喚起例文 User: Mt.Asahidake/sandbox/Example sentence to alert users 管理者伝言板へ報告の際のAN Reporterのご提案 Mt.Asahidakeと申します。いつもウィキペディア上での活動お疲れ様です。さて、表題の件ですが、さんをWikipedia:管理者伝言板/投稿ブロックにて度々お見受けすることから、こちらへの報告をよりスムーズかつ効率的に行えるDragoniezさんのAN Reporterについてお知らせにまいりました。AN Reporterと呼ばれるこのスクリプトを使用することで、報告がより行いやすくなり、また要約欄への手入力を行わなくとも自動で報告対象者が入力されることから、管理者の方でも対処を行いやすくなるなど、さんおよび管理者の双方においてメリットがあるものです。管理作業の効率をより向上させることができるものですので、この機会に是非ご検討いただけますと幸いです。 AN Reporter suggestion when reporting to administrator message board My name is Mt.Asahidake. Thank you for your continued efforts on Wikipedia. Now, regarding the title, since I often see you on Wikipedia:Administrator Message Board/Post Block, I would like to inform you about Dragoniez's AN Reporter, which allows you to report to us more smoothly and efficiently. . By using this script called AN Reporter, it is easier to report, and the person to be reported is automatically entered without having to manually enter it in the summary field, so administrators can also take action. This has benefits for both you and the administrator, such as making it easier to use. We hope that you will take this opportunity to consider this, as it can further improve the efficiency
of your management work.
日本語版Wikipediaコミュニティの現状[ソースを編集]
わかりやすく言うと、【Wikipediaコミュニティは、「みんなが悪いと言ったら、その人が悪者」という程度のコミュニティ】。--Keiichiro Kato（会話） 2023年10月8日 (日) 06:00 (UTC)[返信]
管理に関して重要なブロック依頼の投票では、Wikipediaコミュニティの利用者はルールについて言及せず主観的内容を発言し、ブロック依頼に賛成票を投じる利用者がいるのが現状。--Keiichiro Kato（会話） 2023年10月8日 (日) 01:14 (UTC)[返信]
利用者ブロック依頼の議論について、過去のブロック及び現在、過去のブロック依頼にこだわる傾向があるが、その時のルール違反について議論すべきである。過去のブロック関係に文章量を割いたブロック依頼及び被依頼者コメント、投票は、Wikipedia:論争の解決、Wikipedia:腕ずくで解決しようとしない、Wikipedia:善意にとるの方針に反する。--Keiichiro Kato（会話） 2023年10月8日 (日) 01:36 (UTC)[返信]
過去のブロック関係に文章量を割くということは、ルール違反よりも、魔女裁判のような投票、現在のルール違反を軽視しブロック依頼を有利に進める等の目的で行っていると考え、感じている。--Keiichiro Kato（会話） 2023年10月8日 (日) 01:46 (UTC)[返信]
管理者は都合のいいときは、ノートページでの議論が全くない状態で投票ページでの議論を見て裁定を行う。ノートページでの議論がなくブロック依頼者の味方が投票での議論を誘導し、被ブロック依頼者の味方の管理者による審議妨害・熟読期間での強権ブロックをされる。--Keiichiro Kato（会話） 2023年10月8日 (日) 02:01 (UTC)[返信]
ブロック依頼中は、依頼審議によってブロックを決定すべきです。ブロック依頼・被依頼中の管理者裁量ブロックはWikipedia:論争の解決の方針に反します。「Wikipedia:論争の解決が意味をなさない状態でしょうか？私に対するブロック依頼者の対話不能が原因です」また、Wikipedia:管理者においての記述は、【なお、管理者はこれらの操作を物理的に行える利用者です。これらの操作は方針によって使用範囲が決められており、方針により認められている場合、および操作の必要性が誰の目にも明らかな場合にのみ行うことができます。よって、管理者は操作を行うかどうか決定する利用者ではありません。方針では、これらの操作は原則として、利用者からの依頼と利用者間の合意形成を経た後に実行されることとなっています。】
Wikipedia:規則の悪用の「議論の妨害」は明白な悪意を持って行った場合に適応すべきです。また、Wikipedia:投票は議論の代用とはならないです。ブロック依頼者、またブロック非依頼者が私の編集論争について言及していますが、ブロック依頼者、またブロック非依頼者による第三者の意見であり、Wikipedia:法律家ごっこを行っていると解釈しています。私の書いた発言の削除がWikipedia:法律家ごっこを行っている証拠になっています。
Wikipedia:五本の柱によってウィキペディアは百科事典であること書いてあります。ブロック論争で裁量ブロックにより編集者を減らすことが管理者のすることでしょうか？--Keiichiro Kato（会話） 2023年10月8日 (日) 05:20 (UTC) Wikipedia管理者がブロック依頼のウォッチを続け、強権的な管理者ブロックを続け、またWikipediaルールの改定に関与し続ける場合、管理者関与でWikipediaルールの改定を行った場合、管理者に不利なルールの追加作成は行われないと予測されるのが私の考えです。管理者を目指す場合、貢献ではなく権力欲等で管理者になった場合、管理者に不利なルールの追加作成を拒否する行動に出ることは想像に難くない。[返信]
この通りになった場合、コミュニティは不健全に成長します。--Keiichiro Kato（会話） 2023年10月8日 (日) 04:04 (UTC)--Keiichiro Kato（会話） 2023年10月8日 (日) 05:42 (UTC)
Current situation of the Japanese version of Wikipedia community [Edit source] To put it simply, [Wikipedia community is a community where if everyone says it's bad, that person is the bad person]. --Keiichiro Kato (conversation) October 8, 2023 (Sun) 06:00 (UTC) [Reply] In the voting for important block requests regarding management, users of the Wikipedia community did not mention the rules and posted subjective content. The current situation is that there are users who speak up and vote in favor of block requests. --Keiichiro Kato (conversation) Sunday, October 8, 2023 01:14 (UTC) [Reply]
When discussing user block requests, there is a tendency to focus on past blocks and current and past block requests, but we should discuss the violation of the rules at that time. Block requests, requestee comments, and votes that devote text to past block relationships go against the policies of Wikipedia: resolving disputes, Wikipedia: not trying to resolve disputes by force, and Wikipedia: acting in good faith. --Keiichiro Kato (conversation) Sunday, October 8, 2023 01:36 (UTC) [Reply]
I think and feel that devoting so much text to past block-related matters is done for the purpose of witch trial-like voting, downplaying current rule violations, and gaining an advantage in block requests, rather than rule violations. There is. --Keiichiro Kato (conversation) Sunday, October 8, 2023 01:46 (UTC) [Reply]
When it is convenient for the administrator to do so, he or she may look at the discussion on the voting page and make decisions without any discussion on the notes page. There is no discussion on the note page, and an ally of the block requester induces a discussion through voting, and an administrator who is an ally of the blocked requester obstructs the deliberation and is forcibly blocked during the perusal period. --Keiichiro Kato (conversation) Sunday, October 8, 2023 02:01 (UTC) [Reply]
During a block request, the block should be decided through request deliberation. Administrator discretionary blocking while requesting or receiving a block is against Wikipedia:Dispute resolution policy. "Wikipedia: Is dispute resolution meaningless? This is due to the inability of the person who requested the block to communicate with me." In addition, the description in Wikipedia: Administrator is [Note that the administrator cannot physically perform these operations. This is a user who can do this. The scope of use of these operations is determined by the policy, and may only be performed if permitted by the policy and if the necessity of the operation is obvious to everyone. Therefore, the administrator is not the user who decides whether or not to perform the operation. Our policy states that, in principle, these operations will only be carried out after a request from a user and consensus building between the users. ]
Wikipedia: The rule abuse of "disruption of discussion" should apply when done with clear malice. Also, Wikipedia: Voting is not a substitute for discussion. The person who requested the block and the person who did not request the block mention my editing controversy, but this is interpreted as a third-party opinion from the person who requested the block and the person who did not request the block, and that Wikipedia is playing lawyer. doing. Deleting my comments is proof that Wikipedia is playing lawyer.
Wikipedia: The five pillars describe Wikipedia as an encyclopedia. Is it something administrators should do to reduce the number of editors through discretionary blocks in block disputes? --Keiichiro Kato (conversation) October 8, 2023 (Sun) 05:20 (UTC) Wikipedia administrators continue to monitor block requests, continue to implement heavy-handed administrator blocks, and are involved in revising Wikipedia rules. If this continues, if Wikipedia rules are revised with the involvement of administrators, it is my opinion that no additional rules will be created that are disadvantageous to administrators. If someone aspires to become an administrator and becomes an administrator out of a desire for power rather than contribution, it is not hard to imagine that they will refuse to create additional rules that are disadvantageous to administrators. [reply]
If this continues, the community will grow unhealthy. --Keiichiro Kato (Conversation) October 8, 2023 (Sun) 04:04 (UTC)--Keiichiro Kato (Conversation) October 8, 2023 (Sun) 05:42 (UTC)
－－－－－－
Under the following conditions:
Responsibility — You take responsibility for your edits (since we only host your content).
Civility — You support a civil environment and do not harass other users.
Lawful Behavior — You do not violate copyright, post illegal content, or violate other applicable laws that follow human rights principles.
No Harm — You do not harm our technology infrastructure and you follow the policies for that infrastructure.
Terms of Use and Policies — You adhere to the below Terms of Use, to the Universal Code of Conduct, and to the applicable community policies when you visit our websites or Projects or participate in our communities.
あなたは次の条件を守る必要があります。
責任 — 自分の編集に責任を持ってください（私たちはあなたのコンテンツをホスティングするだけです）。
礼節 — 礼節ある環境を支持し、他の利用者に嫌がらせをしないでください。
合法的な行動 — 著作権法に違反したり、違法なコンテンツを寄稿したり、人権の原則に従った、その他の適用法に違反してはなりません。
害を与えない — 技術基盤に害を与えないようにし、技術基盤に関する方針を守ってください。
利用規約と方針 — 私たちのウェブサイトまたはプロジェクトを訪れたりコミュニティーに参加したりする時には、下記の利用規約、ならびにユニバーサル行動規範および参加するコミュニティーの方針を遵守してください。
ブロック解除依頼への回答。日本語版Wikipediaでは会話ページでブロック解除依頼を行うのに管理者権限で会話ページをブロックした。日本語版Wikipediaでは会話ページのブロックは非推奨。
Responses to unblock requests. In the Japanese version of Wikipedia, the conversation page was blocked with administrator privileges even though you could request to unblock it on the conversation page. Blocking conversation pages is not recommended in the Japanese version of Wikipedia.
会話ページ Talk page
https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85%E2%80%90%E4%BC%9A…
ブロック解除依頼への回答 Response to unblock request
却下の理由: ご自身がブロックされた理由を理解せず、ご自身を正当化するための演説を繰り返しているため、却下いたします。また、会話ページのアクセスを取り消します。
ブロックが解除となるためには、以下の点について管理者を納得させる必要があります。
ウィキペディアに対する妨害・損害を避けるためにあなたをブロックする必要はないこと または
あなたが
なぜブロックされたのか理解し、
ウィキペディアに対する妨害や破壊をやめ、
今後は有用な貢献を行うため、
ブロックがもはや必要でなくなったこと
投稿ブロック解除依頼作成の手引きもぜひお読みください。 春春眠眠 🗨️会話 2023年10月8日 (日) 12:23 (UTC)[返信]
ブロック解除の依頼を再度行いたい場合には、投稿ブロック解除依頼作成の手引きをまずお読みになり、もう一度 {{unblock}} テンプレートを使用してください。なお、これらのテンプレートの乱用があった場合は、あなたの会話ページの保護や、会話ページへのブロックを実施する場合もありますのでご注意ください。
Reason for rejection: Your account will be rejected because you do not understand why you were blocked and are repeatedly making speeches to justify yourself. It will also revoke access to the conversation page.
In order for the block to be lifted, you must convince the administrator of the following points:
There is no need to block you to avoid interference or damage to Wikipedia; or
you
Understand why you were blocked,
Stop interfering with and destroying Wikipedia.
In order to make useful contributions in the future,
that the block is no longer needed
Please also read the instructions for creating a request to unblock a post. Spring sleep sleep 🗨️ Conversation Sunday, October 8, 2023 12:23 (UTC) [Reply] https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Syunsyunminmin
If you would like to request an unblock again, please read the instructions for creating a request to unblock a post first, then use the {{unblock}} template again. Please note that if these templates are misused, your conversation page may be protected or blocked.
https://ja.wikipedia.org/w/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85%E2%8…
ウィキペディアは百科事典であること書いてあります。ブロック論争で裁量ブロックにより編集者を減らすことが管理者のすることでしょうか？
It says that Wikipedia is an encyclopedia. Is it something administrators should do to reduce the number of editors through discretionary blocks in block disputes?
これについて、「ご自身を正当化するための演説」と回答
Answer: “A speech to justify yourself.”
このご使用のユーザー名またはIPアドレスは投稿ブロックの方針に従い、Syunsyunminmin によって投稿をブロックされています。具体的な理由は次の通りです。
審議妨害; 会話ページも塞ぎます。
ブロック開始時期: 2023年10月7日 (土) 13:03
ブロック解除予定: 2023年10月14日 (土) 13:03
ブロック対象: Keiichiro Kato
投稿ブロック依頼やあなたの会話ページなどに、より詳しい情報が記載されていることがありますので確認してください。
The username or IP address you are using has been blocked from posting by Syunsyunminmin in accordance with the Posting Blocking Policy. The specific reasons are as follows.
Obstructs deliberation; also blocks conversation pages.
Block start time: October 7, 2023 (Sat) 13:03
Scheduled to be unblocked: October 14, 2023 (Sat) 13:03
Blocked: Keiichiro Kato
Please check the post block request or your conversation page for more detailed information.
私の会話ページをブロックした管理者は「会話ページも塞ぎます」と方針やガイドラインにない慣習用語を使用
The administrator who blocked my conversation page used customary language that was not in the policy or guidelines, saying, ``I will also block the conversation page.''
利用規約違反の管理者 Administrator in violation of terms of use
利用者:Syunsyunminmin
https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Syunsyunminmin
ーーーーーー
方針やガイドラインにない単語（異常依頼）を使用し、私のブロック依頼を却下した管理者
The administrator used a word that was not in the policy or guidelines (abnormal request) and rejected my block request.
User 利用者:MaximusM4
https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:MaximusM4
利用規約違反であると考える。I believe this is a violation of the Terms of Use.
私が起こしたブロック依頼 Block request I made
即時却下。Immediately rejected.
Wikipedia:投稿ブロック依頼/Daraku K. Wikipedia:Post block request/Daraku K.
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A….
Wikipedia:投稿ブロック依頼/Dragoniez . Wikipedia:Post block request/Daraku K.
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…
Wikipedia:投稿ブロック依頼/えのきだたもつ Wikipedia:Post block request/ えのきだたもつ
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…
Wikipedia:投稿ブロック依頼/ Prefuture Wikipedia:Post block request/ Prefuture
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…
Wikipedia:投稿ブロック依頼/ Mt.Asahidake Wikipedia:Post block request/ Prefuture
https://ja.wikipedia.org/wiki/Wikipedia:%E6%8A%95%E7%A8%BF%E3%83%96%E3%83%A…
以上、対応お願いします。 Please respond to the above.