Bar Camp Brighton 4
Arriving at my second barcamp though I knew the format I was a little unsure about how it would all pan out.
During the introduce we each had to say a secret, these varied from “I have a pointy head” to “Last night I was caught stealing some fluffy grass from a garden”. My secret was “I was paid to call my self Earl for the day during TweetCamp”. A different way to lighten the mood and start the day.
The first session I attended was Tom M talking about the philosophy behind URIs. This took place in the Ninja Turtles Sewer. An interesting look at the philosophy of having perminint links to data online.
The second session in Honk Kong Fooey’s Filing Cabinet on Blogging Tips and Tricks. Miss Geeky (http://www.missgeeky.com) giving an interesting outlook on how she drives her blog. Two posts a day is but one example. Also the opportunities that have arisen through blogging are pretty amazing. Blogs are usually just for a small niche but to be popular blog about everything.
Lunch consisted of sarnies, various odd combinations including Turkey with Avocado and Ham with Egg.
After lunch there was an introduce to Android and the application development. IT gave a veyr braod over view of android and a basic hello world During this session I attempted to flash the latest google code drop on. This bricked my phone.
I spent the following session un bricking my phone.
After the coffee break it was my time to talk about Android. I started a discussion if Android was really open source. This continued into the android interface on a HTC Hero Android Source veruss traditional, and why Google is really not all that different from Apple in the terms of Phone OS Owner.
/Dev/Fort
What we did on holiday, a discuss a dev-fort. An interest take on barcamps. The idea of 5-20 people attending a camp in a fort with NO internet access. A brave thought for many people. More information can be foundhere http://devfort.com/
The final session before dinner covered hacking tweetie to work with groups. This appears to be by hacking tweetie binary in hex editor changing the urls used to request the twitter updates from a local server. The local server modifies the calls being sent to twitter and caches the tweets. Then tweets are sent to tweetie as required.
This pretty much sums up the talks I attended during the day. The evening continued with 152 pizzas to feed us and a hell of a lot of beer available. I crashed out quite early, possibly the first
Trackbacks /
Pingbacks