The app aggregates video from hundreds of different sources across the internet and categorizes them into different channels – comedy, news, music, technology and more. You can subscribe to any or all of these channels and they will be presented to you in a beautiful user interface. Everything is updated in real time and you’ll always see new videos popping in. Get it for FREE on the App Store!

You can download the Nomad Editions app for free from the App Store (currently iPad only) and subscribe to any or all of the magazines you want via In-App Purchase. Check it out.

…and here is our custom skinned version.

To achieve this you will need 2 images: one for the background, and one for the fill. The images that I’ve shown here were designed by Darran Morris so please give credit if you use them.

Update: You can download the images I’ve used here: progress-bar-bg.png, progress-bar-fill.png

Once you have your images created like mine above, create a new Objective-C class. In your header file make it a subclass of UIProgressView.

Next in your implementation file we will create and use our images to draw the progress bar. Note that the images have to be “stretchable” in order to work correctly and to be able to render at different widths and heights.

That’s it! Now you can use this progress view like you would any other UIView by calling initWithFrame: and passing a CGRect – and since the images are stretchable you can make it any size you want.

• 1. Every request that goes through a Wireless (WiFi) Router is a broadcast (think Hubs).
• 2. Browsers will send the same cookies to http://example.com as https://example.com, unless the cookie is marked as secure only.

That means if you are checking your Facebook, or searching Google on a public WiFi network (Starbucks for example), any kid running Firesheep could gain access to your accounts with the click of a mouse. Even if the login page is on https, it doesn’t matter. The second you send a request to http://facebook.com or http://google.com your session cookies are blasted to the entire network, and are fair game.

So now that you know a little more about Firesheep and the risks of surfing on public WiFi, what can you do about it? Use an SSH tunnel. If you have access to an SSH server, which pretty much all web hosting companies give you, then you can set it up as a proxy and securely tunnel all of your web traffic through it. There are several ways to do this, and several different browser plugins to help. I’m going to show you one method using a Mac or Linux computer with Google Chrome and the Switchy! plugin.

The first step is to set up the “tunnel”. This is going to involve a proxy running on your local machine that forwards requests through your SSH server, and since SSH is a secure protocol all of that data will be encrypted. To do this, we need to open a Terminal and issue the following command.

If you don’t have public-key authentication setup then you will be prompted for your SSH password. Afterwards, there will be a SOCKS proxy available at localhost:9000. Now all you need to do is tell your browser to use it. Luckily there is a great little plugin for Chrome called Proxy Switchy which you can download from here. Once installed we need to set it up. Click on the Switchy icon in your toolbar and choose “Options”. We’re going to create a new profile; call it “SSH Tunnel” and select “Manual Configuration”. Where it says SOCKS Host, enter 127.0.0.1. Set the port to 9000 and below that select SOCKS v5. When your done, click “Save”.

Now when you click on the Switchy icon you should see 2 options. Direct Connection (no proxy), and the one we just created SSH Tunnel.

That’s it! Now whenever you’re on public WiFi just open a SSH Tunnel, select that profile from the Switchy menu and all your web browsing will be encrypted – and when you’re on a wired or trusted network you can easily switch back.

You’ll also notice that I’ve added some snazzy new icons and cleaned up the UI a bit. Keep the feedback coming, and enjoy the update!

If you have a previous version of OneWay installed, you can get this update by clicking Check for Updates under the “OneWay” menu. If you haven’t download the application yet, you can do so on the project page.

That being said, the most popular feature request I received was the ability to, after uploading a file, copy its URL to the clipboard. I absolutely agree this would be a great feature, so over the weekend I decided to give it a whirl and I’m releasing it to you today in version 0.5.2.

How it works

In order to use this feature you’ll have to enable it for each of your bookmarks. Create a new bookmark, or edit an existing one by double-clicking it in your list. Click on the “More” arrow below the bookmarks directory and check the box labeled “Enable URL copying for files uploaded to this directory”.

Now enter the URL for the bookmark in the text box and you’re done. Now whenever you upload files to that bookmark you can quickly grab the URL by right-clicking on the upload and selecting the Copy URL to Clipboard.

How to get the Update

If you have already installed OneWay, simply launch the application and under the OneWay Menu choose “Check for Updates” and you should be prompted to install it. If you have not yet installed OneWay you can download the 0.5.2 release on the project page.

OneWay is open source and is licensed under the GNU GPL. If you have a feature request, or you find any bugs, please enter them into my bug tracker.

Enjoy the app!

Next we need to install libssh2. You can do this a couple different ways. The easiest is by grabbing the latest source from here and building it yourself. You could also use a package manager like Fink, or MacPorts. Once installed, we need to locate the dynamic library file called libssh2.1.dylib. I installed from source, so my .dylib file is located in ‘/usr/local/lib’. If you installed with MacPorts it would be in ‘/opt/local/lib’, and Fink installs it somewhere under the ‘/sw’ directory. Once you find yours we need to drag it into our project and drop it in the “Linked Frameworks” directory.

Xcode will prompt you to add the file to your project. Be sure to check the box at that top that says to “Copy items into destination group’s folder” and click “Add”.

Next we have to create a new build phase to copy the library file into our application bundle. In Xcode, in the left column under Targets, control-click on the MySSH target and choose ‘Add’ → ‘New Build Phase’ → ‘New Copy Files Build Phase’. In the popup window select ‘Frameworks’ as the destination and then close it.

Now let’s rename our new build phase from ‘Copy Files’ to ‘Copy Frameworks’ so it’s more clear. Next, while holding down the option key, click and drag the libssh2.1.dylib file from the ‘Linked Frameworks’ group into our new build phase.

What this does now is every time we build the MySSH target it will copy the libssh2.1.dylib from our project into the ‘Frameworks’ directory inside our MySSH.app bundle.

For the next step we need to open up our Terminal, `cd` into our projects directory where the libssh2.1.dylib file is and run the following command:

Linux users will probably recognize this as the `ldd` command. It will display the install name of libssh2 on the top line, followed by the locations of any other libraries it depends on.

The install name for my libssh2 is ‘/usr/local/lib/libssh2.1.dylib’ though yours may differ depending on how you installed it. No matter, since we can’t rely on a user having libssh2 installed in any particular place (or at all) we need to change that path to point to our own libssh2.1.dylib that is in the MySSH.app bundle. For this we use the install_name_tool. Go back to your terminal and from the same directory run the following:

This changes the install_name of our library to a relative path. The ‘@executable_path’ variable represents the path to our application’s binary, and one directory up, in ‘Frameworks’, is where our new build phase copies our library file. If you did this correctly, when you run `otool -L libssh2.1.dylib` again you should see our new relative path on the top line.

Now as I mentioned earlier, the other paths below the install name are all the libraries that libssh2 requires. When bundling your application with a library you must guarantee that all its dependencies exist on the users machine at the path listed. For simplicity I’ve chosen a libssh2 because the libraries that it depends on (libssl, libcrypto, etc.) are all standard on Mac OS X, and are all located in ‘/usr/lib’.

* Note: If you installed libssh2 with MacPorts, pay close attention to the paths listed here. Sometimes when using Macports it will not link against the standard libraries in ‘/usr/lib’ but instead the ones in ‘/opt/local/lib’. If your libssh2 is referencing any libraries in ‘/opt/local/lib’ you will need to change each one using the following command:

Once your terminal output looks like mine above, we can now start using libssh2 in our application. Let’s go back to Xcode, open our TestController.m and enter the following.

Build and run your application, and you should see the libssh2 version number logged to your console. Now it may seem like we are done at this point but there is still one more step. Remember how our libssh2 was referencing other libraries on our system? Well our MySSH application is no different. Let’s go back to our Terminal and take a look. From our projects directory enter the following:

Can you spot the problem?

The compiled binary is referencing libssh2 from our install path. To fix this we need to add another build phase to run after we compile. Back in Xcode, in the left column under Targets, control-click on the MySSH target and choose ‘Add’ → ‘New Build Phase’ → ‘New Run Script Build Phase’. In the popup window add the following code:

…keeping in mind that your ABS_PATH might be different than mine – it is going to be the path that you have listed for libssh2 in the Terminal output above.

Now everytime we build our application, this build phase will change the path your executable looks for libssh2, to the one inside the MySSH.app bundle. That’s it! Now you can give your application to anyone without them needing to install this library. The application will run completely self contained – and if the user should decide to remove your application they can simply delete the .app file and the library will be removed along with it.

dominos.py (right-click and save)

Instructions:

First download dominos.py. You can right-click the link and select save, or use wget:

That’s it. Now all you have to do is order a pizza, and then execute this script from the command line like this:

Be sure to keep running the script periodically for the real time status of:

• When the pizza is being made.
• When the pizza is in the oven.
• When the pizza is cooked and waiting.
• When the pizza is on its way.
• When the pizza was delivered.