[Wikitech-l] Re: 3D models in Commons

Based on my prior research I'm pretty sure GLTF support -- a well-supported modern format that allows textures -- is not a huge amount of work to add. Mostly needs cleanup of the old code & updating dependencies, and adding appropriate validation. I am planning to get to that this year, after we

[Wikitech-l] Re:  Amir Sarabadani receives Web Perf Hero award!

On Thu, May 26, 2022 at 7:22 AM Krinkle wrote: > I'm happy to share that the first Web Perf Hero award of 2022 goes to Amir > Sarabadani! > > This award is in recognition of Amir's work (@Ladsgroup) over the past six > months, in which he demonstrated deep expertise of the MediaWiki platform >

[Wikitech-l] Re: [Commons-l] Uplifting the multimedia stack (was: Community Wishlist Survery)

(Anyway I'm just grumping. I hear positive things about plans for this year and I'm heartened to see more folks involved in planning the next stages!) -- brion On Mon, Jan 3, 2022, 6:10 AM Brion Vibber wrote: > On Thu, Dec 30, 2021, 10:27 AM Samuel Klein wrote: > >> Separate

[Wikitech-l] Re: [Commons-l] Uplifting the multimedia stack (was: Community Wishlist Survery)

On Thu, Dec 30, 2021, 10:27 AM Samuel Klein wrote: > Separate thread. I'm not sure which list is appropriate. > *... but not all the way to sentience > .* > > The annual community wishlist survey (implemented by a small team, > possibly in

Re: [Wikitech-l] Startup module size and ResourceLoader registry overhead

TimedMediaHandler is particularly bad at this right now because it's still in the middle of a switch from an old set of frontend modules to a new one, so we have to register both. :) I'll make sure we chop the old ones out soon... -- brion On Mon, Sep 16, 2019 at 2:11 PM Amir Sarabadani wrote:

Re: [Wikitech-l] Gerrit Vandalism

Just a quick note: incident response is active and ongoing; this is being worked on. -- brion On Mon, Mar 18, 2019, 10:54 PM Eran Rosenthal wrote: > I couldn't catch anyone in the IRC so this is also tracked in: > https://phabricator.wikimedia.org/T218636 > > On Tue, Mar 19, 2019 at 7:40 AM

Re: [Wikitech-l] [Commons-l] Sunsetting VP8 version of WebM for video playback

On Mon, Feb 4, 2019, 2:26 PM Gergo Tisza On Mon, Jan 28, 2019 at 12:22 PM Brion Vibber via Commons-l < > common...@lists.wikimedia.org> wrote: > >> IE 11 users will receive low-resolution, slow JavaScript-based video >> playback instead. If you find this is troublesome,

Re: [Wikitech-l] IE 6/7 MIME type sniffing checks on uploads - is it time to retire them?

On Mon, Jan 28, 2019 at 10:58 PM Kunal Mehta wrote: > Tim wrote a nice blog post about how he reverse-engineered this: > . > > I don't have any comments on whether it's still needed, but if it's > determined that MediaWiki can drop the

[Wikitech-l] IE 6/7 MIME type sniffing checks on uploads - is it time to retire them?

There's been some comments on some old tasks such as T27707 about problems with uploading files that include text metadata that looks like HTML elements. Years ago, we added security checks for IE 5/6/7 to work around IE's mime type sniffing: if you went

[Wikitech-l] Sunsetting VP8 version of WebM for video playback

A few months ago I switched our TimedMediaHandler's config to support the newer, more bandwidth-efficient VP9/Opus variant of WebM and to use these preferably over the older VP8/Vorbis version when creating scaled, playback-ready derivatives. (This does not affect upload support -- you may

[Wikitech-l] Reviving 'EmbedScript' extension for sandboxed JavaScript widgets

Hey all! I'm reviving an old project to embed sandboxed HTML/JavaScript "widgets" into wiki pages as a click-to-play media type, using modern browsers' sandbox and Content-Security-Policy restrictions. Intro and detail notes which I'll keep updating:

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

the old VP8 versions to free up space. -- brion On Mon, Sep 10, 2018 at 12:05 PM Brion Vibber wrote: > These conversions have been running in the background, at a moderate load > to ensure we don't slow down newer uploads much, and are up to the "P"s > alphabetically s

Re: [Wikitech-l] problematic use of "Declined" in Phabricator

*nods* I think the root problem is that the phabricator task system does double duty as both an *issue reporting system* for users and a *task tracker* for devs. An issue reporting system should capture all actual problems and all actual suggestions, and is meant to provide visibility for the

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

l continue once it's switched. -- brion On Wed, Aug 8, 2018 at 2:06 PM Brion Vibber wrote: > Quick update... no major problems noticed so far. One configuration change > I made was to re-enable VP8 transcodes for new files, since disabling them > completely lead to the existing ones no

[Wikitech-l] MediaWiki-Vagrant users beware: vagrant 2.1.4 breakage

HashiCorp has released a 2.1.4 update to Vagrant -- beware that this version changes the order of plugin loading in a way that breaks on MediaWiki-Vagrant's configuration file. It should be fixable on our end, but for now either stick with the version of Vagrant you have installed, or downgrade

Re: [Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

On Tue, Aug 14, 2018 at 8:34 AM Brion Vibber wrote: > On Tue, Aug 14, 2018, 3:39 AM Aleksey Bekh-Ivanov < > aleksey.bekh-iva...@wikimedia.de> wrote: > >> Hi Brion. >> >> I might be a bit late, but I just wonder why did you decide to go with >> fo

Re: [Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

tps://github.com/krakjoe/pthreads > > Aleksey, Wikimedia Deutschland > > On 13 August 2018 at 02:51, Brion Vibber wrote: > > > Thanks, looks like I misinterpreted the report output. :) > > > > I think I can add a test case for ParallelMaintenance which should make >

Re: [Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

n 08/11/2018 06:48 PM, Brion Vibber wrote: > > Second, probably related to that I'm seeing a failure in the code > > coverage calculations -- it's seeing some increased coverage on the > > parent process at least but seems to think it's returning a > > non-zero exit code

Re: [Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

(I've made both changes on the PR.) -- brion On Sun, Aug 12, 2018 at 7:54 AM Brion Vibber wrote: > > On Sun, Aug 12, 2018, 2:49 AM Aryeh Gregor wrote: > >> >> For what it's worth, when I saw ForkableMaintenance I thought of >> forking an open-source project, not U

Re: [Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

On Sun, Aug 12, 2018, 2:49 AM Aryeh Gregor wrote: > > For what it's worth, when I saw ForkableMaintenance I thought of > forking an open-source project, not Unix fork(). Something like > ParallelMaintenance or ParallelizableMaintenance would better suggest > the desired meaning for me. > I

[Wikitech-l] ForkableMaintenance: thoughts and help with tests/code coverage

Hey all! While working on some maintenance scripts for TimedMediaHandler I've been trying to make it easier to do scripts that use multiple parallel processes to run through a large input set faster. My proposal is a ForkableMaintenance class, with an underlying QueueingForkController which is a

Re: [Wikitech-l] (no subject)

just as we are when they choose to work alongside us. Not sure about the language references; they don't seem relevant to the patterns of behavior under discussion. -- brion On Wed, Aug 8, 2018, 4:18 PM MZMcBride wrote: > Brion Vibber wrote: > >I would advise you generally to tr

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

did 5% of stuff), depending on actual factors like whether the remaining files are the same mix of resolutions, and how we adjust the load balance on the job queue. -- brion On Fri, Aug 3, 2018 at 11:22 AM Brion Vibber wrote: > Batch process is continuing... over 2200 source videos have b

Re: [Wikitech-l] coc ban

Oleg -- I interpret that suggestion as "employees of WMF and WMDE have to accept all ongoing abuse they are given without complaint"; that may not be what you intended but that's how I read it, and I'd like to unequivocally *reject that notion*. WMF and WMDE employees are people performing a job,

Re: [Wikitech-l] (no subject)

Hi Dennis. I would advise you generally to treat wikitech-l like a professional workspace, which it is for those of us who are employees of WMF or WMDE. If your corporate HR department would frown at you making a statement about people's character or motivations with derogatory language, think

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

everything, and we may or may not want to increase the number of simultaneous jobs (so far the servers are running beautifully, but are a bit under-loaded). -- brion On Mon, Jul 30, 2018 at 5:51 PM Brion Vibber wrote: > Configuration has been updated and VP9 mode swapped in. Newly uploaded &g

Re: [Wikitech-l] [Multimedia] phone cannot play mobile site video, but standard site video

Our old video player frontend doesn't quite work right on mobile so we've been migrating towards a modern one based on video.js, which does work on mobile and can integrate with our Safari compatibility shim. It's been blocked on some issues with subtitle compatibility, which I'll be working on

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

, with the patches and review, and with final deployment which always takes longer than you expect. :) This'll be a nice improvement to our video output for now, and lays a lot of groundwork for next steps. -- brion On Thu, Jul 26, 2018 at 5:47 PM Brion Vibber wrote: > Oh and one more th

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

y on a smaller screen is the > same, i did not verify on a high resolution screen if a difference can > be noticed. > > rupert > > > On Fri, Jul 27, 2018 at 2:47 AM, Brion Vibber > wrote: > > Oh and one more thing! > > > > For the VP9 configuration I'll be e

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

at we have more available. (Note that the ogv.js player shim for Safari will not handle greater-than-HD resolutions fast enough for playback, even on a fast Mac or iPad; for best results for 4K playback use Firefox, Chrome, or a Chromium-based browser.) -- brion On Thu, Jul 26, 2018 at 5:39 PM Br

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

. -- brion On Fri, Jun 29, 2018 at 9:46 AM Brion Vibber wrote: > Awesome sauce. Thanks Moritz! > > -- brion > > On Fri, Jun 29, 2018 at 7:39 AM Moritz Muehlenhoff < > mmuhlenh...@wikimedia.org> wrote: > >> Hi all, >> >> On Thu, Jun 28, 2018 at 01:54:18PM

Re: [Wikitech-l] AV1? (was Re: [Multimedia] Video output changing to WebM VP9/Opus soon)

yalty-free-web-video-codecs/> > > On Fri, Jun 29, 2018 at 6:46 PM, Brion Vibber > wrote: > > > Awesome sauce. Thanks Moritz! > > > > -- brion > > > > On Fri, Jun 29, 2018 at 7:39 AM Moritz Muehlenhoff < > > mmuhlenh...@wikimedia.org

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

Awesome sauce. Thanks Moritz! -- brion On Fri, Jun 29, 2018 at 7:39 AM Moritz Muehlenhoff < mmuhlenh...@wikimedia.org> wrote: > Hi all, > > On Thu, Jun 28, 2018 at 01:54:18PM -0700, Brion Vibber wrote: > > Current state on this: > > > > * still hoping to deploy

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

rate will end up scaled according to frame rate, but frame rate is surprisingly hard to calculate reliably for WebM input.) -- brion On Sun, Jun 17, 2018 at 1:32 PM Brion Vibber wrote: > On Sun, Jun 17, 2018 at 12:30 PM Brian Wolff wrote: > >> Woo! >> >> Good to see us

Re: [Wikitech-l] [Multimedia] Video output changing to WebM VP9/Opus soon

On Sun, Jun 17, 2018 at 12:30 PM Brian Wolff wrote: > Woo! > > Good to see us moving forward to newer codecs. > :D > What is the expected impact on transcode time/memory usage? (As in, will > large videos still transcode fine or would they potentially hit limits > sooner?) > Using the same

[Wikitech-l] Video output changing to WebM VP9/Opus soon

In the next couple weeks I'm planning to start switching our video transcode output from WebM VP8/Vorbis to the newer WebM VP9/Opus profile, which saves us about 38% on file size and bandwidth while retaining the same quality. This will not affect what kinds of files you upload; only the scaled

Re: [Wikitech-l] Gerrit as a shared community space

I'd just like to apologize for dragging the other thread into this one and being overly personal and failing to assume good faith. That was a failing on my part, and not good practice. Please if you respond further to this thread, treat only the narrow issue of ownership / maintainership

Re: [Wikitech-l] Gerrit as a shared community space

On Sat, Jun 9, 2018 at 10:55 AM Isarra Yos wrote: > Perhaps I was too subtle the last time I hinted at this: this is toxic. > What you and others are doing misrepresenting what others are saying, > the general heavy-handedness, the implications that anyone against a > specific aspect of

Re: [Wikitech-l] Gerrit as a shared community space

On Sat, Jun 9, 2018 at 10:21 AM Alex Monk wrote: > On 9 June 2018 at 18:14, Brion Vibber wrote: > > > On Sat, Jun 9, 2018 at 10:00 AM Alex Monk wrote: > > > > > This is outrageous. Not only are you blatantly misrepresenting what > > various > >

Re: [Wikitech-l] Gerrit as a shared community space

veto others' clarifications. And sometimes an admit makes an edit stick that you don't like. > It is incredibly ironic how against the spirit of the CoC this all is. Can you clarify? -- brion > > On 9 June 2018 at 16:58, Brion Vibber wrote: > > > Recent threads have demon

[Wikitech-l] Gerrit as a shared community space

Recent threads have demonstrated there seems to be some disconnect about what is expected about maintainership and ownership of repositories. This has spilled over into talk about the code of conduct, IMHO specifically because some people are trying to avoid being bound by it or protesting its

Re: [Wikitech-l] Planet Wikimedia using new software "rawdog"

On Wed, May 30, 2018, 7:22 PM Daniel Zahn wrote: > On Wed, May 30, 2018 at 6:57 PM, Brion Vibber > wrote: > > > ... Well, that's a bit of an unfortunate name. o_O > > > > :p "rawdog is an RSS Aggregator Without Delusions Of Grandeur" > Perhaps. I wo

Re: [Wikitech-l] Planet Wikimedia using new software "rawdog"

On Wed, May 30, 2018 at 6:34 PM Daniel Zahn wrote: > this is an announcement to let you know that the service ($lang). > planet.wikimedia.org, an RSS feed aggregator for all Wikimedia related > blogs, has switched software. > > Thanks for the maintenance! > > Today we moved away from

Re: [Wikitech-l] MediaWiki 1.31 branch (and PHP versions)

Exciting times! Looking forward to our PHP 7 future, if not just yet. :D -- brion On Fri, Apr 20, 2018 at 4:54 PM, Chad wrote: > Hi, > > I meant to send this Tuesday but I forgot. > > MediaWiki 1.31 has been branched from master! You should now see a REL1_31 > branch

Re: [Wikitech-l] First step for MCR merged: Deprecate and gut the Revision class

On Dec 22, 2017 3:03 PM, "C. Scott Ananian" wrote: I think a simple revert would be simplest. Adding a feature flag adds new possibilities of overlooked bugs, especially since this is "just" a refactoring and so *in theory* shouldn't be changing anything. Agreed, it's

Re: [Wikitech-l] First step for MCR merged: Deprecate and gut the Revision class

Woohoo! The pieces fall in place... :) -- brion On Dec 22, 2017 2:27 AM, "Daniel Kinzler" wrote: > Hello all! > > Addshore last night merged the patch[1] that is the first major step > towards > Multi-Content-Revisions[2]: it completely guts the Revision class and

[Wikitech-l] Best practices for WebAssembly and compiled JS in front-end modules?

The latest version of all major browsers support C/C++/etc code compiled to WebAssembly ("wasm") format, in addition to the older "asm.js" style of compilation targeting a subset of JavaScript directly. As far as I know the first library that MediaWiki uses to support

Re: [Wikitech-l] HHVM vs. Zend divergence

On Mon, Sep 18, 2017 at 1:58 PM, Max Semenik wrote: > 2) Declare our loyalty to HHVM. This will result in most of our current > users being unable to upgrade, eventually producing what amounts to a > WMF-only product and lots of installations with outdated MediaWiki having

Re: [Wikitech-l] How does a build process look like for a mediawiki extension repository?

For JS dependencies, image optimizations etc the state of the art still seems to be to have a local one-off script and commit the build artifacts into the repo. (For instance TimedMediaHandler fetches some JS libs via npm and copies/patches them into the resources/ dir.) For PHP deps we've got

Re: [Wikitech-l] Turkey ban

The apps aren't currently designed with network-level blocking circumvention in mind. It's certainly possible to be much more resilient especially to something simple like a DNS blacklist, but: * anything we do starts an arms race where smarter blocking could block that too * the apps are open

Re: [Wikitech-l] Questions over usage of ObjectCache

I've filed a task in phabricator to follow up in case there's any surprises with the proposed fix. :) https://phabricator.wikimedia.org/T162077 -- brion On Mon, Apr 3, 2017 at 11:52 AM, Brion Vibber <bvib...@wikimedia.org> wrote: > On Mon, Apr 3, 2017 at 12:56 AM, Nischay Nahata

Re: [Wikitech-l] Questions over usage of ObjectCache

On Mon, Apr 3, 2017 at 12:56 AM, Nischay Nahata wrote: > > I have been trying to add certain rate limiting actions for my extension's > API and noticed that it doesn't work with $wgMainCacheType set to > CACHE_NONE > > This is because User::pingLimiter() > uses

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

Summary from March 8 irc meeting: https://tools.wmflabs.org/meetbot/wikimedia-office/2017/wikimedia-office.2017-03-08-22.03.html -- brion On Mon, Mar 6, 2017 at 9:43 AM, Brion Vibber <bvib...@wikimedia.org> wrote: > On Wed, Feb 15, 2017 at 3:06 PM, Brion Vibber <bvib...@wikimedia.

[Wikitech-l] Code of Conduct for Wikimedia technical spaces now out of draft state

Per the last round of discussion & votes closing on the amendments section some days back, the draft period for the Code of Conduct for technical spaces is complete. I've taken the liberty of removing the 'draft' template and moving the pages out of their "/Draft" subpage location to their final

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

On Wed, Feb 15, 2017 at 3:06 PM, Brion Vibber <bvib...@wikimedia.org> wrote: > Great feedback everybody -- I'll make more updates and we'll circle back > for another discussion in a week or two! > > Meeting summary (full logs linked from there): > https://tools.wmflabs.

Re: [Wikitech-l] SHA-1 hash officially broken

ikitech-l-boun...@lists.wikimedia.org] Im > Auftrag von Brion Vibber > Gesendet: Freitag, 24. Februar 2017 19:48 > An: Wikimedia developers <wikitech-l@lists.wikimedia.org> > Betreff: Re: [Wikitech-l] SHA-1 hash officially broken > > On Fri, Feb 24, 2017 at 10:34 AM,

Re: [Wikitech-l] SHA-1 hash officially broken

On Fri, Feb 24, 2017 at 10:34 AM, Florian Schmidt < florian.schmidt.wel...@t-online.de> wrote: > I searched in phabricator, if we've a task already, but couldn't find any. > However, as the phabricator search and me aren't really good friends, it's > possible, that the search wasn't as honest to

[Wikitech-l] SHA-1 hash officially broken

Google security have announced that they have a working collision attack against the SHA-1 hash: https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html It's highly recommended to move to sha-256 where doable. Note that MediaWiki uses sha-1 in a number of places; in some

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

PM, Brion Vibber <bvib...@wikimedia.org> wrote: > Correction: 22:00 UTC / 2pm PST in #wikimedia-office. Sorry, I calculated > with the wrong time by mistake! > > -- brion > > On Tue, Feb 14, 2017 at 10:38 AM, Brion Vibber <bvib...@wikimedia.org> > wrote: > >&

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

Correction: 22:00 UTC / 2pm PST in #wikimedia-office. Sorry, I calculated with the wrong time by mistake! -- brion On Tue, Feb 14, 2017 at 10:38 AM, Brion Vibber <bvib...@wikimedia.org> wrote: > Whoops I forgot to mention in the list post -- we're planning to talk > abou

Re: [Wikitech-l] MediaWiki-Vagrant needs testers for Debian Jessie changes

Yesss! :) I'll test over the next few days. -- brion On Wed, Feb 15, 2017 at 2:53 AM, Bryan Davis wrote: > TL;DR See and try the new > jessie-migration branch. > > > The Wikimedia Foundation has been working on converting the

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

and that'll be in #wikimedia-office on irc.freenode.net. :) -- brion On Tue, Feb 14, 2017 at 10:38 AM, Brion Vibber <bvib...@wikimedia.org> wrote: > Whoops I forgot to mention in the list post -- we're planning to talk > about this topic in the public ArchCom IRC meeting this W

Re: [Wikitech-l] Provisional notes for proposed revision table restructuring

at 9:28 AM, Brion Vibber <bvib...@wikimedia.org> wrote: > I've got an early draft of some notes > <https://www.mediawiki.org/wiki/User:Brion_VIBBER/Compacting_the_revision_table_round_2> > for a restructuring of the revision table, to support the following: > > * makin

[Wikitech-l] Provisional notes for proposed revision table restructuring

I've got an early draft of some notes for a restructuring of the revision table, to support the following: * making the revision table itself smaller by breaking large things out * reducing duplicate string

Re: [Wikitech-l] [Wikivideo-l] Video transcode prioritization changes in progress

Looks like the high-prio queue is back to normal, all is well. :) Please continue uploading. -- brion On Thu, Feb 9, 2017 at 5:02 PM, James Hare <jamesmh...@gmail.com> wrote: > Should people refrain from uploading videos at this time? > > > On February 9, 2017 at 5:01:51 PM,

Re: [Wikitech-l] [Wikivideo-l] Video transcode prioritization changes in progress

bs without disturbing things... -- brion On Thu, Feb 9, 2017 at 12:00 PM, Brion Vibber <bvib...@wikimedia.org> wrote: > Ok, the video scaler queue change is now live: SD and low-resolution video > output runs on a new, high-priority queue, with HD video output and > transcodes

Re: [Wikitech-l] [Wikivideo-l] Video transcode prioritization changes in progress

AM, Brion Vibber <bvib...@wikimedia.org> wrote: > We're in progress of deploying a small change to the video scalers[1], > which should improve availability of newly uploaded video and audio files. > > The queue will now be split in two, one which covers low-resolution > conve

[Wikitech-l] Video transcode prioritization changes in progress

We're in progress of deploying a small change to the video scalers[1], which should improve availability of newly uploaded video and audio files. The queue will now be split in two, one which covers low-resolution conversions for relatively short files, and one which covers long files and

Re: [Wikitech-l] More useful Puppet docs for MediaWiki-Vagrant

Nice! I like that by expanding the 'source' option I can see dependencies as well as what it's actually doing in terms of config etc. The textual descriptions of the roles are mostly pretty vague so far; should we expand them for instance to describe what will be installed and how to go about

[Wikitech-l] No ArchCom IRC meeting this week

ArchCom IRC meeting was canceled for this week; sorry for the lack of announcement! -- brion ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] ParserAfterParse not called by VisualEditor?

On Sat, Oct 8, 2016 at 5:37 PM, James HK wrote: > Hi, > > > VE's edits should be (indirectly) going through the action=edit API. > > I'm not sure this answer is very helpful. To translate: "it should work exactly the same as edits made with the API", or to

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

On Thu, Sep 1, 2016 at 11:11 AM, bawolff wrote: > Yes, we certainly do have issues with follow-through on summit decisions. > *nod* > For me personally, I've found the dev summits mostly useful as a > community building type thing (For the MediaWiki developer community).

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

On Thu, Sep 1, 2016 at 10:32 AM, Brian Wolff wrote: > Last year there was an attempt to sort of do this (mostly by extending the > word "developer" to mean new things). Largely those types of people didnt > attend (although there were a few exceptions), however I remember

[Wikitech-l] Opening up MediaWiki dev summit in January?

The last couple years we've done a big MediaWiki Dev Summit in January, around the time of the Wikimedia Foundation all-hands meeting. Invitations have been fairly broad to known developers, but there's a very strong feeling that newbies, non-technical people, and in general *the people MediaWiki

Re: [Wikitech-l] [WikimediaMobile] Mobile site is now lazy loading images

Awesome! This will also make it easier to experiment with alternate delivery formats: WebP, direct SVG usage, etc that depend on knowing whether there's client-side support. I'll fire up some more research... :D -- brion On Tue, Aug 23, 2016 at 2:20 PM, Jon Robson wrote:

Re: [Wikitech-l] Better search results on wiki via TextCat

That is super awesome! :D -- brion On Tue, Jul 19, 2016 at 6:41 PM, Deborah Tankersley < dtankers...@wikimedia.org> wrote: > We're happy to announce that after numerous tests and analyses[1] and a > fully operational demo[2], the Discovery Team is ready to release > TextCat[3] into production

Re: [Wikitech-l] What's the "correct" content model when rev_content_model is NULL?

On Tuesday, July 12, 2016, Daniel Kinzler wrote: > Am 12.07.2016 um 18:00 schrieb Rob Lanphier: > > On Tue, Jul 12, 2016 at 1:40 AM, Daniel Kinzler < > daniel.kinz...@wikimedia.de > >> The original design of ContentHandler used integer IDs for content

Re: [Wikitech-l] Crediting the work of our community members

On Mon, Jul 4, 2016 at 9:06 AM, Jon Robson wrote: > Sorry I dropped the ball on this. > I've created the following 2 actionable tasks: > https://phabricator.wikimedia.org/T139300 > https://phabricator.wikimedia.org/T139301 > > I hope we can reach a decision somewhat promptly

[Wikitech-l] Exploring VP9 as a progressive still image codec

I spent some time between projects today exploring the idea of progressive image decoding using the VP9 video codec -- sort of a mashup of progressive JPEG and WebP. Like a progressive JPEG, each resolution step (a separate frame of the "video") encodes only the differences from the previous

[Wikitech-l] File handler options & InstantCommons (was Re: Update from the Perf Team)

On Sun, May 29, 2016 at 11:22 AM, Gergo Tisza <gti...@wikimedia.org> wrote: > On Sun, May 29, 2016 at 7:08 PM, Brion Vibber <bvib...@wikimedia.org> > wrote: > > We could change all that if there was a stable enough URL/linking > > API... Can probably fake it

Re: [Wikitech-l] [Engineering] Update from the Perf Team

On Saturday, May 28, 2016, Brian Wolff wrote: > Pages with large number of thumbnails tends to be a slow path in the > parser. This is even more true for people using instant commons. I dont > know for sure, but I imagine it could be improved by batching the checks > for

Re: [Wikitech-l] Reviving SVG client-side rendering task

On Fri, May 13, 2016 at 1:28 PM, Jon Robson wrote: > Thanks for starting this conversation Brion! > > On mobile we are constantly tackling the trade offs between data > shipped (cost for end user) and quality. Hopefully we'll have a better > solution for this by the end of

Re: [Wikitech-l] Reviving SVG client-side rendering task

On Wed, May 11, 2016 at 11:10 AM, Chris Steipp <cste...@wikimedia.org> wrote: > On Thu, May 5, 2016 at 6:49 AM, Brion Vibber <bvib...@wikimedia.org> > wrote: > > > > > And then there are long term goals of taking more advantage of SVGs > dynamic > > natur

Re: [Wikitech-l] [Mediawiki-i18n] Providing the effective language of messages

Tagging language and directionality on fallback entries sounds reasonable, and not a huge addition. I'm not sure why the fallbacks are cached in the main body instead of letting them through to the backing language's cache, but if that's a necessary or useful choice I've no reason to hop in and

Re: [Wikitech-l] ResourceLoader addModuleStyles() issues

On Monday, May 9, 2016, Krinkle <krinklem...@gmail.com> wrote: > On Wed, May 4, 2016 at 1:43 PM, Brion Vibber <bvib...@wikimedia.org > <javascript:;>> wrote: > > > Quick notes on the migration path: > > > > > > *Cached page HTML* > > &

Re: [Wikitech-l] historical trivia: who first picked UTC as Wikimedia time, when and why?

In 2001 when Magnus was writing the initial attempt at a custom wiki engine in PHP backed by MySQL, he chose to use the TIMESTAMP column type. TIMESTAMPs in MySQL 3 were automatically filled out by the server at INSERT time, normalized to UTC, and exposed in the 14-digit MMDDHHMMSS format we

Re: [Wikitech-l] Reviving SVG client-side rendering task

On Thursday, May 5, 2016, Brad Jorsch (Anomie) <bjor...@wikimedia.org> wrote: > On Thu, May 5, 2016 at 9:49 AM, Brion Vibber <bvib...@wikimedia.org > <javascript:;>> wrote: > There's also the font issue: with the current rasterizing, only certain > free fonts

[Wikitech-l] Reviving SVG client-side rendering task

For the last decade we've supported uploading SVG vector images to MediaWiki, but we serve them as rasterized PNGs to browsers. Recently, display resolutions are going up and up, but so is concern about low-bandwidth mobile users. This means we'd like sharper icons and diagrams on high-density

Re: [Wikitech-l] Phabricator upgrade and UI changes

I find it very aggravating the that the author of a task is now very far away on screen from their comment. Makes it difficult to tell what's going on and harder to target a reply directly at them. -- brion On Wed, May 4, 2016 at 8:57 AM, Federico Leva (Nemo) wrote: >

Re: [Wikitech-l] ResourceLoader addModuleStyles() issues

On Wed, May 4, 2016 at 8:23 AM, Brad Jorsch (Anomie) wrote: > On Wed, May 4, 2016 at 6:34 AM, Krinkle wrote: > > [1] If one would allow page style modules to have dependencies and > resolve > > them server-side in the HTML output, this would cause

Re: [Wikitech-l] ResourceLoader addModuleStyles() issues

Quick notes on the migration path: *Cached page HTML* HTML cached under the old regime would still be served for a while, but ResourceLoader would load the newer style. I *think* that should work as long as the new versions of the modules that were included before still list the style-only

[Wikitech-l] ImageMagick reported security vulnerability

There's a reported ImageMagick security vulnerability making the rounds: http://arstechnica.com/security/2016/05/easily-exploited-bug-exposes-huge-number-of-sites-to-code-execution-attacks/ Many MediaWiki sites are configured to use ImageMagick's 'convert' command to perform image

Re: [Wikitech-l] Getting rid of $wgWellFormedXml = false;

I'd say an HTML5 output mode *ought* to work like this: *Don't try to be clever.* * Consistency and predictability are key to both security review and data consumability. *Quote attributes consistently and predictably.* * Always use double-quotes on attributes in output. *Output specced empty

Re: [Wikitech-l] Rob Lanphier appointed to the Architecture Committee

Woot! -- brion On Monday, April 25, 2016, Tim Starling wrote: > At the previous meeting of the MediaWiki Architecture Committee (April > 20), the members present approved the appointment of Rob Lanphier to > the committee. > > Rob was the main instigator in the

[Wikitech-l] Docs, use of, and admin privileges for wikimedia github project?

There seems to be extremely little documentation on Wikimedia's GitHub project https://github.com/wikimedia ... I can only find https://www.mediawiki.org/wiki/Gerrit/GitHub which mostly says we mirror a bunch of stuff from gerrit. And I know we have continuous integration of some kind set up for

Re: [Wikitech-l] ResourceLoader, latency, & progressive enhancement

on -- are even more important and should not regress or we will be sad pandas. :) /me gets on a plane, will comment more later -- brion On Monday, April 25, 2016, Brion Vibber <bvib...@wikimedia.org> wrote: > On Monday, April 25, 2016, Ori Livneh <o...@wikimedia.org > <javascript:_

Re: [Wikitech-l] ResourceLoader, latency, & progressive enhancement

On Monday, April 25, 2016, Ori Livneh wrote: > Not so straight-forward. Khan Academy tried unbundling JavaScript on HTTP/2 > page views last November and found that performance got worse. They > attribute the regression primarily to the fact that bundling improves >

Re: [Wikitech-l] ResourceLoader, latency, & progressive enhancement

support neither: http://caniuse.com/#feat=spdy http://caniuse.com/#feat=http2 -- brion > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] > > On 2016-04-23 3:08 PM, Brion Vibber wrote: > > Started as quick thoughts, turned into more of an essay, so I've posted &

[Wikitech-l] ResourceLoader, latency, & progressive enhancement

Started as quick thoughts, turned into more of an essay, so I've posted the bulk on mediawiki.org: https://www.mediawiki.org/wiki/User:Brion_VIBBER/ResourceLoader_and_latency tl;dr summary: On slow networks, latency in loading large JS and HTML resources means things don't always work right

Re: [Wikitech-l] Best practices for read/write vs read-only requests, and our multi-DC future

infrastructure to make sure we're handling those jobs reliably on small sites without dedicated job runners. -- brion On Apr 21, 2016 5:26 PM, "Brion Vibber" <bvib...@wikimedia.org> wrote: > On Thu, Apr 21, 2016 at 4:59 PM, Erik Bernhardson < > ebernhard...@wikimedia.org> wr

  1   2   3   4   5   6   7   8   9   10   >