Looks like the same as in T398391: Server side upload for CMBGAMER 2018 (which was opened through v2c) - I'm guessing the task layout may have been copied from there

Where though?

It's from C-SPAN

I note it came down as a 2.4G MP4 file...

There may be some different access and/or speed for those in the US or those outside...

Normally I'd just go to video2commons and insert the link, but for this video, it keeps saying error, so I opened a task for it here

Is there an easier way to download these than yt-dlp or similar?

In T397024#10965034, @A_smart_kitten wrote:

(Also, not to badger about it too much, but I would be very grateful if the 'tags' field for the server-side-upload form could be unlocked :D / cc @Aklapper)

Closing as declined, as unfortunately the video2commons URL in the task description seems to no longer be available.

FYI, Server-side upload queues are currently unmaintained, and requests are not guaranteed to be handled in a reasonable timeframe. It is possible that no-one will handle your request.
The general advice is to upload files using the Upload Wizard if you can, and to file a bug report if the Upload Wizard does not work for you.

To be fair, technically this task was for a Herald rule; but the video2commons URL update may have solved (or at least, helped with) the root cause behind my request — ie., v2c server-side-upload-requesters not being made aware that the queue is currently unmaintained.

Changes deployed. I guess this is fixed now, please reopen if not.

Re-closing, as those three URLs now no longer work for me either unfortunately

For one person, me, as I used the presence of that tag when creating this task to quickly estimate what proportion of server-side-upload requests came from v2c :P

Hmm, "task tracking"... who exactly cares and for which reason? :)

@Aklapper slight side note — assuming that PR goes through, please could you unlock the 'tags' field on form 106, so that the auto-generated form link can also add video2commons (for task tracking purposes)?

I admit I've also thought about this.
The better approach however would be fixing the underlying issue and deploying (!) an updated version of video2commons, similar to https://github.com/toolforge/video2commons/issues/207.

In T391469#10725916, @Aklapper wrote:

I updated https://phabricator.wikimedia.org/transactions/editengine/maniphest.task/view/106/

https://commons.wikimedia.org/wiki/File:Can_Couples_Find_Perfect_Places_In_Aberdeen-_-_S11_Ep6_-_Full_Episode_-_Location,_Location,_Location.webm seems to have uploaded successfully anyway.

See T393851

Weird. It *did* in fact upload at https://commons.wikimedia.org/wiki/File:President_Trump_Delivers_Remarks_at_the_Governors_Working_Session.webm

https://commons.wikimedia.org/wiki/File:1925._%D0%A1%D1%82%D0%B5%D0%BF%D0%B0%D0%BD_%D0%A5%D0%B0%D0%BB%D1%82%D1%83%D1%80%D0%B8%D0%BD.webm Seems to have uploaded just fine the normal way.

Anyways, closing this bug since the file is uploaded.

Looking at logs, it looked like what happened is there were two publish jobs. The second one failed (due to the first one having a lock) which caused an error to be communicated to the client. However the first one was still going and eventually succeeded. Indeed https://commons.wikimedia.org/wiki/File:Cat_Valentine's_TOP_62_Moments_in_Victorious!_-_NickRewind.webm exists