Changing a crucial element of the fifth most popular website on the
Internet may be a good example for an article about [[PITA]] :D
While I'm open to new formats/technologies I think a fundamental
prerequisite is a widespread support among browsers/clients. JS-only
support will severely weaken
An encode latency of 7 seconds and decode latency of 1 second arent what I
would call "very fast" (the decode latency measurement probably isnt
realistic as decode and encode to png is different from just display in
browser. Then again all these measurements are going to vary by filesize,
not to
Personally, I've wanted to do away with having a settings file in PHP
entirely, and rather do something closer to how Drupal 8 handles
configurations. With the current state of configuration, its not reliably
possible to know how a wiki is configured automatically. Making any sort of
On Mon, Dec 4, 2017 at 10:34 AM Ruben Kelevra wrote:
> > Sure, your suggestion avoids a lot of this. But the CPUs involved will
> > experience heavy load, both on the server as well as clients that need
> > to recode FLIF files via a JavaScript library first.
> FLIF is very
Unfortunately, I had to revert it. We'll try again later when the schema
change is compete.
On Mon, Dec 4, 2017 at 2:38 PM, Brad Jorsch (Anomie)
wrote:
> I've just now enable the feature flag on the testing wikis[1][2][3] that
> allows MediaWiki to store comments longer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I've written an RfC to introduce a standardized and recommended way
for re-distributors and packagers of MediaWiki to be able to tune
DefaultSettings.php as appropriate.
You can read more details on-wiki[1], and discuss it on Phabricator[2].
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
For a while now, Wikimedia has been restricting the different binaries
that we shell out to (mostly image handling things) with firejail[1].
This was a manual process by writing wrapper scripts that invoked
firejail, and pointing MediaWiki to
I've just now enable the feature flag on the testing wikis[1][2][3] that
allows MediaWiki to store comments longer than 255 bytes.
The web UI has not been updated to allow longer comments in places where it
enforces a limit, such as the edit summary box. But if you use the API to
edit, or perform
Forwarding as engineering@ is rarely used anymore.
Thanks Timo.
- Forwarded message from Timo Tijhof -
> Date: Fri, 1 Dec 2017 18:42:26 -0800
> From: Timo Tijhof
> To: Engineering
> Subject: [Engineering]
Hey Thiemo,
On 04.12.2017 10:43, Thiemo Kreuz wrote:> I consider myself an image
file format nerd, so thanks a lot for
> sharing this! FLIF was new to me.Don't mind it! :)
> I would like to share two important notes:
>
> 1. Unfortunately the flif.info website does not say a word about the
> CPU
Hey,
I consider myself an image file format nerd, so thanks a lot for
sharing this! FLIF was new to me.
I would like to share two important notes:
1. Unfortunately the flif.info website does not say a word about the
CPU resources their current implementation burns when converting a,
let's say,
11 matches
Mail list logo