|Open||None||T52039 Proposed changes to default settings (DefaultSettings.php) (tracking)|
|Resolved||dmaza||T191922 Enable $wgCookieSetOnIpBlock by default after the IP cookie block feature is fully tested and released|
|Declined||None||T233597 Refactor ApiMain to use OutputPage::sendCacheControl|
|Resolved||dbarratt||T196575 Add block cookie for browser-based API edits (including VisualEditor & MobileFrontend)|
|Resolved||• TBolliger||T120734 Epic ⚡️ Improve MediaWiki's blocking tools|
|Resolved||dmaza||T152462 Add cookie when blocking anonymous users|
|Resolved||dbarratt||T192017 Enable anon cookie blocking on all Wikimedia wikis|
It looks like the limited release in T196121: Enable set cookie with IP/IP-Range blocks when blocking logged-out users on itwiki is not causing any problems and we can proceed with this task. The numbers in Graphite look reasonable and I found no reports of unexpected blocking problems on Italian Wikipedia's major discussion locations (Talk:Main Page, Information desk, Oracle, Bar, or their talk page for blocking policies.)
Let's take this into our next sprint!
Before you move forward with this, could you please make sure legal updates the cookie statement accordingly? There was information about the block cookie in the old template that was shown, but that is no longer being used. I emailed them about this but haven't heard back.
As you may know, some admins in the EU are worried they could theoretically be sued for issuing a cookie by blocking someone. I don't think this is something you or them should worry about (because it's the software that issues the cookie, not the admin), but the cookie statement should be reflected to reduce worries.
If you sent a recent email to them, could you please CC me into the thread?