Note: I started writing this past year after the festival finished, and then I went heads down into an spiral of web audio hacking and conferencing and what not, so I didn’t finish it.
But with the festival starting this Friday, it’s NOW OR NEVER!
Ahead with the PUBLISH button!
(AKA #MozFest everywhere else)
a week almost a year ago already, but I’m still feeling its effects on my brain: tons of new ideas, and a pervasive feeling of not having enough time to develop them all. I guess it’s good (if I manage it properly).
I came to the Festival without knowing what it would be about. The Mozilla London office had been pretty much taken over by the Mozilla Foundation people from all over the world who were doing their last preparations in there. Meeting rooms were a scarce resource, and one of them was even renamed as “MF WAR ROOM”, until someone came next day and re-renamed it as “MW PEACE ROOM”. So, it was all “a madhouse”, in Potch’s words, but amicable, friendly chaos after all. Hard to gather what the festival would consist of, though. So I just waited until Friday…
Days that take Sole to want to get rid of the stable build and want to go to Nightly so she can fix the little things here and there that annoy her: 1.
Days that she spends “distracted” with a Jewels-style game: 1.
Hence the jump from day 1 to 3.
I went and compared the stable version with the Nightly version I had flashed on the other Flame and most of the bugs were gone. So I figured that since what I actually want is to “scratch my itches” (another terrible software metaphor) what I’ll do is flash a recent Gecko and work with my custom build of Gaia where I can do whatever I want. WHATEVER. I. WANT. YES.
(Sending a patch and getting it accepted will be an entirely different matter, but maybe I’ll convince everyone that using .ANI files on the home screen is a good idea)*.
I’m kind of getting acquainted to the one-button navigation, but sometimes I sorely miss Android’s BACK button. I’m not sure if that’s because the apps don’t open new links in the right way or why it’s that, but I find that going back to where I was takes me more time than I’d like it to take. I’m not sure how will new users find this workflow–maybe I’m conditioned to find it not as cool but new people love it, so I’m not complaining much about it until I investigate on the best way to open links… but before that, I need to update Gaia!
* Hi, if you thought I was serious, you’ve just been trolled.
Today I finally got a Flame to use as my main phone (what they call dogfooding, but it sounds atrocious to me). I had been using a Flame for testing since June or so, but I kept flashing nightly builds and let me tell you… it’s risky at least.
Sadly I was busy attending other matters (namely the DevTools meetup which is happening this week at the London office) so I didn’t have much of a chance to experiment on the phone.
My main goal was basically flash it with an updated version of the operating system, since the Flame comes with 1.3 and I wanted to use 2.x. Then I took my SIM card out of my Android Nexus 5 and put it into the Flame. Bam, it works. Including data! No need to tinker with GPRS and APN settings and what not. Sweet! I already even got a spam call advising me on how to claim compensation on that accident I never had. Yay!
I also imported some of my contacts from my Google account. The importer lets you connect to GMail and then loads the contacts, and you can go through the list to choose which ones to import. Good time for some pruning of old contacts I haven’t spoken to in a while :-P
There were some weirdnesses on the rendering but I didn’t file a bug yet as I want to compare with the other phone and a freshly flashed version and see if the weirdnesses have been fixed or not.
I can also confirm that the Twitter “app” (it’s actually more like a glorified bookmark for m.twitter.com) for FxOS is as terrible as usual. I keep internally whispering to myself: OAuth, Oauth, tokens, rate limits each time I try to use the Twitter app and get frustrated by how badly it works on every single mobile browser, so as to scare myself and avoid writing my own client with support for offline and push notifications.
Now I have to find out how to configure the alarm clock. If it doesn’t work I’ll be late to the office tomorrow—it won’t be my fault! :P
Oh and before you ask: no one at Mozilla is forcing us to use this or that phone. This is just done on my own volition because other platforms keep creeping me out and I’d rather contribute to something I can trust.
PS I don’t actually have any grand plan for writing a long series of posts on my experiences on using the Flame as my main phone so don’t get too excited, teehee!
As with the Extensible Web Summit, we wrote some notes collaboratively. Here are the notes for the Web Audio Hackday!
We started the day with me being late because I took a series of badly timed bad decisions and that ended up in me taking the wrong untergrund lines. In short: I don’t know how to metro in Berlin in the mornings and I’m still so sorry.
I finally arrived to Soundcloud’s offices, and it was cool that Jan was still doing the presentations, so Tiffany gave me a giant glass of water and I almost drank it all while they finished. Then I set up my computer and proceeded to give my talk/workshop!
It was an improved and revised version of the beta-talk I gave at Mozilla London past past week:
Note to self: maybe remove red banners behind me if wearing a red shirt, so as not to blend with them