Hi everyone,
the Design System Team (DST) is proposing the following changes to
MediaWiki browser support [1]:
- Drop support for Internet Explorer 11 (IE 11)
- Drop support for all versions of Edge Legacy
- Drop support for Opera
- Increase Basic (Grade C) support for Chrome and Firefox to versions 49+,
Safari and iOS to versions 10+.
What this means: The browsers we’re phasing out won’t be tested for layout
rendering anymore. While users on these browsers might and will still be
able to read and basically interact with content, they might experience
some quirks. This step helps us integrate modern web features more
seamlessly.
These changes will unlock the ability to use specific newer browser
features that cannot be safely used today without requiring a fallback,
notably CSS custom properties (used in upcoming reading customization
features like Night Mode) and the <summary> and <details> HTML elements
that can be used to replace the checkbox hack.
This will reduce the amount of code sent to 99.9% of users and cut down on
software development costs and maintenance burdens.
See the full announcement for more details; PDF to download [2].
On behalf of the Wikimedia Foundation Design System Team,
Volker
[1] https://www.mediawiki.org/wiki/Compatibility#Browser_support_matrix
[2] https://phabricator.wikimedia.org/F52025988
Hello everyone,
Tomorrow's UTC-morning deployment of 1.43.0-wmf.6 might be blocked on a
small but potentially noisy issue in LiquidThreads:
https://phabricator.wikimedia.org/T365495
If anyone can offer a spare null-coalescing operator at the right spot
(and ideally get it merged&backported), as Core's parseAsContent() does
not enjoy passing a null parameter anymore, that would be lovely - but
better trust Krinkle's initial analysis in the task instead (thanks!).
Thanks in advance!
andre
--
Andre Klapper (he/him) | Bugwrangler
https://blogs.gnome.org/aklapper/
Hi all,
very simple queries don't work, what happened. It seems to be defective
since about 30 minutes.
select * from pagelinks;
mysqlsel/db server: View 'dewiki_p.pagelinks' references invalid table(s)
or column(s) or function(s) or definer/invoker of view lack rights to use
them
(This message is about Wikimedia-specific changes. Nothing mentioned here
is mandatory for the third-party MediaWiki users.)
Hello everyone,
I am reaching out on behalf of the Wikimedia Foundation Trust and Safety
Product <https://www.mediawiki.org/wiki/Trust_and_Safety_Product> team,
working on the Temporary Accounts
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts>
project (formerly, IP Masking). We are making preparations for deployment
on testwiki.
We want to minimize the impact of temporary accounts on the ecosystem of
tools and features. Before deployment, we'll ask for stewards' confirmation
that critical workflows are not affected. Now, we would like to ask you to
check the impact on code you maintain. There may be breaking changes!
We do not have a firm deadline for deployment yet. We will let you know as
soon as we do. We would like to ask you to consider updating your tool's
code over the next weeks, if the tool works on any/all production cluster
wiki. If it only works on selected wikis and testwiki is not one of them,
you will have more time to update it. If you think it will take longer than
that to update your code, please let us know on our talk page
<https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…>.
For a full explanation of the technical change, please read our
documentation
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
In particular, the section on how your code might need to be updated
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
Some examples of ways code might be affected (not exhaustive):
- A feature looks for the IP address in the user name (it will no longer
be found).
- A feature that relies on looking at the user’s ID to identify if the
user is registered or unregistered. Temporary accounts will not have a
user_id of 0.
- A feature works differently for unregistered vs registered users.
See more examples
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
We may have discovered your issue already and filed a Phabricator task
using the #temporary-accounts tag. You may wish to file a subtask of T337012
<https://phabricator.wikimedia.org/T337012>. We hope that this task will
help us all as the technical community coordinates on tools requiring
updates.
If you have any questions or would like to learn more about the project,
take a look at our project page and reach out to us on the talk page
<https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…>.
Thank you!
Szymon Grabarczuk (he/him)
Lead Movement Communications Specialist
(Product & Tech)
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
We (MediaWiki Platform Team) are calling on you to nominate individuals for
the Web Perf Hero award for 2024.
https://wikitech.wikimedia.org/wiki/Web_Perf_Hero_award
A nomination is as simple as sending an email to
mediawiki-platform-team(a)wikimedia.org with the relevant information and we
will curate these responses and develop a list once the nomination period
has closed. The nomination period would run from today April 17, 2024 to
May 19, 2024.
When you nominate a person, include an example of where or how they made a
measurable performance improvement on Wikipedia or sister projects. This
can be as simple as links to Gerrit patch(es) or Phabricator task(s).
Nominations are open to all technical contributors (including WMF staff).
We really encourage you to nominate others, though self nominations are
permitted. You are also free to nominate multiple developers if you have
more than one in mind.
You can have a look at
https://wikitech.wikimedia.org/wiki/Web_Perf_Hero_award for past awards
given out in previous years. Thanks in advance for your nominations!
Derick,
On behalf of MediaWiki Platform Team
Hi Gnangarra,
On 13/05/24 10:45, Gnangarra wrote:
> From some who uses the app regularly, has big thumbs, and needs reading
> glasses I'll appreciate the voice input feature, now it just has to
> recognise my Australian accent 🤣 this should be interesting, and I'll
> apologize early on for any slips of the tongue.
>
Good to hear that you would find the voice input feature helpful. As to
the australian accent being recognized, we just piggy back on the
speech-to-text services that are available in your device. If you
already use any speech-to-text service that recognizes your accent well,
the same should work fine for app's voice input feature too.
If you notice any discrepancy, feel free to let us know :-)
> Thank you and everyone thats working on it.
>
Thank you for the kind words!
--
Sivaraam
Hello everyone,
We have an update on some changes coming to the Wishlist:
1. The new edition of the survey will *open in July and remain open
year-round*.
2. *There will be a new intake form*. Volunteers can submit a wish in
their preferred language and do not need to know Wikitext.
3. Volunteers will be able to submit wishes, review wishes, edit
existing wishes, and discuss wishes with one another and the Foundation
staff.
4. Wishes will be grouped into "*Focus Areas"*.
5. Participants will *vote for the Focus Areas.*
6. Wishes can be categorized by project(s) and by “type” (bug, feature
request, optimization, and so on)
7. We’ll eventually have a *dashboard* which will allow users to search
for wishes and filter by project or wish type.
For the full update and screenshots, please read our announcement on Meta
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey/Future_Of_The_Wis…>
.
Best regards,
Sandister Tei <https://meta.wikimedia.org/wiki/User:STei_(WMF)> (she/her)
Movement Communications Specialist (Community Tech & Trust and Safety)
Wikimedia Foundation
Hi all,
Hope you have been well! We have just released v5.0.1 of the Commons
Android app to production. The update is now available on Play store [1]
and F-droid [2]. You could also build the app directly from our GitHub
repository [3].
If you've faced issues with your profile not working / contribution information
not being shown appropriately, sorry about that! We've fixed that in
this version
:-)
We've had yet another revamp of the Maps screens in this version. We replaced
Mapbox altogether with the osmdroid library. Key elements like pin visualization
and user-centered display are still included in this redesign. We did
this to guard
against possible misuse of the Mapbox token and, more crucially, to keep the app
from becoming dependent on a service that charges for usage but offers
a free tier.
As a consequence, you may observe the Nearby and other Map screens not being
as snappy as they used to. We've noticed this and are actively
discussing on ways
to improve the same[4]. Feel free to chime in with your thoughts.
Talking about improvements to the app, this year Kanahia will be contributing to
the app during Google Summer of Code 2024! His project will focus on improving
upload queue management [5]. He will be mentored by Nicolas and Ritika.
Other significant changes:
- Add the ability to export locations of nearby missing pictures in GPX and KML
formats. This allows you to browse the locations with desired radius
for offline
use in your favourite map apps like OsmAnd or Maps.ME
- Added a compass arrow in the Nearby banner shown in the "Contributions" screen
to guide you towards the nearest item, thus providing the missing
directional cues.
The arrow dynamically adjusts based on device rotation, aligning
with the calculated
bearing towards the target location. Further, the distance and
direction are updated as
you move.
- Implemented voice input feature for caption and description fields,
enabling you
to dictate text directly into these fields.
- Improved various flows in the app to redirect you to the login page
and display a
persistent message if your session becomes invalid due to a password change.
- Revamped initial upload screen layout and the description edit
screen layout for
enhanced user experience and ensuring better symmetry in the design.
These are only a small chunk of all the changes that were part of this
release. Checkout
our release notes [3] for a more detailed set of changes since the
last announcement.
As always, feel free to reach our to us with your valuable feedback.
You could share
feedback in our talk page [6] / by writing an e-mail to
commons-app-android(a)googlegroups.com / via our issue tracker [7].
[[ References ]]
[1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons
(staged rollout has been initiated. It should be available in few days)
[2]: https://f-droid.org/en/packages/fr.free.nrw.commons
[3]: https://github.com/commons-app/apps-android-commons/releases/tag/v5.0.0
[4]: https://github.com/commons-app/apps-android-commons/issues/5529
[5]: https://phabricator.wikimedia.org/T360265
[6]: https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app
[7]: https://github.com/commons-app/apps-android-commons/issues
Best regards,
Sivaraam (User:Kaartic)