iOS4 on my 3G
This describes my iphone perfectly since the upgrade.... I'm glad I'm not alone...
iOS4 on my 3GInstalling A Subversion Server On Windows
While I would never recommend running a subversion server on anything but a Linux machine, I was recently asked to write a tutorial on doing so on a Windows based machine. Installing a subversion server on windows can be a daunting task. Luckily a project has come forth to make that task significantly easier called Visual SVN.
VisualSVN serves as a front end management console for your windows based subversion server. This will save you from manually editing configuration files, generating ssh keys and many other things.
Drop by their homepage and grab the free version of VisualSVN here:
http://www.visualsvn.com/server/download/
The installer has will ask a handful of questions. The first will ask if you want to install VisualSVN Server and the management console together:

It is recommended that you choose “VisualSVN Server and Management Console” which should already be selected for you.
Next you will be asked for the specifics of how your server is going to run:

1) Location: This is where the server’s program files will reside. Usually the default works just fine.
2) Repositories: This is where your subversion repositories will live. As your repositories will grow over time, it is best to choose a location with plenty of space.
3) Server Port: You can usually leave this to port 443 and keep the secure connection checkbox ticked. Be sure your not running anything on that port such as a website with an SSL certificate. Also be sure your firewall is configured to allow connections on the port you specify here.
4) Subversion Authentication: I typically recommend to use this method as opposed to windows authentication as it allows you a bit more flexibility. However your in house requirements may be a bit different. This tutorial covers using subversion authentication.
At this point the installer has everything it needs to install both subversion and the management console. Upon completetion you will be given the option to start the management console. Leave that checked and press finish.
CONFIGURING THE SERVER:When the management console first opens it will give you information about your newly installed subversion server.

The most important info you will need is the server URL. By default this is going to be your windows machine name. If you have a domain name pointing to the server or a unique IP address we will want to change this. Follow these steps:
1.) Click on “VisualSVN Server” on the left pane.
2.) Select Action from the top menu and click Properties. (ACTION->PROPERTIES)
You should get a dialog that looks similar to this. If it looks different be sure Visual SVN Server is selected as described in step 1.

3.) Click on the Network Tab. Here is where you can specify your fully qualified domain name or unique IP addresses, if you have additional addresses and/or IP addresses you can also bind them here:

The server name field is where you will want to specify your unique IP address, fully qualified domain name or NetBios name that already has a binding to your machine.
4.) If you change your Machine name as described in the last step, you will also need to regenerate your SSL certificate. To do this click on the certificate tab.
5.) Click on Change Certificate
6.) A new dialog will open. Select “Create new self signed certificate” then click NEXT
7.) You will be asked for the Common Name this is your fully qualified domain name or NetBios name.
8.) The following steps will ask you a handful of questions about your organization for the certificate. As this is a self signed certificate you can elect to leave these blank, although I highly recommend filling out the information as you may run into problems with certain subversion clients. Click next until the new certificate is generated.Press APPLY then OK and your subversion server will restart.
CREATING YOUR FIRST REPOSITORY:
You now have a subversion server installed and configured on your windows machine. Next we will want to create our first repository and user that can access that repository.
We’ll start with creating the initial repository. To do this right click on Repositories on the left side pane, select CREATE NEW REPOSITORY.

A dialog will appear asking for the name of the repo (see below). For this tutorial we are just going to use the name ‘test’. We will also check the box to create the default repository structure.

Once you click OK you will see your repository appear in the left side pane. We now have our first (empty) repository on our new server. It’s time to create a user that can access that repository.
CREATING A USER:Your repository is useless until you (or someone) can access it. During the installation earlier in this tutorial we specified that we wanted to use Subversion authentication. This section of the tutorial assumes you are using Subversion authentication.
1.) To create a new subversion user right click USERS in the left pane and click CREATE USER.
2.) You will be prompted for the username and asked to specify and confirm a password.
3.) The new user should appear under users in the management console. Right clicking the user will allow you to delete or change the password if/when needed.
Now that you have created the user, you will want to be sure your new user has access to the test repository we created earlier.
On the left pane you will want to right click on your test repository and click properties.

The Security tab should pop up. Click the ADD button and add the user you just created. You will also want to click on that user and select the permissions the new user should have. In this example I’ve selected READ/WRITE. (see below)

Press APPLY then OK.
You are now ready to use your first subversion repository. The next part of the tutorial explains using TortoiseSVN on the client machine, which is typically the development machine that needs access to the source code on the server you have just setup.
INSTALLING AND USING TORTISESVN
The first thing you will want to do is head over to the Tortisesvn homepage and download the client:
http://tortoisesvn.net/downloads
The installer is pretty straight forward and all of the defaults should be just fine for our purposes.
You will typically be asked to reboot after installation. Go ahead and reboot and then we’ll get started.
ACCESSING OUR TEST REPOSITORY
Once your machine has rebooted it’s time to make use of our test repository. For this example I’m going to download our first repository in an empty folder that I’ve called source.
Open up Windows explorer by going to MY COMPUTER->C:\ create a new folder called SOURCE and navigate into your new folder.
You should now be looking at an empty folder. Right click and select SVN Checkout.

You will want to fill in the details of your new subversion repository. The most important thing here is the URL of your repository. All of your repositories will be accessed with a url that is formulated like this:
https://DOMAIN/IP ADDRESS.COM/svn/test/trunk/
https – be sure you have the s so that you are using a secure connection.
DOMAIN/IP ADDRESS.COM – this is the fully qualified domain name, IP Address or NetBios address you configured during the CONFIGURING THE SERVER section of this tutorial.
/svn/ -- all of your repositories will live under the svn folder.
/test/trunk – test is the name of the repository we created and we want to work with the trunk of the repository.
So all together my checkout url looks like:
https://127.0.0.1/svn/test/trunk/

You may want to adjust the checkout directory to meet your needs, for this example we are downloading the repository directly into the folder named source that we created. If you specify a folder that does not exist, it will be created during the checkout process.
The remainder of the options on this page should typically be fine at their defaults. If you have special needs when working with a project you may need to change some of these.
Once you are satisfied with the selection press OK.
Since we are using a self signed SSL certificate. The first time we access the repository, we will be warned that the issuer of our SSL certificate is unknown. This is fine and won’t cause any problems. By pressing Accept Permanently you will never get this warning again. This message can be eliminated by purchasing an SSL certificate from a trusted source such as GoDaddy.

Once you choose to accept our unsigned certificate you will be prompted for your login credentials. This is where you enter the username/password you created earlier in this tutorial.
If all goes well you should have checked out revision 1 of our empty repository called test.
Adding A File To The Repository And Committing It
For this example we’ll create a simple text file, add some content, commit it, make some changes, commit again and view the differences between versions.
Right click in the Windows Explorer window you have just performed your checkout to and select NEW->TEXT DOCUMENT. For this tutorial we are just going to name it sample.txt.
I’m going to populate our sample.txt file with a bit of PHP code as seen in the below screenshot.

I’ll save the code I’ve put into the file and now I’m ready to commit my changes.
Since the file called sample.txt doesn’t actually exist in the repository yet, we’ll first add it, then commit it.
To add the file, right click on the sample.txt file and select TortoiseSVN->Add…

We are now ready to commit the file to the repository. Right click our file again and you should now see a new option titled SVN Commit.

The commit dialog will appear (see below). Here is where you enter in what you have done so that other developers can see your comments and notes about changes. This is where you will also see what files are to be committed and the statuses of these files.

Enter your comments and press ok. You should get a dialog letting you know that revision 2 was committed to our test repository.
Next, lets make a few changes to the file and repeat the commit process. I wont go through the commit process again. Just follow the steps above each time you wish to commit a change.
At this point I’ve made two sets of changes, and committed my changes for each one. Let’s have a look.
GETTING THE DIFFERENCE BETWEEN REVISIONS:For this tutorial let’s say I wish to find out what has changed in this file. I’m going to right click on the file once again, but this time select TortoiseSVN->Diff with Previous Version.

This may take a few seconds depending on the extent of the changes. Once processing is done, you will get a split screen of the two versions with any changes highlighted. In my case it looks like this:

If you where to click on Show log instead, you would get a list of all revisions, who made the revisions, and the comments the developer entered about that particular revision.

Right clicking on any of these revisions gives you a myriad of options to view the differences with previous revisions, your working copy and more.
I hope this was helpful in getting you started with a full windows based subversion solution.
- Brian
Installing A Subversion Server On WindowsA day in the life of a dog (in 25 seconds)
This is an old post.. but I love the video, so I just had to repost it.. Sasha passed away about a year ago RIP.
--- Snip -- Repost from a long time ago ------
I always wonder how my dog spends her days... I've always assumed that due to her age she just lays on the bed all day...
So... to discover what exactly she does, I setup a webcam, capturing a frame every 8 minutes OR whenever there was motion detected... The video starts around Noon and ends around 10pm.. this is funny.. A whole day in 25 seconds...
Website: http://www.capturemax.com
TNL-FTP A Free FTP Client for Windows

I just uploaded some minor updates to my free FTP client for windows. Back in the 90s I fell in love with WS-FTP, over time their UI changed a lot and I hated it, and didn't see a reason to continue paying for it. So I wrote my own clone that had a UI that was very close to what I preferred working with. Eventually some colleagues convinced me to release it for free... so here it is:
"This new version has many fixes geared towards Windows 7 and Windows Vista users. This FTP Client is included with Perl Scripting Tool as a FREE stand alone application. This feature-rich FTP Client makes FTP a snap. TNL-FTP is a feature-rich drag-and-drop FTP client. With a look and feel that is comfortable and straight forward to use.
What’s New in 1.9?
• Now Supports Resume on Uploads and Downloads
• Send Raw FTP commands directly to the ftp server.
• Open Local Files (instead of just VIEW).
• Optional Gridlines on Directory Listings.
• Several Bugs Corrected.
• Minor Cosmetic Changes.
Features Include:
• Multiple Profiles
• Advanced Connection Settings
• Automatic Transfer Mode Detection (I.e. Binary, ASCII)
• Full SOCKS4 and SOCKS5 Proxy Server Support.
• Full Drag and Drop File Transfers.
• Advanced functions such as CHMOD, Passive Transfers and Resumes.
TNL-FTP’s UI is styled after classic versions of WS-FTP to give you a familiar look and feel.
TNL-FTP is free and can be downloaded here: DOWNLOAD TNL-FTP
TNL-FTP Homeage:: http://tnlftp.tnlsoft.com
TNL-FTP A Free FTP Client for WindowsMy Battle With The Local FOX Affiliate
This is the anniversary of this post.. and it's one of my favorites. I recall a job interview that only consisted of this story... So here it is again direct from 11 years ago... this post-dates the dot-com bust ![]()
This is my story of a small battle with my local FOX affiliate in Dayton, OH. It involves my love of Star Trek, Bad Web Developers, non-responsive corporations, and the news media. This is rather old, but I just came across the Wired News Story about the incident again, and was inspired to tell the story.
What Started It All.
6 Years ago, the show Star Trek Voyager was on the air, however problems between UPN and Fox, forced many Fox affiliates to drop the UPN Show.
Unfortunately in Dayton, OH they did this during after the 1st part of a 2 parter. I was pissed. After waiting and waiting hoping to hear something about the show, I eventually realized it was no longer going to be aired on broadcast TV in my town.
Protest.
I went to the FOX 45 website, and tried to find an email address to lodge my complaint. This site was the WORST front page site I had ever seen. There was no email contact, only a website form which I proceeded to fill out. A few choice words might I add. Then I proceeded to click that SUBMIT button with a vengeful satisfaction.
The next page alerts me that I did not fill out the form completely. They expected me to not only provide my name and email address, but my full address and telephone number. This was a bit disturbing, but I felt that their offense was so severe, I would do anything to get my show back. So I went back and filled everything out.
A few weeks went by and no response. Not even an autoresponder saying that they got my complaint. So I returned to the website and lodged another complaint, filling in all of my information.
Again, a few weeks went by and nothing.
By this time it had been a month without Star Trek and thanks to the net I was well aware that there was a conclusion to the cliffhanger they left me with. So I found myself back on the website. This time determined to find an email address.
The Discovery
I figured that form I had filled out a few times was simply emailed to someone at the station and the 'Mail To' form on the page might have an email address in the HTML code. So, I went back to the page and did a view source. There was no email address to be found but there was a reference to a file. it was something like /_vti_xxx/comments.txt So I simply appended that path to the url... (i.e. www.fox45.com/_vti_xxx/comments.txt) and waited and waited and waited for my dialup connection to load this amazingly large page.
I was dumbfounded. What was there was every single comment submitted to the site, complete with names, addresses, phone numbers and email addresses. The FIRST thing I noticed was that I was not alone in my anger about the Star Trek show. I was only one of hundreds complaining. But I had come to the realization that all of these peoples personal information was there for the taking by anyone with a web browser, including my own personal information (in there twice!).
I was amazed at the sheer lack of competence for a professional organization in their web security. Even in 1999. While that may be expected from a fan site or a hobby site, you would not expect that from a business (at the same time you wouldn't expect a reputable company to use Frontpage 97).
Trying To Get FOX 45 to Listen
I printed all 500+ pages of this publicly accessable page to my fax program and let my computer send this fax to the station with a cover letter explaining my concern and detailing the problem.
A few weeks pass and no response. The file remained.
So.. again..I resend the fax... I'm sure they really loved the fact I was faxing them more than a ream of paper. TWICE. Someone HAD to notice that.
About 3 days later the contact page disappeared and offered a generic email address to send comments to. However the file containing everyone's information was still up there. So this time, I altered my cover letter, letting them know that removing the contact page doesnt remove the data that was submitted though the (now) missing page. Another 500+ page fax plus emails to the generic contact addresses listed on the site... (still trying to get their attention).
Drastic Action
A few more weeks passed and nothing. A friend of mine where talking about this and how totally wrong the situation was and decided that we would send the link/url to everyone's email address who had their information compromised.
I dont' have a copy of the email we sent anymore, but we explained the situation, provided the url so they could see for themselves, and encouraged everyone to call the station and demand that their information be secured.
We wrote a simple perl script (less than 8 lines of code) to extract all of the email addresses from the file and put them nicely by themselves in a 1 address per line output file. We proceeded to send the emails to everyone who's information was in there. We also added email addresses of competing television stations in the area, as well as various other media outlets. The emails where sent them under an anonymous name, Black Flag, with a real return email address so that we could get responses.
This was about 1am... The emails went out, we went to bed and then to work in the morning and after work all hell broke loose. Several news agencencies had emailed wanting an interview. Wired being the most notable, wanted an interview, but we didnt respond in time and they ran the story anyway. The file on the net was gone. There was an outpouring of support from people who appreciated what we had done, A few emails to our web-host claiming we where spamming them and The FOX Affiliate cried foul and said that we 'hacked' them and claimed that we even changed his password so they could not access the site. All this from a simple VIEW SOURCE command available on all web browsers.
Quote:
"We feel like we got hit in the back of the head," said Hanson, who claimed that Black Flag had changed his password so that he could not access his site. "They come along and they mess with this info, and then they send a mass mailing, so here we are in this whirlwind."
Quote:
A search of the file by Wired News uncovered 657 individual email addresses. The page was removed from the site at about 9:25 a.m. PST.
Anyway... it took a lot to get them to take the file down, but after some extreme measures they finally did.
I called and claimed responsibility and asked them if they would hire me. They seemed a bit busy, and declined my job offer.
Why am I writing about something from 6 years ago.. ehh.. I just came across the Wired news story and found it amusing... a bit distorted, but amusing... You can read it here:
http://wired-vig.wired.com/news/technology/0,1282,17437,00.html




