Ruari's thoughts

Before you can upload files you need an auto-login cookie. You could extract the cookie information from your Opera cookie store, but it is just as easy to get cURL to generate a new login cookie. Just change 'username' and 'password' to your own My Opera username and password in the following command and then run it:

$ curl -L -c ~/.myoperacookie -d "location=&user=username&passwd=password&remember=1" http://my.opera.com/community/login/index.pl > /dev/null

Next save the following as shell script. Before saving this you'll need to edit the 'username' parts to make it your own My Opera username:

#!/bin/bash
curl -b ~/.myoperacookie http://my.opera.com/username/files/addpic.pl -F file=@"$1" -F dir="$2" -o /dev/null
file=`echo $1 | sed -e "s/.*\///" | sed -e "s/ /%20/g"`
curl -s -I "http://files.myopera.com/username/$2/$file" -e http://my.opera.com/ | grep HTTP | sed -e "s/HTTP\/1.1 200 OK/Upload Successful/" | sed -e "s/HTTP.*/Upload Failed/"

Note: Make sure you make the script executable and save it somewhere in your execute path.

To use the script simply type the script's name (I called my script 'moput', meaning 'My Opera Put'), followed by the name and path to file you want to upload, and the name of the My Opera directory you want to upload to. For example, to upload a local file called 'funny.jpg' from your local '~/Pictures' directory to your My Opera Pictures directory, you could issue the following:

$ moput ~/Pictures/funny.jpg Pictures

Note: If the My Opera directory doesn't exist it will be created. If you want it to be a subdirectory this is possible to, e.g. 'files/Pictures'. If you only mention the local file and don't mention a My Opera directory, it will placed in 'files' but you will be told that the 'Upload Failed'.

Now the obvious questions are, "How is this more efficient than the regular uploader? What if I have lots of files to upload, do I have to upload them one at a time?"

Firstly, for me at least it is more efficient as I prefer work on the command line. It also allows me to upload files from remote machines that I connect to via ssh (hence no GUI). However, I appreciate that many people won't see these as benefits. In answer to the main question, yes you can queue up lots of files to upload, and no it doesn't even require having to make a more complex script. Instead you can just make use of the other tools on your system. Suppose for example I wanted to upload all the .jpg files in the current working directory to My Opera and save them in the remote Pictures/jpegs folder. For this you could use the UNIX 'find' command as follows:

$ find *.jpg -exec moput {} Pictures/jpegs \;

Here is another variant, which would copy all PDF files in the current working directory and one sub directory deep, and save them in in the remote 'Documents' folder:

$ find . -maxdepth 2 -type f -name "*.pdf" -exec moput {} Documents \;

Note: If you are not familiar with the 'find' command, read the 'man' page or consult one of the many online tutorials before generating more variant commands. 'find' is incredibly powerful, meaning plenty of things are possible, including stuff that you might not intend!

As many Mac users tend to shy away from the command line, here is a nice Graphical option, using an Automator workflow.

Before we can create the Automator workflow, we need a My Opera login cookie. This is exactly the same as my early instructions but I will repeat it here for convenience.

To make a login cookie, start the Terminal application and type the following, remembering to change the 'username' and 'pasword' to reflect your own My Opera login credentials:

curl -L -c ~/.myoperacookie -d "location=&user=username&passwd=password&remember=1" http://my.opera.com/community/login/index.pl > /dev/null

Now we need to create an Automator workflow as follows:

1. Start Automator
   
2. In "Select a starting point to open a new workflow", highlight "Files & Folders"
   
3. Select "Get content from": "my Mac" & "Use files & folder selected in the Finder when workflow runs"
   
4. Under "Actions > Utlilities" drag "Run Shell Script" to the workflow on the right, below the initial entry.
   
5. Change the "Pass input" option to "as arguments"
   
6. Replace the example code provided by Automator with the following, remembering to change the two 'username' references to reflect your own My Opera username:
   
   
   

   for item in "${@}"
   do
   curl -b ~/.myoperacookie http://my.opera.com/username/files/addpic.pl -F file=@"${item}" -F dir=files -o /dev/null
   file=`echo ${item} | sed -e "s/.*\///" | sed -e "s/ /%20/g"`
   curl -s -I "http://files.myopera.com/username/files/$file" -e http://my.opera.com/ | grep HTTP | sed -e "s/HTTP\/1.1 200 OK/0/" | sed -e "s/HTTP.*/1/"
   done | sort -r | head -1 | sed -e "s/0/File(s) uploaded successfully./" | sed -e "s/1/Check My Opera files: Items may be missing./"
   

   
   
7. Under "Actions > Utlilities" drag "Run AppleScript" to the workflow on the right, below the previous entry.
   
8. Replace the example code provided by Automator with the following:
   
   

   on run {input}
   
   tell application "Finder"
   display dialog input buttons {"OK"}
   end tell
   
   return input
   end run
   

   
   
9. Select "File > Save as Plug-in" and name it appropriately (e.g. 'Send Files to My Opera'), as a Plug-in for "Finder".
   
10. Quit Automator
    

To use: Simply highlight the files you wish to upload in a Finder window, right click with your mouse (or Ctrl+click) and choose "More > Automator > Send Files to My Opera". Automator will then start in the background (you can see the status at the top of the screen). When it is done you will get a message telling you if the files uploaded or not. Done!

Of course if all this seems like too much work, you could just use Unite to share files instead!