Not sure if that’s because of anyone’s action, but it now works. Probably still worth investigating though

Currently experiencing on itwiki T425969

For everyone who missed it or wants to rewatch it: Wikipedia Screen Reader Example uploaded on commons: https://commons.wikimedia.org/wiki/File:Wikipedia_Screenreader_Example.webm

Also on itwiki. Example w https://it.wikipedia.org/wiki/Template:TOCleft

Update: I've reworked the hackathon session scope. Instead of a hands-on prototyping session, I've split it into two focused discussions:

Update: I originally scoped this task as hands-on prototype work during the hackathon. After thinking about it more, I realized the most valuable use of a room full of Wikimedians isn't watching me write Go, but it's getting input on the questions I can't answer alone.

In T417140#11628412, @Bawolff wrote:

That said, i never understand how a webapp can be e2ee. If the service provider is a potential attacker they can just replace the apps code. (This is a criticism that applies to a lot of alleged e2ee systems)

In T417140#11626296, @Aklapper wrote:

So far I do not understand why this ticket is called "E2EE Messaging for MediaWiki".
All recent comments sound like "some external stand-alone app, which only uses MediaWiki for auth or as a source for some stuff" instead.

In T417141#11626008, @EMill-WMF wrote:

Hi @valcio - thanks for opening this to get our thoughts. I want to be upfront that, while we of course believe in the availability of E2EE communication as a general matter, we're very unlikely to support Wikipedia offering an E2EE messaging system of its own. That would be a very significant area for the platform to expand in to, with both high technical and cryptographic complexity, and non-technical challenges to user safety, that organizations with a primary focus on private messaging are better suited to undertake. It's not just a matter of needing code to implement it. Not trying to tell you not to work on this, or projects like it - just that it is not something we would expect to devote resources to supporting here.

In T417140#11626221, @Bawolff wrote:

Its not entirely clear how you plan to integrate this into mediawiki. There is no concept of private messaging in mediawiki currently, so its unclear how this fits into the design of mediawiki.

Is it just an external messaging system using mediawiki/wikipedia for identity management?

[That said its a hackathon, don't let me stop you]

In T417138#11606604, @Daimona wrote:

Maybe we should find some time to talk about the idea?

I have opened a separate RFC T417141 to request a strategic validation from the Product Safety and Integrity team.

Possible tags: Security, Privacy, Product Safety and Integrity.
To be added once undrafted.

@Piergiovanna @Daimona, know you are interested in this topic and will be joining the hackathon. Would you be interested in leading/hosting this brief session with me?

Possible tags: Accessibility, Design, Codex.
To be added once undrafted.

In the meanwhile, it probably would be nice sending a message trough the technical newsletter, informing communities that they can override the message locally by editing MediaWiki:growthexperiments-homepage-mentorship-question-disclaimer-mentor-away and removing the links to the user page.

In T391113#10720677, @Sgs wrote:

Hiding the update to newcomers after a given date is easy but emptying the fields may be a more tricky.

The gadget is now opt-in only (diff). Please enable dark-mode back for unlogged users. Thank you.

This gadget follows a community discussion (here) so it would probably be better to ask there for an opinion.

@Bugreporter: There are already classes applied to the body element to identify the used skin (e.g. .skin-vector-2022).

Thank you. Closing this task!

L'utenza è stata creata (cfr. log 56182630).
Per ora eventuali richieste che necessitano dell'accesso vanno fatte a @Civvi, dopodiché - ad elezioni concluse - si occuperà di tutto la commissione.

In T363630#9750975, @Nardog wrote:

Somehow, the same code works here but here doesn't

That's because of T295514: Score audio uses different players depending on whether the page has other embedded media.

The issue has also been reported on itwiki.

Looks similar to T292324 but that should have been solved

Thanks, @Stang

In T306535#7876802, @Urbanecm_WMF wrote:

Hello @ValeJappo, fyi, I just deployed the fix to itwiki. Within a couple of hours (max. 3 hours), your mentor dashboard should update again (as well as everyone else's). Please do not hesitate to let us know if it doesn't work for any reason.

Renewing the request as it should now be possible, as WikiWho has been transferred on Wikimedia servers