I’m offering a small run of mate cosies: “warm hands, cold mate” for this winter season. Each mate cosy is produced on my hacked kh930 knitting machine, by hand by me (the machine isn’t motorized yet) and then finished by hand by me. They are available in this limited run (probably around 40 pieces total) for a price of 60 euros for either black/white or black/red. If you would like a special order QR code on the front of your black/white cosy, that will cost 80 euros. The QR codes don’t really work very consistently since little knit v’s are not easily recognized as square pixels. They sort of work in the dark. You could improve this by writing a QR code reader filter that “sees” v’s as pixels. If you are the first to code such a filter, or if you are the first to code up any other means for creating readable QR codes for knitting, and you open source the code, I will give a cosy to you for free.
Shipping will not exist, in other words, this is for Berlin pick up only. Payment is either by German bank transfer or by cash in person during 28c3 or during BerlinSides or during BreakFast. This small run of cosies is a bootstrapping attempt on my part to raise money to fund a commercial industrial factory knitting run of 500 pieces of my 1D CA scarf. The proceeds from selling the scarves will raise money to purchase or at least partially purchase an industrial knitting machine myself to hack, open source, and run small knitting production runs locally. So if you purchase one, you are helping to create open-ness in textile manufacturing as well as make my life that much more awesome while I work on this project.
To order a mate cosy, drop me an email to fabienne at the name of this website. Please specify color (black/red or black/white) and/or QR code (black/white only). QR codes are available up to 25×25 (QR code Version 2) but I recommend QR code version 1 in 21×21 pixels. For the QR code, please don’t submit more than error correction L (the lowest) because it won’t help. The mate cosies will be sold on a first emailed (don’t play with your email headers, geez), first payed, first served basis. That means that I will email you back with a confirmation and the information on how to pay to secure your cosy.
Quite a few thank you’s are in order for even this small run: Marcus Loscher for ok-ing a small run of these related to his company’s delicious product club-mate, Lisa for her suggestion that I put a hand-warmer in the cosy, (thanks! I did!), Astera for her help in testing prototype four, Travis for his never ending help both in our crazy drive in November of 2010 to pick up the machine and our subsequent four days of no sleep and his support since then on software and hardware which we will be able to offer as a kit in the future, Skytee for his testing and de-busying of the pattern suggestions, LadyAda and Becky Stern and Steve Conklin for open sourcing and documenting their knitting machine efforts which allowed us to extend the hack, Jimmie for helping test QR code reading and error correction levels in double bed jacquard knitting, Steel Breeze for her help in documenting double bed jacquard and hands-on help with carriage setting, and the lovely machine knitter people who helped on the knitting machine boards on Ravelry.
Now for some hypertransparency! The cosies take about 2.5 hours each of my hands-on time to complete. The yarn for the cosies is Hamburger Wollfabrik “Pretty Woman” 60 percent extra fine merino, 40 percent acrylic. That means these cosies are machine washable cold on a delicate setting, but I recommend hand washing cold first with a bit of wool-friendly detergent in case the dye runs a bit. Each cosy uses 83 grams of wool. The black/red cosies use 60 grams of black, 23 grams of red, with 28 grams of the black in the ribbing. The black/white cosies use 32 grams of black, and 51 grams of white, with 28 grams of the white in the ribbing. Each cosy uses about 3.34 euros of wool.
The largest cost with regards to this production is obviously my hands-on labor. With the way knitting machines work, this hands-on production cost is not possible to reduce without owning or having access to an industrial knitting machine instead of my lovely but limited hacked consumer kh930 knitting machine from 1981. Even if I were to machine sew some of the seams, it wouldn’t speed up the time of hand casting off the gathered edge at the very top of the cosy, and the seam to the inside of the ribbing to the main body needs to be blind stitched in the double backing (not possible with a sewing machine). All that means is that I’ve made these as stream lined as technically and humanly possible, but it still takes a mini sweatshop style production on my part to produce them.
On the off chance that you have access to a hacked Brother knitting machine, or a knitting machine that can accept a computer defined pattern, here is how to make your own. If you offer these for sale, please don’t use the club-mate logo unless you have prior permission from the copyright holder. Please use your own art, and do so with creativity and awesomesauce. Here is the pattern:
Mate Cosies a pattern for knitting machine fun and mate lovers
Mate Cosies by Fabienne Serriere is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Requirements: Brother KH930 hacked, Brother KR850 or similar double bed, Brother double bed color changer (KRC900 or similar).
Cast on 38L, 39R on the main bed and 38L, 38R on the double bed, as for ribbing with the needles offset. Set the yarn mast tensions to +1. Set the tension on both beds to zero, set the double bed to extra firm with the II lever to the right, and cast on right to left with your ribbing color (black for black/red, white for black/white). Hang your double bed cast-on comb and add weights.
Change the top carriage to slip left with the left part button pushed in. Change the bottom carriage to slip right with the right part switch pushed up. Change the extra firm lever on the double bed back to I. Change the tension on both beds to 1. Knit 3 circular passes (l-r, r-l, l-r) ending on the right side. Change both top and bottom carriage to ribbing setting by canceling the part buttons. Knit ribbing for 65 rows.
Hang extra claw weights on the edges of the knitting. With the carriage on the left, set your 77 wide by 96 stitch long pattern in the knitting machine’s memory with your hacked machine setup or with your proprietary computer link. Use a pattern that is simply two color, the kh930 will automagically explode it to double bed jacquard with the KRC key. Press the KRC key. While on the left, set the main carriage to KC(II) and set tension on both beds to 3. Push the carriage past the left turnaround mark, load in your main color (for both of my cosies, that color is black) and pull the carriage from left to right once across the bed. Now set the main carriage to slip in both directions, leave the KC(II) knob selected and set the double bed for birds-eye backing by setting both slip levers to P.R, select both the left and right “lili” knobs to “lili”, and set the tension lever to “lili”. You are now set up to knit double bed jacquard with an auto-backing in a mechanically defined birds-eye pattern. As you push the carriage across to the left towards the color changer, the display on the kh930 will tell you the next color (1 or 2, main or contrast, black or white, black or red) to chose in the secondary seven segment display. Continue in pattern until you have knit all 96 rows of your pattern, moving the claw weights up every 20 rows or so on the edges. When complete, the machine beeps. You will now have the contrast color and be on the left, change to the main color (black). Reset for ribbing (full needle rib as for the first half of the pattern) and clearing all the part buttons on the top and double bed, set the main carriage knob back to N.L, clear the “lili” knobs on the double bed, set the double bed tension lever back to I on the left, set the tension on both beds to 1. Knit two rows of ribbing in the main color, ending on the left. Use the color changer to change to the contrasting color or waste yarn, and knit 4 rows to perform a scrap off cast off. Cut your yarn, remove all weights, knit the carriage once from right to left to release the knitting from the machine.
Cast off by hand with the tail of the main color (black) by stitching through each stich, front and back, of the black row. It’s easiest to do this two stitches at a time, run a tapestry needle threaded with the black tail through the top of the back (purled) stitch from the front side of the fabric, then through the left edge of the front (knitted) stitch. Repeat across the top of your fabric, lightly tugging to gather the top edge of your Mate Cosy. When you have sewn through all the live black stitches on the top edge, unravel your four rows of contrast/waste yarn until the left, and use the tucked in stitches as extra strength for your gathered edge. Trim off the excess contrast yarn, leaving a tail as long as your main color cast off tail. Next, fold the ribbed part of the cosy up against the back of the cosy. Blind stitch the ribbing down along the cast-on edge. Next with an extra length of your main color (black), stitch from the cast off edge down the right side of the back of the cosy. Use a standard knit seaming technique of your choice. Stop when you reach the ribbing, and stitch a few top stitches holding in the ribbing, the edge of the cosy and tuck in the ends of your stitching back and forth in the lining for strength and cut the yarn. Taking yarn the color of your ribbing (black for black/red, white for black/white), place your Mate Cosy over an empty clean bottle of mate. Stitch the ribbing tightly into place starting at the top of the ribbing and work your way down to the bottom of the cosy. Insert a piece of flat elastic in the bottom folded-over edge of your cosy. Tie or stitch the elastic to itself to keep your cosy snug and tight on the bottom of the bottle. Stitch a few finishing stitches on the bottom of the hand-hold area of the cosy to hide the elastic. Remove the Mate Cosy from the bottle, and thread both the main and contrast gathering yarn tails at the top of the bottle on your tapestry needle. Gently pull the yarns to gather the top of the cosy to slightly larger than the circumference of the place on the bottle where the top your cosy will sit. Be careful to not break the yarns while gathering. Stitch the yarn tails back and forth in the lining to strengthen the gather and keep it in place without a knot. Congrats! You now have warm hands and cold mate!
Fresh off the knitting machine is this algorithmically morphing scarf with a pattern that changes by one pixel in each repeat. The software was made by Laura Kogler and used by me with the hacked Brother KH930 I currently have. Laura Kogler’s pattern generator script is meant for mosaic knitting but I knit it as a standard two color fair isle pattern on my KH930. Knitting mosaic or slip-stitch on the KH930 is very operator intensive. It’s much faster to knit fair isle on the machine. It is a two-sided scarf with one side black on pink and the other side inverted with pink on black. I hand-seamed the whole thing together (which took days) and kitchenered the ends. It is knit in Hamburger Wollfabrik 3-ply Merino in a dark pink and black. It’s incredibly warm and soft, beyond the general nomminess of the algorithmically generated morphing pattern. The scarf has it’s own ravelry page.
The output I used from Laura Kogler’s script is pictured here below in teal and dark teal:
The output pictured above is 7 repeats wide, but I knit it 3 repeats wide for each side of the scarf. Each repeat is 26 stitches (pixels) wide, and the total length of the file sent to the knitting machine is 361 stitches (rows, pixels) long. I flipped the pattern upside down for the second half of the length with the KH930′s built-in pattern flipping functions.
I’m working on some general open source scripts for generative patterns for knitting machines, and so far I have thrown together some Processing code for creating random blocks in definable sizes: http://pastebin.com/HLgwmJA2. Eventually I hope to have some general open source algorithmic tools for the knitting machine to allow you to create much longer pattern morphs where the pixel mutations are more prominent. I also am writing in some auto-fill tools to add in patterns to blank areas in picture knitting so they turn out better with two-color knitting on knitting machines. The other killer feature will be to have options to limit the amount of repeats of one color in one row, to keep floats short on the reverse side of the knitting. Happy knitting to all you warmth-creating people out there!
In February of 2007 I worked out an argyle pattern based on my blue skull logo (see graph paper drawing below). In June of 2008 I knit the two color pattern up by hand (see shot in front of graffiti above). This week, August of 2011, I knit my skull argyle on a hacked knitting machine (Brother KH-930, documented here, code on github here). Sometimes it takes years to complete a project, especially if a project requires a new machine with which to make it.
The finished ipad sleeve (see images below) is knit from cotton on the hacked KH-930 (with computer control) and finished with a sewing machine. It isn’t all that complex, and is drawn pixel-wise on the Gimp and exported to the knitting machine with some code to emulate a TDD Tandy floppy disk drive, a bit of hardware, and some code to parse the resulting bitmap into a format which the knitting machine will recognize. This happened during cccamp11 where I had brought the knitting machine to demo in the HXX hardware tent. In the process I have learned all about the mechanics of knitting machines, their capabilities, how to get them to be computer controlled and the yarns that knitting machines like. In the end, I really still hate hand knitting two color stranded patterns, but I love the way the finished products look. The machine gets to offload that burden and still output beautiful pieces.
Update (September 18th, 2011): I redid the sleeve in a cotton that doesn’t fuzz so much, made the pattern repeat properly, and made the skulls right side up on both sides. The ravelry page for the first version is here, and the second version is here. The second version is pictured below:
and a before and after shot with the old on the left, new on the right:
Another friend of mine is going to get a dell mini 10v: the now discontinued easily hackintoshable netbook. Since I did the install and it was hellish from the current how-to’s available in June of 2010 (because of bit rot and lack of updates regarding versions of software in those how-to’s), I thought I would include some links and notes on how I got it finally working.
I bought a retail version of os x snow leopard 10.6.3 and tried to install it, but it didn’t work for me in the least. In the end I borrowed a retail version of snow leopard 10.6.0 from a friend, used it in conjunction with netbookmaker 0.8.4 rc1, from an external usb harddrive formatted from a working snow leopard 10.6.4 machine. You can’t format the external usb harddrive from anything lower than an existing snow leopard 10.6.0 machine.
Just to be clear: installing hackintosh directly from 10.6.3 doesn’t work, and won’t ever work. Find an earlier os x version 10.6.0 or 10.6.1 (in the retail version, single user copies won’t work) then upgrade but only step by step upgrades to 10.6.2 then 10.6.3. Currently my hackintosh runs 10.6.3 fairly happily, with some kernel panics about once a week.
I first formatted the internal harddrive when setting up os x to have 2 large partitions so I could then install linux as a dual boot.
To do my initial install I followed this how-to:
and then this forum post to step up to 10.6.3:
Then for the dual bootness with linux, I did a classic ubuntu install from usb stick and I think I fixed the grub issues by following this http://www.dailyblogged.com/booting-ubuntu-with-the-chameleon-bootloader/ … but I’m not sure since it has been several months.
I then successfully reflashed the hackintosh’s built in broadcom wireless card (from the ubuntu partition) with airport product + vendor id’s, + most importantly, region free for wifi channel 12 + 13, using this how-to: http://prasys.info/2009/12/rebranding-broadcom-802-11abgn-cards-as-airport/ . Please note that in step 8 of the how-to, the git path in that how-to has moved to this: git clone git://git.bu3sch.de/b43-tools.git . The system profiler on os x now reports my card as an AirPort Extreme with the Locale: ETSI and adds and subtracts channels based on my current location.
So now I have a working system where I use the chameleon bootloader to dual boot os x snow leopard 10.6.3 and Ubuntu 10.04 LTS Lucid Lynx.
after a long break in posting, fabienne.us has moved to a happy new wp hosting that i am administering myself, and has had a bit of a facelift. those of you who have followed this blog for more than a year will notice that it looks a lot like it did 2 years ago. yay for a new css of shinyness and all that!
the other big news is that i am living in cologne (germany) now full time, the 3rd annual hardhack happened and there will be even _more_ hardhacks this year as subconferences of other conferences.
Back in April I ran my first half marathon. I live blogged it with twitter and twitpic as many of you may have followed along. Here is the archived race report dredged up from the dregs of internet history (had to grab my back tweets from twitter history, maybe you just want a local backup of your last 3200 tweets, I used dacort’s easy one liner unix command).
a bit of sun. i’ve warmed up and started stretching. considering just taking e70? or maybe just g1? arg gadget decisions! #bhm
My official net time was 02:28:06 which is great considering how ill I had been the three months before the race thus cutting into my training. I truly focused on slowing down at the beginning, enjoying the run, and talking to some fellow racers as I liveblogged. Having my friends cheer me on via @replies on twitter was definitely a motivation. I will sign up for a marathon in june or july of 2010, and hopefully run another half during my training. Here is my shot at the finish, with the non-adjusted time:
If I liveblog another race, here is what I would want to have:
- a more waterproof mobile device
- number pad typing much easier than full keyboard typing while running
- voice to text would be ideal
- gps coordinates added to each post
- auto distance from gps calculated with splits would be awesome
just a quick update to let you know i was sponsored a 3d printer by wim of kd85.com and i built it and got it working. i presented some slides (odp format, pdf here) about open source hardware and how the makerbot fits into all that at openchaos at the C4 in cologne a few weeks ago. a photo build log of me putting mine together (some assembly required) is here.
i will be bringing ‘lectric to dorkbot aachen next week on wednesday, so stop by if you want to print something out or if you want to see a 3d plastic extrusion printer built from scratch up and running. you can design your own stuff to print and upload it to the thingiverse ahead of time, or just contact me with your digital file and some contact info by email fabienne attt fabienne do0tt us.
a 3 second short video clip showing ‘lectric, my makerbot, printing its very first print (a lego brick) is here below:
i have a media server that i have been working on (slowly) with 2.2 terrabytes of space, an ubuntu machine, amd 64 bit, with mythtv running (german dvb-t or cable tv recording capabilities). all this is well and good but i wanted a better interface to navigate my growing movie and tv show collection. enter xbmc, the interface optimized for couch use (aka with a remote) for navigation of a home theater pc. i have had some woes setting up xbmc, and about a year ago someone recommended trying boxee as it is xmbc + online social network, so you can see what your friends are watching and loving. it turns out boxee still doesn’t have package binaries for 64 bit linux machines, so there are a few hacks to get it working. here is what i did yesterday (after upgrading my ubuntu box to 9.04 jaunty most of the day). i tried a lot of different ways of getting boxee to work, here is what finally worked for me, a bash script for grabbing the newest package (hard to find url on boxee’s site, this script helps with that) and it installs getlibs, a way to getlibs for 64 bit machines with 32 bit packages.
and then to get the network recognized by boxee, add this:
sudo apt-get install lib32nss-mdns
next on my list is getting lirc (the infrared remote control stuff) working so my remote works better with mythtv (some buttons working) and to work at all with boxee (not recognized at all). it’s fun to pick up working on all of this after putting it aside for over a year!
My cousin’s girlfriend, and good friend of mine, Caro, has a gallery opening in Berlin next week:
THE WAY WE MET THE WAY / Marga Binsthock Matar – Caroline Gutlé
On a Tuesday evening I saw Marga flying.
She told me to come in.
With spiritual drawings she showed me her mind,
with the sound of my balafon, I replied I understood.
Now begins our story…
Gallery: Visual Jazz, Petersburgerstr. 47, 10249 Berlin-Friedrichshain
Tram: M10 Strassmannstr
Opening: 2.4.2009, 19h00. bis 18.5. , Di–So, 17h30–20h00
So come check out her work! I’m sure it will be a very neighborly and convivial opening, please join in.
i just came across some photos i made of my sister eating at a thai restaurant, once in 2002 in nyc, and secondly in 2008 in lausanne, switzerland. my mother (a professional analog photographer) used to take a series of photographs many years apart at the same location with the same sorts of clothing. if i can find it, i will try to scan the treehouse series (photos probably in a box of mine in storage in california), with my sister and i sitting in the same place in our treehouse many years apart.
at any rate, my sister and i remembered that i had shot a few photos in nyc at my favorite thai place in the east village, tara thai. this came to us when we were forced to improvise dinner plans in lausanne last year because a vegetarian restaurant no longer existed. we managed to convince our waitress to make thai iced tea as well, which the thai restaurant in lausanne insisted was only a summer drink. we didn’t look at the original photos when we reshot, only what we remembered. it’s mind boggling what the human memory can retain six years later from a favorite photograph. either that, or my sister has some sort of inherent thai food consuming pose coded into her dna. either way, i find it fascinating.
i struggled a bit getting backups going for our (mostly mac) office at doctr.com, but now things are finally up and running. i combined a first gen drobo, an airport extreme (wired over gigabit), time machine, and multiple macs with os 10.5.6 (leopard).
i mostly followed the “use sparse image” section from this post. here is what i did step by step:
- setup drobo with drobo dashboard directly plugged into one computer, format for max size (i chose 8TB because it would be faster boot time than 16TB, and frankly right now only 2TB drives are at a good price point, which makes 5.5 available TB if you have 4 x 2TB drives. i currently have 4 x 1TB drives in the drobo which makes 2.7TB available space. you can estimate available space with the drobolator), even if you don’t have that much space, this means you can slot in some bigger drives in the future without touching your setup, so make this max size BIG.
- next format the drive with os x’s disk utility with “Mac OS Extended (Journaled)”. if you don’t, you won’t be able to use it for time machine over the airport extreme. disk utility should see it as an 8TB drive (even though it really is much smaller). this step is currently incorrect on this page. you must chose “Mac OS Extended (Journaled)” (aka hfs+). this setup will absolutely not work if you choose just “Mac OS Extended”.
- the next step is the step outlined here under the heading “Best Method: Use a Sparse Image”. i repeated this step for all our macs at the office, making a sparse image for each with the correct hostname of each machine, the correct MAC address for each machine, and a different name for each -volname. for the sizes, i took the total disk space of each machine and added a bit of headroom for extra weekly backups with time machine. once time machine uses up the space alloted by the sparse image for that particular machine, it will start deleting older weekly backups. currently we don’t have any machines that are even using their full disk capacity, so i have a feeling my headroom will be plenty. make sure that when you add up all the sizes of your sparse images, that your total is less than 95 percent of the drobo available space you estimated with the drobolator. so i, for example, have 4 x 1 TB drives in the drobo, which gives me 2.7TB of available space, so i should keep the sum of all my sparse image files under 2.565 TB. the nice thing about definining these sparse image files is that you can make them bigger later, if, for example, you add a new drive into a machine (or if you upgrade the total usable disk space of your drobo by putting more/bigger drives into your drobo). to increase the sparse image size , “disconnect all users” in the airport utility and plug your drobo directly back into a tower or laptop. in the command line:
$ hdiutil resize -size 1500g nameofsparseimage
you can also add more sparse images by doing the same thing, disconnect all users, plug the drobo back into a machine, add a new sparse image for a new machine you want to backup.
- once you have all the sparse images on the drive, eject it from your computer, and plug it into the airport extreme (via usb). now setup your airport extreme with the airport utility. choose “Manual Setup” and the “Disks” tab up top. the airport extreme will not report the right size of the drive, don’t worry about that. under the “File Sharing” tab, check “Enable File Sharing”. for me, the way it seemed to be happiest was to choose “Secure Shared Disks: With a disk password” and “Airport Disks Guest Access: Not allowed” and leave “Advertise disks globally using Bonjour” unchecked. Click the “Update” button at the bottom of the airport utility and let the airport extreme reboot completely. i had some problems when playing with configs that the airport extreme wouldn’t reboot properly. a friend noted that this was because the airport extreme sometimes pulls power from the connected disks and doesn’t totally reboot itself. my solution was to unplug the usb from the drive and unplug the power cable from the airport extreme. then repower the airport extreme, then plug in the drive once it has booted back up again.
- now you can configure time machine. on one of the machines for which you have made a custom sparse bundle, open a finder window and select your airport extreme from the “shared” tab on the left. click the “Connect” button and enter the disk password you defined in the airport utility. the drobo should now be mounted as a shared drive in your finder window, and you should be able to see the sparse bundles you previously made there. now open time machine preferences on this machine and choose disk/change disk. if you have followed everything above, you should see the drobo in the list of available drives. you won’t see any different partitions or the sparse bundles, just choose the drobo drive. time machine may ask you for the disk password again, this can be your username and the disk password you set in the airport utility. (backups should work for all users on the same machine, even if you don’t expressly go into each user and setup time machine, this should be a system wide backup.) now start your backup. when your backup is going, the sparse bundle should mount as a drive on your machine (maybe even on your desktop if you have the Finder pref “Show these items on the Desktop:” “External Disks” selected.) your backups should be only written to this sparse bundle and not write anything extra to the drobo. verify this by navigating in your finder to the airport extreme and make sure that only your sparse bundles that you first made there are listed. if there is anything extra apart from your original sparse bundles, you made a mistake in step 3 with the name of the machine or the mac address. each machine should only write to its own sparse bundle for which you have defined a set size. now time machine won’t try to eat up your entire drobo’s space (in my case 8TB) and stay within the size parameters you set in step 3.
this setup has been up and running for a few days at this point, and i can use time machine (though it is a bit slow) on each machine to step back in time. i will report later if there are any issues with the airport extreme requiring reboot or issues with the drobo. for now it’s all crunching along quite nicely, and i’ve even swapped some disks in and out of the drobo to upgrade my total raid space. i don’t have an offsite backup solution yet, but i’m considering doing backups every two weeks using super duper! with external terabyte drives for each machine. all in all, the drobo is an awesome raid solution that works so painlessly with different sized drives, but getting it to work with a multi-mac setup was a tad more than i bargained for. feel free to leave comments if i left something out, or if something in this outline doesn’t work for you.
lots of hardware related events are coming up. first of all i will be speaking informally at the baustel-montag this coming monday about hardhack. next up i will be speaking during re:publica about open hardware (namely licensing and historical implications of open circuit information). i will most likely attend sigint, (the ccc event not in december and not in berlin). after that comes my event, hardhack, which will be only hands-on hardware stuff, no blah blah at all. then ph-neutral which this year will include some hardhack components. and the newest addition to my roster, i will be organizing HARdware, a pre-HAR2009 event to build some really awesome interactive hardware things for attendees of HAR to play with during camp. my project will be a group of networked, interactive, and hackable couches in the slacker dome. other projects may include a huge outdoor capacitive dance interface, cotton candy representations of network traffic, and walls of networked color changing pixels. contact me (fabienne @ this website) if you want to get involved!
i’ll be giving a talk at the Free Software Foundation Europe fellowship meeting in Berlin this week Thursday, February 12th 2009 at 19:30 at the New Thinking Store, Tucholskystrasse 48. more info here. i’ll be speaking on open source hardware and the presentation will be in english.
i was reluctant to start reading the book Anathem by Neal Stephenson because i was afraid that i would be depressed about living in the present. i voiced my apprehension to the author at a book reading here in Berlin. he thought it was a silly fear, and thus i started absorbing the pithy mathtastic volume. i usually jot down page numbers of my favorite passages at the front of the book, but since this one had been autographed and dedicated to me, i figured i shouldn’t sully it with my usual pencil scratches. [sidenote: why aren't there ebook readers where i can annotate (underline and scrawl notes in the margin) and do full text search yet? get on it ebook creators.] so i twittered my three month journey through this mathic universe. notable quotes include:
p. 171: “When I recited the 127th through 283rd digits of pi, the fight went out of them.”
p. 210: “his plan had another advantage as well: it was flagrantly silly.” recreating battles with weeds vs. garden. awesome.
p. 351: “…desperate men living on the top of a mountain, eating lichens.”
p. 642: “We are speaking of an infinitesimal snatch of time just after the Big Bang…”
p.721: “anything else, as long as i have a channel open?” “is it a private channel?” “don’t be ridiculous,” he pointed out.
…and on page 799 reference to euclid’s proof that the square root of two is an irrational number. this was an incredible read, one which i hadn’t anticipated i would enjoy, but in the end it wasn’t the future world or its mathy inhabitants that drove the story. as always, it was the incredible characters that propel a narrative that only stephenson can weave into a cohesive story. i loved the whole journey.
so after all those nokia posts over the years, for the first time ever, i don’t use a nokia as my mobile device [updated feb 6th, 2009, see bottom of post] (mobile phone? cellphone? does anyone make calls anymore with these devices?). yes, i broke down after seeing eliot’s dev version g1 android google phone and bought a new phone. i was waiting way too long for a replacement for my aging nokia e70, and i couldn’t wait any longer after the release of the curse of silence at the end of congress (my pics of 25c3 here). so why would i break down and use a google phone after all my anti-google rants? i can’t stand the iphone’s touchscreen soft keyboard: the iphone is just a pull device for me, not a push device. the openmoko is great in theory, but once again i need a keyboard. the google phone is pretty much the only option for me right now, short of getting another nokia that i’m not happy with.
it’s a bit shocking to realize the uptake in the open source mobile development community around the android. i guess i never thought about the iphone app store having a competitor in the google android market, but it’s got crazy uptake. some thoughts on my g1 in the last 21 days i’ve had it (largely compared to e70, rockstar of an old phone that it was):
- 24 days ago: omg omg omg my g1 dev version arrived just now! my g1 android phone’s back battery cover smells like rubber in new shoes. i’m like a kid in new clothes on the first day of school. yay data plan working in g1 android dev phone. (i must find a shorter way to say that.) i feel so dirty as an ex-nokia-fangirl.
- 23 days ago: acquired 8gb micro sd for g1, 1tb ext hdd for photo backup/processing. space: i has it. yay k9 mail on android g1 phone works with self signed imap certs! i can haz email on my new phone! i want a real jabber client for the g1 phone (general xmpp, maybe off smack?, sexier than this. ) who wants to help?
- 20 days ago: @timbray The truth bout multi-touch and the Android G1.
- 17 days ago: the g1 dev version standard headphones suck so so bad. guess i will have to mod them with minijack. oh wait wasn’t i doing this in 2005?
- 14 days ago: g1 shows up fine over usb with g5 tower at work, not on ubuntu media server or g4 tower at home, with card reader or tethered. frak. 1gb micro sd from g1 mounting just fine on ubuntu media tower, syncing just fine with amarok. 8gb frak up is a mystery. arg found a how-to for repartitioning large micro sd cards for g1 android right when i needed to leave the house. less travel, more nerding.
- 13 days ago: so amarok did sync all the songs, id3 tags, file folders, + even album art to g1. BUT: no playlist file. meh, “repeat all” for my shower. cannibalizing hacked nokia popport to mod g1 headphones. deja-freaking-vu.
- 8 days ago: weird bug on the g1, camera takes one pic, then says i need to insert sd card. playing music at the same time off sd card.
- 4 days ago: my g1 has lost connection to my cell carrier 3 times in 2 days and requires hard reboot. wtf?
so the basic thing is, this is a sexy phone, with a backlit full keyboard, but it’s definitely beta to the max. the battery life sucks (haven’t tried different battery mod patches yet), and it has some issues with keeping a cellphone connection in places of crappy signal that cuts in and out. however, that being said, the android market with its over-the-air downloads and installs is a huge HUGE huge contender to the iphone app store. i must say that’s the big point of this phone, it’s in an interesting position of open source and useability. when i bought it at the beginning of the month, i did not expect to be inspired to write or patch apps for it. and now, well, i very well may code some stuff up. final verdict for my g1: i don’t hate it i’m going to switch back to nokia for the time being.
update feb 6, 2009: i tried tethering and couldn’t even get this broswer proxy server to work. not being able to share my 3g connection with my laptop was the last straw for me. i am going to switch back to my nokia until the g1 has:
- a jabber client that deals well with disconnects and saves your login credentials.
- better battery life.
- a way to share a calendar without going through gcal.
- a way to tether 3g properly to a laptop, either cabled or wireless.