Also, moved into SVN repository, guest access is below.

https://guest:guests@svn.labyrinthdata.net.au/jetiblogin/trunk/jetib.sh

Some of the organisations that may use the JetIB system are:

• Curtin University (Bentley Campus)
• James Cook University
• UNSW (University of New South Wales) – ADFA (Australian Defence Force Academy) (Canberra)

You will need to modify the script for each location.

It should run on just about any Linux/Unix/BSD system that has a POSIX shell, and curl installed. It should run on a OS X Mac as well.
If you have zenity installed, it'll use that to ask for your credentials, otherwise it'll just ask for them in the terminal. If your credentials are stored in a .jetibcreds file in your home directory it will use them instead. (Format of username:password)

Once connected, it'll loop around updating your shell display with the terminal of your session (this should also perform as a keep alive for your session), pressing ctrl-c will exit that loop and log you out, and clean up the session cookie.

Edit: New version available at http://weirdo.bur.st/2009/09/09/jetib-login-tool-v0-2/

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124

#!/bin/sh
#
# Jetib Login Tool (v0.1)
# 
# Author: Timothy White http://weirdo.bur.st/
# 
# This script will log you in to a jetib (Jet Internet Billing) system
#
#
# It will first attempt to load your credentials from .jetibcreds
# If this file doesn't exist, it will fall back to asking for your
# credentials first via zenity, and if zenity isn't installed then via
# normal shell input
#
# curl must be installed and in your path for this tool to work
 
# Curtin University settings are as follows
#DOMAIN="jetib.curtin.edu.au"
#LOGIN_PAGE="/curtin/portal/login"
#STATUS_PAGE="/curtin/portal/popup_text_refresh"
#OGOFF_PAGE="/curtin/portal/logout"
 
DOMAIN="jetib.curtin.edu.au"
LOGIN_PAGE="/curtin/portal/login"
STATUS_PAGE="/curtin/portal/popup_text_refresh"
LOGOFF_PAGE="/curtin/portal/logout"
 
# .jetibcreds file in users home directory
# containing login credentials in the format of
# username:password
JETLOGIN="$HOME/.jetibcreds"
 
# User agent to pretend to be (just incase they block scripts, pretend to be a browser)
USER_AGENT="Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)"
 
# Find location of curl and zenity
CURL=$(which curl)
ZENITY=$(which zenity)
 
 
# Catch ctrl_c requests and logout and cleanup
ctrl_c() {
    stty echo # Turn TTY echo back ON!
    # (Maybe we caught Ctrl-c when they were supposed to be entering password)
    echo ""
    echo "Logging you off..."
    # Send logoff request
    curl -s https://$DOMAIN$LOGOFF_PAGE -c cookies.txt -b cookies.txt |grep "<p>"
 
    # Clear cookies file
    rm cookies.txt
    exit 0
}
 
status_page() {
    # Get status page text
    status_text=$(curl -s https://$DOMAIN$STATUS_PAGE -c cookies.txt -b cookies.txt)
 
    # Process status page text
    remaining=$(echo "$status_text" | grep remaining)
    loggedinas=$(echo "$status_text" | grep "logged in as"|egrep -o '<em>.*</em>'|grep -o '[0-9]*')
    quota=$(echo "$status_text" | grep -i quota|egrep -o ':[^<]*' )
    thismonth=$(echo "$status_text" | grep -i "this month"|grep -o '[^<]*'|grep 'this')
    thissession=$(echo "$status_text" | grep -i "this session"|grep -o '[^<]*'|grep 'this')
 
    # Display status page
    clear
    echo "$remaining"
    echo "Logged in as: $loggedinas"
    echo "Monthly Quota$quota"
    echo "$thismonth"
    echo "$thissession"
    echo ""
    echo "Press Ctrl-C to disconnect"
 
}
 
 
if [ -x "$CURL" ]
then
    if [ -r "$JETLOGIN" ]
    then
        # .jetibcreds file in users home directory
        # containing login credentials in the format of
        # username:password
        creds=$(cat $JETLOGIN)
        USERNAME=${creds%%:*}
        PASSWORD=${creds#*:}
 
    else
        # Credentials not saved, ask for them
        if [ -x "$ZENITY" ]
        then
            # Use Zenity to ask for credentials
            USERNAME=$(zenity --entry --title="Internet Login" --text="Username")
            PASSWORD=$(zenity --entry --title="Internet Login" --text="Password" --hide-text)
        else
            # Zenity not installed, falling back to shell to ask for credentials
            echo -n "Username: "
            read USERNAME
            echo ""
            echo -n "Password: "
            # trap ctrl-c and call ctrl_c()
            trap ctrl_c INT 
            stty -echo # Turn off TTY echo so password is hidden
            read PASSWORD
            stty echo # Turn TTY echo back ON!
            echo "" # force a carriage return to be output
        fi
    fi
 
    # Submit login request to server (No error checking yet)
    curl -s -A "$USER_AGENT" -F "targeturl=''" -F "submit=Logon" -F "username=$USERNAME" -F "password=$PASSWORD" -c cookies.txt https://$DOMAIN$LOGIN_PAGE > /dev/null
 
    # trap ctrl-c and call ctrl_c()
    trap ctrl_c INT 
    while true
    do # Loop updating status page every minute until Ctrl-C is pressed
    status_page ; sleep 1m
    done
 
else
    echo "This Jetib login tool requires curl to be installed and in the PATH";
fi

The Homecast HT8000 and HT8200 are essentially identical devices, with the difference of a "Freeview" (or a, we'll restrict your view) sticker and some slightly different hardware. Thankfully, you can convert the HT8200 back into a HT8000 with a firmware "update". The rest of what appears below isn't my work, and is easily found at http://members.optusnet.com.au/nis200sx/ and remains the work of that person. I am placing a copy of it here, not to try and take credit from him, but rather to preserve the information (and methods) in the event that it is removed for some reason. I may also attempt to expand on his Method 2 and 3 at a later stage.

Oh, and before you try, the .TP0 files you have recorded on the HT8200 are useless unless you watch them on the HT8200 (with the freeview sucky firmware).

Loading HT8000 Firmware onto a HT8200

---

Question:

• Why would anyone want to load HT8000 firmware (software) onto their HT8200 PVR?

Answer:

• The benefits are easier file navigation (30sec and percentage jump buttons work)

• Plus the recordings are not encrypted (and the USB type B port works for transferring to/from a Windows PC) so they can be played on a PC and converted to DVDs etc.

Question:

• What am I losing by doing this?

Answer:

• The downside is that any recordings already done with HT8200 firmware will no longer be playable.

Question:

• How do I do it?

Answer:

• There are 3 ways to get a HT8200 to accept HT8000 firmware. Below I will outline the 3 methods, from easiest to hardest. Note: The hardest method is the best method (I'll explain why below).

Method 1 – Easiest

Download a copy of the HT8000 firmware that has already had the Model ID number changed to match the HT8200.

The benefit of this method is that it is extremely easy and you do not need any special skills or understanding of what's being done. The downside is that you are reliant on me, or someone else, providing you access to a suitable firmware file any time Homecast release a newer version (assuming you want to keep the firmware up to date).

This firmware file will load on a HT8200 and turn it into a HT8000: Download 8200-to-8000-1048.zip (Mirror Download 8200-to-8000-1048.zip) Well, it will still say that it is a HT8200, with SW version 1.00.9A, but it will actually be running HT8000 SW version 1.04.8A.

After updating to this file you can still update to a normal HT8200 firmware file in future (the PVR still thinks it's a HT8200). If you want to update to a newer HT8000 version (when the next one is released) you will need download the latest 8200-to-8000 zip file from this web-site. Each time a new HT8000 version is released I will try to put a new 8200-to-8000 file online.

Method 2 – Medium (not finished)

Download a copy of the HT8000 firmware and use a hex editor to change the Model ID number yourself.

The benefit of this method is that you are not reliant on anyone else doing the editing for you, so it is easier to keep the firmware up to date.

I will update this page soon to explain how…

Method 3 – Harder (not finished)

Download a copy of softwareclean.bin and upload it to your HT8200 using Homecast's Upgrade application and a null-modem serial cable.

The benefit of this method is that it only needs be done once. After loading softwareclean.bin your HT8200 won't know what it is until you then load some firmware onto it. At this point you can load ANY firmware onto – Be CAREFUL!!! After loading a regular, unedited, HT8000 firmware onto your HT8200 from then on it will think that it is a HT8000, so when HT8000 updates are released in future you can just update using the regular HT8000 firmware from the Homecast website.

I will update this page soon to explain how…

(Mirror Download SoftwareClean.bin)

http://www.computerforum.com/150870-asus-mobo-p5kpl-am-ps-issue-problem.html

I rechecked the power, reset, and led connectors against the screen print on the mainboard and all looked correct, but then I noticed it also says USB56 next to that set of connectors.

The printing on the mainboard is very misleading, the connection diagram for hdd, power and reset is right next to a similarly pinned USB connector. Make sure you are using the connectors labelled F_PANEL not the USB56 connector.

I went back to the motherboard, and webber75 was correct! The labelling for the Front panel connectors, is UNDER the USB connection! Quickly fixed, and we had power again!! Unfortunately, the motherboard is still playing up, so it's still not 100%, but for anyone else having problems getting an ASUS P5KPL motherboard to boot or power on, check which connections  you have plugged the front panel wires into!

Grase

Introducing Grase!

It's pronounced the same as Grace, so please don't pronounce it like grass!

So what is Grase? Grase is a complete Hotspot/Internet Gateway Solution. It incorporates a server hosting a captive portal (which "captures" a users attempts to access the internet before being authenticated and redirects them to the authentication page), traffic/data accounting software, user management interface, a caching and filtering proxy.

Or simply, a combination of LAMP (Linux, Apache, MySQL, PHP), Squid, Dansguardian, CoovaChilli, FreeRadius, Monit, OpenVPN, and a custom interface to managing users and the system.

The project relies heavily on other projects, the main features are the integration of the other projects and the custom interface to it all. The administration interface was the first part of the project, and consists of user management, session monitoring, and system settings. More details of the interface to come later, along with a project page with information.

So part of the solution was going to be to make the downloads happen quicker. It was already going through a Squid proxy, which should have made this happen, but it still meant the downloads would be slow the first time, so one user would be charged for the downloads, and not subsequent users. And due to the fact that it load balances the servers, the chances of all users hitting the same avast download server is next to nothing. My searches on the net lead me to http://files.avast.com/files/eng/mirror.zip which is an application from the Avast Distributed Network Manager that sets up a central server for managing avast in a corporate setting. After playing around with the mirror.exe file that generates a mirror, and discovering that adding "restrict_products=av_pro" to the mirror.ini file, I could limit the mirror generation to just the normal avast files for program and virus definition updates.

So now I had an Avast mirror, I now needed to do 2 things, find a way to generate an avast mirror, and update it without using the windows only, mirror.exe program, and find a way to make Avast clients update from the mirror, and not the internet.

The first problem was solved with a bit of poking around in the files downloaded by mirror.exe, and discovering that it checks a couple of "stamp" files on the server, if the stamp files are new, it downloads the file it is a stamp for, in particular, mirror.def, which contains a complete list of all the files needed for a mirror, with the MD5 sum of the file, and filesize, as well as the "products" that utilise the file. This file makes it easy to generate a mirror!! Below is the script that generates a mirror. There are a few things it doesn't do that mirror.exe does. It doesn't generate the 400.vps files, which Linux clients use to update from (all other clients should use the partial update files to save downloading 20Mb+ every time). It also doesn't generate a new mirror.def file that only contains the files that this partial contains, instead it uses the same mirror.def file that it used to generate the mirror from the master servers. It also doesn't modify the servers.def file. The main reason for this is that these files are signed, and we don't yet know how to sign them ourselves, so the clients would reject any modifications. Also, unless someone who will be behind the proxy, and thus using your mirror, attempts to create their own more complete mirror, mirror.def being wrong doesn't matter. Also, changing the servers.def file to point to your mirror as mirror.exe does, would prevent users from later updating Avast on another network that doesn't contain your mirror.

The next part of the solution is how to redirect requests for Avast updates to your mirror, without Avast knowing it isn't getting it's updates from the real servers, so that no modifications to Avast are needed.
So this part actually worked out a lot easier than initially thought. All users currently go through a Squid proxy, transparently, due to filtering and the obvious benefit of caching on a limited internet connection. I thought that with Avast attempting it's updates from a variety of servers throughout the world, and with both IP and domain name attempts (it alternates between the 2 so that DNS outages, or DNS hijacks, can't prevent it from updating), it would be difficult to write a generic filter to redirect them. Then I realised that every request from avast, was to a directory, iavs4x. Suddenly I didn't need to worry about which server it was attempting to connect to, just the directory. So I wrote a Squid Redirector that rewrites any request that is to the directory, iavs4x, to go to the server that hosts the mirror. You can setup ACL's so that not every URL goes through the redirector, but as I already use a redirector for adzapping, I didn't pursue this option. The script is below, change the server variable to reflect your mirror server.

avast_mirror.sh

#!/bin/bash
 
#### Avast Mirror
#
# Files that should be in mirror but won't be
# 400.vps 400.vps.md5
#
# Extra files we need that aren't in mirror.def
# jollyroger.vpu.stamp jollyroger.vpu servers.def servers.def.stamp servers.def.vpu.stamp servers.def.lkg  servers.def.vpu
 
# BASEURL (Select a random from mirrors file? with fallback, currently just default)
BASEURL="http://files.avast.com/iavs4x/"
mirror_def=mirror.def
BASEDIR=/home/mirror
TMP_URL_LIST=/tmp/mirror_files
 
# Filter for mirror.def
restrict_products='av_pro'
 
# Set DEBUG to anything other than '' to get debugging info
DEBUG=''
 
 
cd $BASEDIR
 
# Files updated from stamp files
function stamp_update {
	file=$1
	stampfile=$1.stamp
	old_stamp=$(cat $stampfile)
	file_stamp=$file_stamp.new
	wget -q -O $file_stamp $BASEURL$stampfile
	new_stamp=$(cat $file_stamp)
	if test "x$old_stamp" != "x$new_stamp" ; then
		echo "$file out of date."
		echo "Updating..."
		mv $file_stamp $stampfile
		mv -f $file $file.old
		wget -nv $BASEURL$file
		echo "$file updated"
	else
		if test -n "$DEBUG" ; then echo "$file up to date.";fi
	fi
}
 
stamp_update mirror.def
stamp_update jollyroger.vpu
stamp_update servers.def
stamp_update servers.def.vpu
 
# Read in mirror.def, check all files and add out of date ones to queue
	rm -f $TMP_URL_LIST
	# Add "extra" files that are always downloaded here
	#echo  $BASEURL"servers.def.lkg" > $TMP_URL_LIST
	filelist=$(cat $mirror_def |grep $restrict_products|cut -f 2 -d =|cut -f 1-3 -d ,)
	for file in $filelist
	do
		info=( `echo "$file" | tr -s ',' ' '` )
		filename=${info[0]}
		filesize=${info[1]}
		filemd5=${info[2]}
		if test ! -f $filename
			then
			if test -n "$DEBUG" ; then echo;fi
			echo "Adding new $filename to download queue"
			echo $BASEURL$filename >> $TMP_URL_LIST
			continue
		fi
		curfilesize=$(stat -c%s "$filename")
		if test "0$curfilesize" -lt "0$filesize" 
			then
			if test -n "$DEBUG" ; then echo;fi
			echo "Adding incomplete $filename to download queue"
			echo $BASEURL$filename >> $TMP_URL_LIST
			continue
		fi
 
		curfilemd5=$(md5sum "$filename" | cut -f 1 -d ' '|tr [:lower:] [:upper:])
		if test "x$filemd5" != "x$curfilemd5"
			then
			mv -f $filename $filename.old
			if test -n "$DEBUG" ; then echo;fi
			echo "Adding corrupt $filename to download queue"
			echo $BASEURL$filename >> $TMP_URL_LIST
			continue
		fi
		if test -n "$DEBUG" ; then echo -n ".";fi
		#echo "$filename already downloaded and complete"		
	done
	if test -n "$DEBUG" ; then echo;fi
	if test -s $TMP_URL_LIST
		then		
		echo "Downloading out of date mirror files"
		#Download files
		# --no-dns-cache means it'll load balance randomly accross different servers for each file
		wget -c -nv -N --no-dns-cache -i /tmp/mirror_files --progress=dot |tee -a mirror.log
	fi

avast_redirect.pl

#!/usr/bin/perl
$|=1;
$server='10.1.0.1';
while (<>) {
    @X = split;
    $url = $X[0];
    if ($url =~ /^http:\/\/[^\/]*\/iavs4x\// && $url !~ m/$server/o) {
        $url =~ s/^http:\/\/[^\/]*\/iavs4x\//http:\/\/$server\/iavs4x\//o;
        print "$url\n";
    } else {
        print "\n";
    }
}

p.s. Sara and i have registered our domain and will soon be launching our site. It'll be a website, photos and blog, so this blog will go back to being a technical blog. We'll let you know more details when it happens, and if you are subscribed to the emails, we'll unsubscribe you from here and start a new subscription on the new blog.

If you haven't heard, and facebook hasn't told you, it's official. Sara and I are engaged!!

We'll let you know more details later!

God Bless

Tim

Isaac Adam Attfield

Born 6:47pm, 23rd September 2008
6 pounds 11 oz.

Our handsome new nephew. Welcome to the World!

Congratulations Sarah and Martin. Look after your baby brother Emily!

Well it works, but unfortunately the program is windows only, and it means you need a computer. That's no good for normal messaging. So what did I do? What any geek in my position would do naturally.  I observed. Quite simply, I observed what the program did. Of course, I didn't just look at the screen while using the program, I also looked at what it did behind the scenes, in particular on the network (internet). As it uses SSL (HTTPS) it wasn't the easiest thing to observe, but my perseverance paid off, and soon I had a transcript of the program talking to the server. Thankfully it was a rather simple conversation, using XML, and no fancy hand shakes. A single XML POST request would authenticate the user, and send a message, with a simple XML reply. So I didn't have to worry about doing an authentication, keeping a cookie, or a fancy hash or something, and then working more fancy magic to send a message. A simple template XML request, fill in the blanks, and submit, and the server would send the message and give back an XML reply saying that the message was sent. A very simple API. And I didn't have to reverse engineer anything to work it out.

Of course, the next step was to write a simple program that could be used on the phone to send a message via the API.  The most basic of programs can be written in about 5 lines in PHP, but of course I needed it to be easy to use, with some security, so I've gone a little beyond the most basic. I present a simple form, a drop down to select the number to send to (to keep it secure, so that only predefined numbers can be sent to), a box to type the message, an input field for a security password, and a submit button. Of course, then below when you hit submit, it gives you feed back with the message length, it lets you know that it's trying to connect to the API server, when it's connected it sends it, and lets you know the results. Probably more feedback than is needed, but what the heck, it's not for public use.

Now for anyone else wanting to do something similar, I'll help you along a little, by providing some of the required components, namely the XML templates. You'll have to work out how to use them, write your own software to use them, and also what the server is. Oh, and what the phone company is. I'm not going to risk some phone company getting upset at me, so nothing I provide will apply specifically to some phone company. It could be any one of them. If you work out the phone company, and contact me through the contact page, I'm probably more than willing to assist you in filling in the blanks, to save you some trouble. Or letting you know a way to fill them in yourself.

The POST request with xml template. You can see all the variables that need to be filled in. You may also be able to omit some things and simplify it. I did do some tests and you can simpify it a lot. A word of note, $userid is not your phone number, when you register for the service, there is an internet ID associated with your number, which you use for logging in. Discovering that is another thing I'll leave up to you. $messagetype is ether "text" or "text/concatenated" if the message is longer than 160 chars, otherwise it'll be cut off. There is a total message length limit for concatenated messages, of about 450 letters. You'll also have to work out the page it submits to, the useragent (which may not be needed), and the host it submits it all to.

POST /OAK/$page HTTP/1.0
User-Agent: $useragent
Cache-Control: no-cache
Content-Length: $length

<sms><authentication user="$userid" password="$userpassword" client_app="$appname"><product name="$appname"/>
</authentication><message from="$usernumber" type="$messagetype" responseDetail="3" action="send"><content>
<![CDATA[$message]]></content><message to="$number"/></message></sms>

A XML reply when the message is sucessfully sent looks like this.

HTTP/1.0 200 OK
Content-Type: text/xml
Content-Length: 167

<sms>
<authentication>
<product></product>
</authentication>
<message ref="1" status="0">
<content></content>
<message ref="2" status="0"></message>
</message>
</sms>

Adam and Rosy

I have few words atm, as I come to grips with the loss of my baby sister. Sara and I have flown to Perth to be here with my family, and the other families. Please keep us all in your prayers, and especially the 2 in hospital still, Adam being one of them, Rosy's boyfriend.

I miss you little sister. I love you. Go be with the Father now. Say hello to Elizabeth for me, and Grandpa.

Young love dies in crash which claims 3 lives
Teenage couple's love was obvious

I leave early tomorrow morning for the 2 hr drive up to Mt Binga, so please pray I have a safe drive, and my transition into the staff goes smoothly. They don't normally have people start 1/2 way through the year so the rest of the staff would already known each other well, and I have to now fit in. Still, I look forward with excitement.

God Bless

Tim

I know it's been a very long time since an update email, so this is long overdue. Since my last updates, my laptop had died in Singapore, I had arrived back in Perth, I went to work on the farm, my laptop was fixed, my Digital SLR was fixed, I had a 21st, I flew to Brisbane, I registered for Centerlinks New Start allowance, I turned 21, and I was finally reunited with Sara. Yep, lots happened.

I've been in QLD for just over 2 weeks now, and while at Church on Sunday morning, listening to the rapper Burning Bush preach, I just knew that I had to head out to Googa Outdoor Education Camp, where my mate Clancy is working. We had planned on heading down Thursday and Friday of this week, but on Sunday I knew we had to go that day. I had already sent them my resume in case they had work. So Sara, Jess and I packed an overnight bag, some food and lots of warm blankets and headed out past Blackbutt to Googa. Then yesterday morning after a sleep in (for once), we had gotten up and started cooking pasta for breakfast when Clancy hailed me on the 2 way telling me that another campsite down the road had a position open. So I drove around to the office, and called the other campsite, and organised an interview for that afternoon. A 1/2 hour drive down the road and you arrive at the Mt Binga Immanuel Lutheran College Campus. After an interview, a chat and a tour, we headed off with a promise of a call after they had talked to the Principal. And while on the 2 hour drive home, the call came with a 1 month initial contract, and then if all works out, the rest of the year!!

Basically, one of the girls working there had a motorbike accident some time back, and had a knee surgery, yesterday morning Mt Binga found out that she wouldn't be good to work again till after December as she needed a second surgery now. And why was I down there anyway? Because I just knew I had to go out to Googa earlier than we had originally planned! God is good. I head down tomorrow morning.

It's exactly what I wanted, youth work, outdoors, Christian environment. And God opened the doors as needed. The only down side, I hardly get to see Sara, and she leaves in 3 weeks. Sara's door was opened a few weeks back with her acceptance in to a School Of Frontier Missions in Taiwan, and she'll be leaving Mid September. It's a bummer that having been apart so much this year, Sara and I are going to be apart again sooner than we had thought. But God knows what he is doing, he opened these doors, and closed others. He has provided for us, and thankfully we've had the last few weeks together. Hopefully we'll be together for Christmas, whether that's in Cambodia or Brisbane. (Cambodia would be nice, especially if Jess is over there, and Susie comes too). It's in God's hands, he will provide as we need.

Anyway, I've got a lot to sort out now, as I leave tomorrow and need to pack my stuff, and go buy some stuff for my new room. (It's gonna be cold!) Please keep my work in prayers, and Sara's school in prayers too. She is still trusting for school fee's, and support money while there.

Once again, thanks to everyone who has supported us in prayers and finances. Also, I am attempting to send some support money to a student in South Africa that did her DTS with me. If anyone wishes to help support her too, please ether contact me or my dad.

God Bless

Tim

Tomorrow I'll be starting to sort out my laptop, camera and dentist. Thanks for everything! Thanks for all your prayer and support.

God Bless

Tim

God Bless

Take Care

Thanks for everything. (I have another blog to post when I'm back on my laptop)

Tim

After Graduation this evening, we headed down to Cafe Kima, one of our local hang out spots. There we were, an Australia, a New Zealander, and a South African, having a drink together. Steve had his first beer in 6 months, and I had a nice Jack and Coke. I understand many jokes start off with an Australia, New Zealander and a South African in a pub, so we took a photo to remember the funny side of it. Most of the team still in JBay joined us at the cafe, although you could see the "groups" already starting to form. Those who's boyfriends had come down, kinda just congregated together. Steve, Richard and I sat together, and were joined by some of the staff briefly. Then a table of just girls formed. It was a little sad to see the groups forming, as we got there first, and invited everyone to sit with us when they arrived. But fair enough, we are all going different ways, so it's OK to sit apart.

While I would love to go to bed, the work isn't finished yet. I now have the task of burning DVD's full of photos. Our grad slide show of photos (for the Swazambique team) will be on the DVD, along with outreach photos. And probably lecture phase photos too if I get the time. It's rather time consuming to shrink a couple thousand photos, and also go through them taking out the "junk" ones. I also wonder how many people will go through all the photos. I know that I'd start going through them with friends, but would never get through them all. I'm glad I made the slide show already, because it's 5 minutes, and is actually a good representation of our outreach, so it'll be good for sitting down with friends and showing them the video. On a little technical aside, the slide show was rather a work of art for me. I wrote my own software to take a directory of photos, shrink them down and put frames around them and then choose the best template for them, depending on how many portrait and landscape photos there are. It also allows for photos to be fullsize on a page. It then takes a background image, makes a title page, blurs the image for all the following pages and arranges the framed photos according to the template, while adding some randomness to make it look more like a photo album thats been thrown together, and not a template. I was rather impressed with it myself, and after combining all the "pages" into a video with just a simple fade effect between pages, it came out looking rather kiff. I had quite a few people comment on it after, about it looking professional, and something they hadn't seen before (in particular, it wasn't like lots of peoples power point shows). I will most likely release the code for it after some clean up. But before then, you'll be able to download the video (a compressed version), sometime after I arrive back in Perth and upload it. So you'll be able to comment yourself on the style!

Anyway, putting the aside, aside. Tomorrow Steve and I have to say goodbye. A strange thought, yet it shouldn't be hard. A group of us will be at Bruce's for our last breakfast, and then hopefully having waffles for lunch!! It's going to be a quite weekend. Almost lonely. But I have lots I want to finish on the base before I leave, regarding the wireless internet, and the server. So I should be busy!

Anyway, that's all for now. Thanks to everyone that has been supporting me through my DTS, in prayer, finances or even just chatting. It's been much appreciated. My DTS has been a life changing experience, and I hope that you all see how I've been changed when you get a chance to see me again. I will write about where I feel God is leading me later, but for now I'm keeping that fairly much to myself and few close friends. So stay tuned, God has big plans for you, me and this world!

God Bless

Tim

DTS. 165 days. And everyone worth it! DTS = Discipleship Training School == Dying To Self

Sara is back in Cambodia. She is in a village with no electricity or internet and may be out of contact till July 5th.

I fly home next monday, arriving in Australia on tuesday.

And I think that's about all for now.

Thanks for all your prayer and support. Looking forward to seeing everyone again!

God Bless

Tim

The money has come through and we have spent most of it already.  Our older
kids all have the track suits they are required to wear for the winter and
we are using the rest of the money for the odds and ends the rest of the
kids need.

Thanks again for your generosity.

Regards,

Aaron

So once again. Thanks to everyone that donated.

God Bless

Tim

Anyway. All safe. Other team arrives tomorrow.

Tired. Shower and off to the sunrise soon.

Thanks for all your prayers and support

God Bless

Tim