I'm not sure if it's related to this... but I can't seem to get the achievement for having worked on a video for a length of time, regardless of if I'm on Linux or Windows.

john@joran Team Fortress 2 > ll
total 4640
drwxrwxr-x  3 john    4096 2013-01-18 10:05 bin
drwx------  3 john    4096 2012-11-13 15:06 config
drwxrwxr-x  4 john    4096 2012-11-13 15:07 hl2
-rwxrwxr--  1 john    6891 2013-01-21 23:21 hl2_linux
-rwxrwxr--  1 john    2171 2013-01-21 23:21 hl2.sh
-rw-rw-r--  1 john      17 2013-01-21 23:21 libcurl.so
drwxr--r--  3 john    4096 2012-11-13 15:07 platform
-rw-rw-r--  1 john 4712557 2013-01-11 19:54 strace-loop
drwxrwxr-x 16 john    4096 2013-01-11 19:55 tf
john@joran Team Fortress 2 > cat libcurl.so 
libcurl.so.4.2.0

wut?

So the libcurl.so included with TF2 is a plain text file with just "libcurl.so.4.2.0" in it? I assume that's not usual for .so files?

It's more weird than that, since TF2 main doesn't actually use libcurl.so, the libcurl in TF2 is statically linked (though a library it uses may need it, still investigating that). I've fixed the problem with the non SSL libcurl but I'm still trying to figure out why we have a libcurl.so on the root.

We should have a fix for this out in the next week or so. Until then if you want to upload to YouTube you can export your rendered movie and then upload it to YouTube directly. Which to be honest actually works better given the security issues with YouTube and Google.

Security issues? What issues? And don't I need to upload it via TF2 in order to get the achievements?

Google now wants you to create a new authorization for apps that upload to YouTube (so you can revoke the authorization). You have to do this on your Google account (I couldn't see a way to do it on YouTube itself). It creates a special password for the application, that you can revoke/isn't your real password. But it means you end up with a giant password that is only good for TF2, which TF2 won't remember and you can't paste (another bug I'm sure, but one that might not be fixed).

It works (the upload to YouTube) once my changes to TF's use of libcurl are released, but it just seems kind of bad (on Windows as well). And yes I do think you have to do it if you want the achievement. I don't believe you can turn off two-factor authentication on YouTube anymore. Which is the security issue I mention.

I'd say that's more of a security "feature"* than a security issue.

• see http://catb.org/jargon/html/F/feature.html
  Edit: Added quotes and asterisk

@matthewsor is it worth filing a feature request for that? :) having an in-game oauth2 process for youtube would mean the user logs in to google with normal user/pass (and 2factor code from their phone), then TF2 gets a token to look after, no passwords to worry about.

While I do think someone here needs to revisit how TF2 works with YouTube, it isn't the Linux cabal's focus. Right now we are really only shooting for parity with the Windows version, full on features are a bit outside of our box.

Ok the fixes for this are all in. I believe we will also be removing the wacky libcurl.so text file (though I have no control over the actual Steam image, so it might be awhile before it really is removed). I even fixed the paste bug on the password dialog, to make it just a bit easier to get your giant application password for YouTube into TF. Should go out in the next week or so.

I believe that this issue may have popped up again, I'm getting the same error as the original "Error: Protocol https not supported or disabled in libcurl" when trying to upload to YouTube through TF2 under Linux.

I'm also having the issue on Ubuntu 13.10 , even though I generated an application-specific password.

Yep, still getting the error "* Protocol https not supported or disabled in libcurl".

I wouldn't mind just uploading exported movies, particularly since I don't make lots of replays, but apparently you can't get the Youtube-related in-game achievements that way.

(Since the game already has a Register button that opens an in-game browser, would it be feasible to add oauth?)

@cburschka BTW, this linked issue has the solution.