Lis ton message de Nganguem Victor avant qu'il ne soit effacé!
Pour lire ton message, suis simplement ce lien:
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
D'autres personnes sont aussi présentes:
Oded (Tel Aviv, Israël)
Priya (Udaipur, Inde)
RajaYogi BK (Udaipur, Inde)
Karuna (Udaipur, Inde)
Chika Reginald Onyia (Pnompen', Cambodge)
...Qui d'autre?
http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6
Les liens ne fonctionnent pas dans ce message? Copie les dans la barre d'adresse de ton navigateur.
Tu as reçu cet email suite à un message envoyé par Nganguem Victor de notre système. S'il s'agit d'une erreur, ignore simplement cet email. La requête sera alors effacée du système.
Amuse-toi bien !
L'équipe Badoo
Courrier automatique de Badoo suite à l'envoi d'un message à ton attention sur Badoo. Les réponses ne sont ni stockées, ni traitées. Si tu ne veux plus recevoir de message de Badoo, fais-le nous savoir:
http://eu1.badoo.com/impersonation.phtml?lang_id=6&mail_code=65&email=media…
Hello all,
I would like to draw your attention to the BlueSpice Product Days on May 10 and 11.
https://bluespice.com/bluespice-product-days-2023/
I briefly thought about whether this mailing list is the right place to draw attention to it. But I think you can get a good impression of what is going on technically in organizations and companies when it comes to MediaWiki and what is being discussed about content and structuring. And since we produce and publish in the Wikimedia context, all developments are available to the community. So the announcement really makes sense.
We will show nice new things like the ContentDroplets, talk about real-time editing, templates, cloud, AI and hashchains. We also have a number of interesting speakers on knowledge management.
You can attend online via Hopin. Participation is of course always free. It's best to register now.
We look forward to your participation, your feedback and thoughts.
All the best!
Dr. Richard Heigl
CEO
Hallo Welt! GmbH
We would like to announce the release of MediaWiki Language Extension
Bundle 2023.04. This bundle is compatible with '''MediaWiki >=
1.38.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.04.tar…
* sha256sum: c39c9d969255808a628e9fe2a9a2eceefd14ee5d3d0ef8d1fd1a4765804ad896
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.04.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 ==
* This is the last release of MLEB supporting '''MediaWiki >= 1.38'''
== Babel ==
* Fix "User categories creation should be able to use templates"
({{phab|T211665}}, {{gerrit|881947}})
* Add ability to override Babel categories ({{gerrit|881944}})
* Fix "Some language tags show wrong language ("English") in Babel
boxes" ({{phab|T64714}}, {{gerrit|884400}})
== CleanChanges and cldr ==
* Localisation and maintenance updates.
== Translate ==
* Optionally allow setting a source language for aggregate groups
({{phab|T281073}})
* Allow fetching translation statistics for messages with similar
prefix ({{phab|T298966}})
* Fix bug with importing fuzzy translations from .po files ({{phab|T323430}})
* Add back-links in various special pages in the Translate extension
* Use a text-based group selector in Special:ExportTranslations in
order to improve usability when a large number of message groups are
present ({{phab|T331843}})
* Show error message if group being exported has no translations for
selected language ({{phab|T331824}})
* Display "Translate" tab if a user has permission to translate
irrespective of whether public editing is enabled ({{phab|T334330}})
* Add support to configure readable and writable translation memory
services separately ({{phab|T322284}})
** Support for the <code>mirrors</code> configuration parameter will
be dropped in the next MLEB release.
== UniversalLanguageSelector ==
* Localisation and maintenance updates.
* Fix issues with up/down keys navigation for the ULS menu ({{phab|T328956}})
* Remove ULSMobileWebfontsEnabled configuration option ({{phab|T332837}})
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
Hello Everyone,
Today it was identified that the Graph extension [1], which uses the older
Vega 1 & Vega 2 libraries, had a number of security vulnerabilities.
In the interest of the security of our users, the Graph extension was
disabled on Wikimedia wiki's. We know that this is disruptive for editors
and readers, and WMF teams are working quickly on a plan to respond to
these vulnerabilities.
We recommend that any other third party users of the Graph extension should
disable the use of that extension on their wikis.
A configuration change will suppress the exposed raw tags and graph json
definition to avoid excess disruption to the end user experience when the
extension is disabled. [2] This also provides a tracking category
"Category:Pages with disabled graphs" showing the pages that used to
contain graphs. Local administrators can localise the name of the category
and its description by editing [[MediaWiki:Graph-disabled-category]],
[[MediaWiki:Graph-disabled-category-desc]] interface messages on your local
wiki.
On Wikimedia projects, graphs created via the extension will remain
unavailable. This means that pages that were formerly displaying graphs
will now display a small blank area. To help readers understand this
situation, communities can now define a brief message that can be displayed
to readers in place of each graph until this is resolved. That message can
be defined on each wiki at [[MediaWiki:Graph-disabled]] by local
administrators.
Wikimedia Foundation staff are looking at options available and expected
timelines. For updates on this topic, follow the public Phabricator task
for this issue: https://phabricator.wikimedia.org/T334940
We are seeking translation to be able to distribute a massmessage about
this to various language wikis tomorrow. Please help us translate here:
https://meta.wikimedia.org/wiki/User:Seddon_(WMF)/Graph_massmessage
Thank you,
Seddon
[1] https://www.mediawiki.org/wiki/Extension:Graph
[2]
https://gerrit.wikimedia.org/r/plugins/gitiles/operations/mediawiki-config/…
Seddon (he/him they/them)
*Engineering Manager*
*Wikimedia Foundation*
Hello,
In accordance with CoC's amendment policy
<https://www.mediawiki.org/wiki/Code_of_Conduct/Amendments>. The committee
proposes an amendment on behalf of one of the community members to be added
in unacceptable behavior section
<https://www.mediawiki.org/wiki/Code_of_Conduct#Unacceptable_behavior>:
Soliciting help, support or technical assistance for websites whose
predominant activity or content is behaviour that explicitly and
significantly violates provisions of the code of conduct is forbidden in
Wikimedia technical spaces. For example, websites advocating violence or
hate speech are not welcome to ask for support on Wikimedia support forums.
This is similar to w:en:Wikipedia:No Nazis
<https://en.wikipedia.org/wiki/en:Wikipedia:No%20Nazis>
This will be open for three months for community feedback in
https://www.mediawiki.org/wiki/Topic:Xgg6dvg2athdb1h7 and if the community
reaches consensus and the committee won't oppose it, It will be added to
the policy.
Best
Amir (he/him),
On behalf of the CoC committee
Hi Everyone,
We are trying to workaround failed backups due to
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/2003866 . We
used to use --single-transaction, but the option now requires RELOAD
or FLUSH_TABLES. We failed to enable the privileges for the mwuser.
MediaWiki's backup documentation is at
https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki . Here is the
command MediaWiki recommends:
mysqldump -h hostname -u userid -p \
--default-character-set=whatever dbname > backup.sql
But the article does not discuss how to ensure consistency for the
database and dump file. For MySQL, that should be --single-transaction
or --lock-tables. (If I am reading the MySQL documentation correctly).
My question is, what should we use to ensure consistency of the dump file?
--single-transaction or --lock-tables or something else?
Jeff