Addressing Issues vs. Assessing Unproblematic Uses (Rant)

A good example of something I tend to dislike, in geek culture. Users who are talking about issues they have are getting confronted with evidence that they may be wrong instead of any acknowledgment that there might be an issue. Basically, a variant of the “blame the victim” game.

Case in point, a discussion about memory usage by Firefox 3, started by Mahmoud Al-Qudsi, on his NeoSmart blog:

Firefox 3 is Still a Memory Hog

Granted, Al-Qudsi’s post could be interpreted as a form of provocation, especially given its title. But thoughtful responses are more effective than “counterstrike,” in cases in which you want to broaden your user base.

So the ZDNet response, unsurprisingly, is to run some benchmark tests. Under their conditions, they get better results for Firefox 3 than for other browsers, excluding Firefox 2 which was the basis of Al-Qudsi’s comment. The “only logical conclusion” is that the problem is with the user. Not surprising in geek culture which not only requires people to ask questions in a very specific way but calls that method the “smart” one.

How to ask a question the Smart Way

One issue with a piece like the ZDNet one is that those who are, say, having issues with a given browser are less likely to get those issues addressed than if the reaction had been more thoughtful. It’s fine to compare browsers or anything else under a standardized set of experimental conditions. But care should be taken to troubleshoot the issues users are saying they have. In other words, it’s especially important for tech journalists and developers to look at what users are actually saying, even if the problem is in the way they use the software. Sure, users can say weird things. But if developers don’t pay attention to users, chances are that they won’t pay attention to the tools the developers build.

The personal reason I’m interested in this issue is that I’ve been having memory issue with both Firefox 2 and in Flock 1.4 (my browser of choice, at least on Windows). I rarely have the same issues in Internet Explorer 7 or Safari 3. It might be “my problem,” but it still means that, as much as I love Mozila-based browsers, I feel compelled to switch to other browsers.

A major “selling point” for Firefox 3 (Ff3) is a set of improvements in memory management. Benchmarks and tests can help convince users to give Ff3 a try but those who are having issues with Ff3′s memory management should be the basis of a thoughtful analysis in terms of patterns in memory usage. It might just be that some sites take up more memory in Ff than in other browsers, for reasons unknown. Or that there are settings and/or extensions which are making Ff more memory hungry. The point is, this can all be troubleshot.

Helping users get a more pleasant experience out of Ff should be a great way to expand Ff’s userbase. Even if the problem is in the way they use Ff.

Ah, well…

Browser memory usage – the good, the bad, and the down right ugly! | Hardware 2.0 | ZDNet.com

Bubbling Wildly

Lag time on last night’s batches was quite short. In fact, the “Mighty S-04″ lives up to its reputation: in a large bucket with lots of headspace and a lid not sealing properly, the “So Far” was churning away in less than two hours after pitching. I had just started to sleep and the airlock was bubbling very vigorously. As that fermenter is in my bedroom, the noise woke me up. I loosened the lid on top of that bucket to make sure I wouldn’t get a spill. There wasn’t that much kräusen but fermentation was clearly vigorous, already. This morning, it smells this distinctive S-04 smell and has a good, thick kräusen.

The “Lo Five,” which I left in the basement, is also showing clear signs of fermentation. Thick kräusen, frequent bubbles, yeast smell… As it’s the first batch in which I use US-05 yeast, I didn’t know what to expect. The smell is actually fairly similar to the S-04 but less assertive. The fact that I’m using this yeast for the first time is also a reason I couldn’t attest to its fault tolerance. Judging from the smell, at least, I’d say that it’s as “robust” as S-04 and Ringwood but that it might still make for a cleaner profile which doesn’t hide small flaws really well.

My intention is to “drop” the fermenting beer away from the yeast pretty quickly on the “So Far” to intensify diacetyl. Can’t find the reference, but some British brewery is still doing this, with special equipment. Maybe it’s called “dumping” or “crashing.” Racking the beer early, the yeast isn’t able to “chew up” the diacetyl so more of it is left in the finished beer. Yeah, I know. Diacetyl isn’t typical of mild ales. But I tend to like some level of diacetyl in British-style beers. In this case, if the beer is complex enough despite its low ABV, a bit of diacetyl could round off the finished beer.

As is often the case in homebrewing, I’m already thinking about other batches I might want to do. One could be a doubled-up version of “So Far” (twice the grainbill, maybe twice the hops). Another would be a light weizen, brewed with Lallemand’s Munich strain.

It’s too much fun.

Brewing Mildly

[This is one of my geekier posts, here. As a creative generalist, I typically "write for a general audience." Whether or not I have an actual audience in mind, my default approach to blog writing is to write as generally as possible. But this post is about homebrewing. As these things go, it's much easier to write when you assume that "people know what you're talking about." In this case, some basic things about all-grain brewing at home. Not that I'm using that obscure a terminology, here. But it's a post which could leave some people behind, scratching their heads. If it's your case, sorry. But, you know, "it's my blog day and I'll geek if I want to." As for the verb tenses and reference to time, I'm writing much of this as I go along.]

So…

Generated a recipe for a Mild (11A) using BeerTools and posted it in their recipe library.

So Far (So Good)/Lo Five

That generated recipe is serving as the basis for two recipes I’m mashing right now (June 8, 2008). One, “So Far (So Good),” close to this generated one, is a single-step (infusion) mash with a simple grainbill, to be fermented with S-04 (so it’s “British style”). The other (“Lo Five”) is a multi-step mash with a more complex grainbill (added Carastan, Caramel 80, and chocolate). “Lo Five” is to be fermented with SS-05 (so it’s something of an “American style”).

I’ve copied the main details of this generated recipe in the standalone BeerTools Pro desktop application (version 1.5.9 beta, WinXP; also available on Mac OS X). I then tweaked that generated recipe a tiny bit to suit my needs for the “So Far.”

Here’s the version I used, before I started brewing:

So Far (So Good)

11-A Mild

BeerTools Pro Color Graphic

Size: 5,0 gal
Efficience: 75,0%
Atténuation: 75,0%
Calories: 114,99 kcal per 12,0 fl oz

Densité Initiale: 1,035 (1,030 – 1,038 )
|=================#==============|

Terminal Gravity: 1,009 (1,008 – 1,013)
|==========#=====================|

Couleur: 13,81 (12,0 – 25,0)
|==========#=====================|

Alcool: 3,41% (2,8% – 4,5%)
|=============#==================|

Amertume: 16,9 (10,0 – 25,0)
|===============#================|

Ingredients:

1,0 ea Fermentis S-04 Safale S-04
2.5 kg 6-Row Brewers Malt
150 g Brown Malt
150 g Vienna Malt
150 g Munich TYPE I
200 g Special B – Caramel malt
0.5 oz Challenger (8,0%) – added during boil, boiled 90 min
11,0 g Strisselspalt (3,3%) – added during boil, boiled 10 min

Schedule:

Air ambiant: 70,0 °F
Source Water: 130,0 °F
Altitude: 0,0 m

00:13:00 MashinEaud Empâtage: 1,91 gal; Strike: 173,56 °F; Target: 158,0 °F
01:33:00 Sacc 1Rest: 80 min; Final: 158,0 °F
02:13:00 Fly SpargeSparge Volume: 4,0 gal; Sparge Temperature: 168,0 °F; Runoff: 3,48 gal

Notes

Trying for a relatively simple mild. May skip the Strisselspalt. Doing two similar recipes.

Results generated by BeerTools Pro 1.5.9b

I then cloned that recipe and tweaked it a bit more to get my “Lo Five” recipe. Here’s the recipe I used before I started brewing:

Lo Five

11-A Mild

BeerTools Pro Color Graphic

Size: 5,0 gal
Efficience: 75,0%
Atténuation: 75,0%
Calories: 106,17 kcal per 12,0 fl oz

Densité Initiale: 1,032 (1,030 – 1,038 )
|============#===================|

Terminal Gravity: 1,008 (1,008 – 1,013)
|========#=======================|

Couleur: 17,05 (12,0 – 25,0)
|==============#=================|

Alcool: 3,15% (2,8% – 4,5%)
|===========#====================|

Amertume: 15,0 (10,0 – 25,0)
|=============#==================|

Ingredients:

1,0 ea Fermentis US-05 Safale US-05
2 kg 6-Row Brewers Malt
150 g Brown Malt
150 g Vienna Malt
150 g Munich TYPE I
200 g Special B – Caramel malt
105 g Light Carastan
125 g 2-Row Caramel Malt 80L
50 g 2-Row Chocolate Malt
0.5 oz Challenger (8,0%) – added during boil, boiled 90 min

Schedule:

Air ambiant: 70,0 °F
Source Water: 130,0 °F
Altitude: 0,0 m

00:03:00 MashinEaud Empâtage: 2,02 gal; Strike: 130,09 °F; Target: 122,0 °F
00:21:36 Ramp 1Heat: 18,6 min; Target: 150 °F
00:41:36 Sacc 1Rest: 20 min; Final: 150,0 °F
01:00:12 Ramp 2Heat: 18,6 min; Target: 158 °F
01:20:12 Sacc 2Rest: 20 min; Final: 158,0 °F
01:38:49 MashoutHeat: 18,6 min; Target: 170,0 °F
02:18:49 Fly SpargeSparge Volume: 3,72 gal; Sparge Temperature: 168,0 °F; Runoff: 3,23 gal

Notes

Trying for a relatively simple mild. May skip the Strisselspalt. Doing two similar recipes.

Results generated by BeerTools Pro 1.5.9b

On a whim (and because I just found out I had some), I switched the hops on the Lo Five to Crystal at 4.9% A.A. One half-ounce plug as first wort hopping, and another half-ounce pellet for the full boil. According to BeerTools Pro, t brings my bitterness level either below BJCP-sanctioned 10-25 IBUs for a Mild (11A) if I don’t add the boil time (FWH isn’t supposed to contribute much bitterness), or at two-thirds of the bitterness range if I add the full boil time.

The “brown malt” is actually some 6-row I roasted in a corn popper. The one in the “Lo Five” is darker (roasted longer) than the one in the “So Far.”

I’ve been having a hard time with the temperature for the “So Far.” I ended up doing a pseudo-decoction and adding some hot water to raise the temperature to something closer to even the low end of the optimal range for saccharification. This is the first batch I mash in a mashtun I got from friends in Austin. I used the strike temperature from the BeerTools Pro software (174F) but I hadn’t set the “heat capacity” and “heat transfer coefficient.” As I usually mash in my Bruheat, I rarely think about heat loss.

On the other hand, I largely overshot the strike temperature on the Lo Five. Two main reasons, AFAICT. One, the Bruheat I mashed the Lo Five in also served to preheat some sparge water, so it was still pretty hot. Second, the hot water from the sink was around 140F instead of 130F, as I had expected. In this case, overshooting the strike temperature wasn’t very problematic. The idea was to do a kind of protein rest, but that’s really not important, with the well-modified malts we all use.

Sparging the Lo Five’s mash was a real treat. Very smooth flow from HLT to MT to vessel. Plus, the smell of the Crystal hops in the first runnings was just fabulous. Because I “recirculate” during the mash, with my Bruheat, I didn’t have to recirculate, yet the runnings were quite clear. My sparge water was pretty much at the perfect temperature and I had just a bit extra sparge water (that I’m using in the So Far). I poured the liquid beneath the false bottom and it looked really nice. Rather clear and dark. After this, the grain bed was almost completely dry.

I did have to recirculate the So Far quite a bit. A good four litres, maybe even more. Still, it remains cloudier than most batches I’ve seen, possibly because some starches are remaining. I didn’t check conversion but I mashed long enough that I was assuming it was enough. Still, with a very low mash temperature, I may have needed an even longer mash. Actually, the mash is much cloudier than the runnings, which eventually became relatively clear.

May need to heat a bit of sparge water. Stopping the sparge in the meantime. A bit like a late mashout, it may help convert some of the remaining starch.

Oops! Was waiting for the Lo Five to boil. Thought it was taking a long time. Usually, the Bruheat gets to boiling pretty quickly. Eventually noticed that the element wasn’t running. The thermostat was still working (clicking sound when I reach the wort’s temperature) but I wasn’t hearing the sound of the element heating the wort. Unplugged the Bruheat, pressed the reset button, etc. Still wasn’t working. Was getting ready to try the clothes dryer to see if there was electricity coming through when I noticed it was in fact the dryer that I had plugged back, not the Bruheat.

Ah, well…

Ok…

One thing I found interesting is that when the wort was cooling off instead of heating up, the hop aroma wasn’t as pleasant as before. As the wort heated up, the pleasant profile from the Crystal came back as it was.

These are actually old hops, kept in a vacuum-sealed package. This specific package was a bit loose, as if the vacuum-seal hadn’t worked. I expected the hops to smell old. But they smelled really nice and fresh. Their colour is a bit off, but I trust their smell more than their colour.

Eventually got a rolling boil. Because of FWH, I didn’t skim the break material from the wort, which makes for a very different boil. In fact, when I added some of the runnings I had left on the side (to avoid a boilover), the effect was quite interesting.

Added back the rest of the runnings, waited to get a rolling boil again, then added the hops. Had to be careful not to get a boilover as the hops in the unskimmed wort created a lot of foam.

At the same time, I’m heating some sparge water for the So Far. Yes, once again. Guess I really under-evaluated how much sparge water I needed for this one. Strange.

It should be hot enough, now.

This time, I had let the top of the grain bed dry up a bit. This might not be so good. So I added enough water to cover the grain bed and I’ll wait a bit before I resume running off.

Overall, I’ve been much less careful with the “So Far” than with the “Lo Five.” My reasoning has to do with the fact that I perceive S-04 (Whitbread; PDF) to be a “stronger” yeast than the US-05 (PDF; aka US-56; the Sierra Nevada strain, apparently). For one thing, the optimal temperature range for the S-04 is somewhat higher than for the US-05: although Fermentis rates both at 15C to 24C, S-04 is known to sustain higher fermentation temperatures than most other strains (apart from some Belgian strains like Chouffe’s yeast). The flavour profile from S-04 also tends to be more estery than for the US-05, so it can increase the complexity of the finished beer and even cover up some small flaws. Plus, “Mighty S-04″ is one of those strains which can be (and has been) used in open fermentation and continually repitched. A bit like “famously robust” Ringwood yeast. So, unlike a lager strain, this is not a yeast strain that Peter McAuslan would likely call “wimpy.” The “strength” of this strength is obvious in the fact that it ferments very vigorously and quickly.

Besides, I have a slurry of S-04 (graciously donated by a friend) and only a rehydrated pack of US-05. With more yeast comes a certain safety.

Another whim: I added a plug of Crystal to the “Lo Five” about two minutes before the end of boil. Shouldn’t get any bitterness from this, may get some flavour and, quite likely, some nice hop aroma.

So I was somewhat careless with the “So Far.” Conversely, I was rather careful with the “Lo Five.” Not more than for the typical homebrew batch, but more than with the “So Far.” At every step, I started with the “Lo Five” and let the “So Far” wait for its turn, when I wasn’t too busy with the “Lo Five.” For instance, I only started boiling the “So Far” when the “Lo Five” had been pitched. I didn’t even rinse the Bruheat after transfering the “Lo Five,” so the “So Far” started heating up with some hops from the “Lo Five.”

What I expect as a difference between the two is that the “Lo Five” will be rather clean and crisp while the “So Far” will be a chewier and grainier beer with some fruit notes.

More specifically, I’d like the “Lo Five” to have a clearly delineated malt profile and a perceivable hoppiness. in both nose and flavour. Though I wasn’t very specific about trying to emulate it, I guess my inspiration for that one was Three FloydsMild, as brewed for Legends of Notre Dame. That one was one of my favourite beers, from one of my favourite breweries, served at one of my favourites places. I don’t think “Lo Five” will be anywhere as tasty as that beer, but I was probably aiming for that kind of profile.

Tasting the “Lo Five” wort once it was cool, I thought it was decidedly bitter. Given the fact that this beer may finish rather low, it might be unbalanced. Typically, unfermented wort is sweeter than the finished beer so I’m assuming the bitterness might intensify. What’s somewhat sad is that a Mild can’t really age so it’s not like I’ll be able to wait for the bitterness to smoothen out.

Ah, well… We’ll see.

On the other hand, I seem to have overshot my OG. Not by much, and I probably had a reading error. Given how well the sparge went, it’d make sense that I overshot my efficiency (I usually get 75%-78%). But BeerTools Pro is giving me an efficiency of 92% which is pretty much not possible on a homebrew scale without pulverizing the grain (and leeching lots of tannins). At any rate, if the actual OG is higher than expected, it might balance the beer a bit.

Yes, clearly there’s a problem with my thermometer.

Just finished cleaning up (2:36, June 9, 2008). When I took the OG on the “So Far,” the wort was barely lukewarm yet the thermometer was indicating 120F. Using this temperature for hydrometer correction, the OG for the “So Far” would be exactly the same as that for the “Lo Five” (which seemed cooler). That would mean an efficiency of 83% which is not impossible but kind of high. In fact, the volume in the primary seems to be more than 5 gallons so the efficiency would go through the roof.

I did skip the Strisselspalt but the “So Far” was run through the hops from the “Lo Five” at knock-off. It was boiled about an hour, instead of 90 minutes.

Pricing Applications for OS X iPhone

AppleInsider has a rumour about Apple trying to get developers to charge for applications they release on the AppStore for OS X iPhone devices.
As is often the case, some reactions are more interesting than the article.
Wanted to add a comment but I’m getting tired of sites which use their own authentication (instead of OpenID), so I thought I’d use Diigo to comment on the discussion. I’m sure other comments are being added "as we speak," but the conversation is veering off into trolling so I stopped.
As I read those comments, I kept thinking about DemiForce‘s Trism and about one of my own posts about no-cost software.
Other random notes about the AppStore.

  • If the store is built appropriately, it can give a lot of exposure to developers who may then capitalize on their work.
  • I’m still hoping that there will eventually be a way to have customized AppStores for universities and other institutions.
  • The AppStore process does exclude FLOSS, at least in principle.
  • It’s quite likely that some developers for OS X iPhone will also develop for OS X Leopard.
  • Some OS X iPhone applications are likely meant to accompany a service or a desktop application, say with synchronization.

So, commenting on the AppleInsider discussion…

  • tags: toblog

    • Interesting thread as a whole. The issue hasn’t been discussed extensively, AFAICT. – post by enkerli
    • added nuisance for iPod touch owners
      • Really? As a would-be touch owner, I don’t see how the app pricing would make a difference through the firmware pricing. – post by enkerli
    • Out of spite I would charge 1¢.
      • Testing micropayment? My guess Apple set a minimum. – post by enkerli
    • Free 7 day trial
      • Seems quite likely. Demiforce.com already announced a free demo (presumably w/o time limits). – post by enkerli
    • becoming only a cost center
      • Breaking even could be nice but Apple probably sees the AppStore as a selling point for its Touch devices. Also, developers on OSX iPhone can enhance the halo effect. – post by enkerli
    • Free apps imply "no" support.
      • Under certain conditions only. – post by enkerli
    • Apple promised the option of Free Apps.

      its part of my contract with them.

      • Expected but it’s good to see confirmation. – post by enkerli
    • I refuse to make costing apps at this point.
      • Thoughtfully put. – post by enkerli
    • There are TONS of FREE online games. We’re not talking about games with much complexity, but they’re still games.
      • Casual gaming makes a lot of sense on OSX iPhone. – post by enkerli
    • Another misleading article title. "Pushing" is not the same as "encouraging".
      • Agreed! The article doesn’t make it sound like the push is very aggressive and, even if it is, Apple can’t really coax developers into selling their apps if they don’t want to. – post by enkerli
    • clearly point to earnings as a metric
      • Not a bad point. But, hopefully, there are other ways to achieve this. – post by enkerli
    • Ahhhhh, the voice of reason. So refreshing
      • Agreed. But it’s not so unique. Just masked by some loud voices. – post by enkerli
    • you don’t need to charge a lot of money for the apps
      • Economies of scale should work well for some OSX iPhone apps. At the same time, there are other ways to make money that to charge for the app itself, especially in these days of online services. – post by enkerli
    • what about ad-supported apps?
      • Not a bad question. I actually hope there won’t be too much of those, but it’s likely that there will be some. It can be more subtle, using an app to lead people to a site. – post by enkerli
    • Spaz out much?
      • Snarky but respectful. Nice! – post by enkerli
    • It’s actually 30% of the REVENUE
      • Excellent point. – post by enkerli
    • in the long run, an App Store with lots of freeware will get more traffic
      • Interesting way to put it. OTOH, it’s probably not traffic that Apple’s cares the most about, for the AppStore. – post by enkerli
    • iTunes gets you to the iTunes Store.
      TextWrangler is really BBEdit Lite. It can be considered to be a gateway drug for BBEdit.
      Skype is a front-end to get you to buy some paid services.
      Sketch-up has an expensive paid version.
      • These are useful examples of the "economy of free" because they show how diverse no-cost software can be in business model. Of course, there are many other models based on no-cost software. – post by enkerli
    • My apps are free because they will be Christianity related and I don’t believe that anyone should be charged to get a bible in the medium they want.
      • It’s hard not to respect the argument and I appreciate the honesty. Also, because the apps aren’t forced on anyone, the position seems quite open. – post by enkerli
    • Given the quality of your writing
      • Feeding the troll doesn’t help. – post by enkerli

Waiting for Other Touch Devices?

Though I’m interpreting Apple’s current back-to-school special to imply that we might not see radically new iPod touch models until September, I’m still hoping that there will be a variety of touch devices available in the not-so-distant future, whether or not Apple makes them.

Turns out, the rumour mill has some items related to my wish, including this one:

AppleInsider | Larger Apple multi-touch devices move beyond prototype stage

This could be excellent news for the device category as a whole and for Apple itself. As explained before, I’m especially enthusiastic about touch devices in educational contexts.

I’ve been lusting over an iPod touch since it was announced. I sincerely think that an iPod touch will significantly enhance my life. As strange as it may sound, especially given the fact I’m no gadget freak, I think frequently about the iPod touch. Think Wayne, in Wayne’s World 2, going to a music store to try a guitar (and being denied the privilege to play Stairway to Heaven). That’s almost me and the iPod touch. When I go to an Apple Store, I spend precious minutes with a touch.

Given my current pattern of computer use, the fact that I have no access to a laptop at this point, and the availability of WiFi connections at some interesting spots, I think an iPod touch will enable me to spend much less time in front of this desktop, spend much more time outside, and focus on my general well-being.

One important feature the touch has, which can have a significant effect on my life, is instant-on. My desktop still takes minutes to wake up from “Stand by.” Several times during the day, the main reason I wake my desktop is to make sure I haven’t received important email messages. (I don’t have push email.) For a number of reasons, what starts out as simple email-checking frequently ends up being a more elaborate browsing session. An iPod touch would greatly reduce the need for those extended sessions and let me “do other things with my life.”

Another reason a touch would be important in my life at this point is that I no longer have access to a working MP3 player. While I don’t technically need any portable media player to be happy, getting my first iPod just a few years ago was an important change in my life. I’ll still miss my late iRiver‘s recording capabilities, but it’s now possible to get microphone input on the iPod touch. Eventually, the iPod touch could become a very attractive tool for fieldwork recordings. Or for podcasting. Given my audio orientation, a recording-capable iPod touch could be quite useful. Even more so than iPod Classic with recording capabilities.

There are a number of other things which should make the iPod touch very useful in my life. A set of them have to do with expected features and applications. One is Omni Group’s intention to release their OmniFocus task management software through the iPhone SDK. As an enthusiastic user of OmniOutliner for most of the time I’ve spent on Mac OS X laptops, I can just imagine how useful OmniFocus could be on an iPod touch. Getting Things Done, the handheld version. It could help me streamline my whole workflow, the way OO used to do. In other words: OF on an iPod touch could be this fieldworker’s dream come true.

There are also applications to be released for Apple’s Touch devices which may be less “utilitarian” but still quite exciting. Including the Trism game. In terms of both “appropriate use of the platform” and pricing, Trism scores high on my list. I see it as an excellent example of what casual gaming can be like. One practical aspect of casual gaming, especially on such a flexible device as the iPod touch, is that it can greatly decrease stress levels by giving users “something to do while they wait.” I’ve had that experience with other handhelds. Whether it’s riding the bus or waiting for a computer to wake up from stand by, having something to do with your hands makes the situation just a tad bit more pleasant.

I’m also expecting some new features to eventually be released through software, including some advanced podcatching features like wireless synchronization of podcasts and, one can dream, a way to interact directly with podcast content. Despite having been an avid podcast listener for years, I think podcasts aren’t nearly “interactive” enough. Software on a touch device could solve this. But that part is wishful thinking. I tend to do a lot of wishlists. Sometimes, my daydreams become realities.

The cool thing is, it looks as though I’ll be able to get my own touch device in the near future. w00t! :-D

Even if Apple does release new Touch devices, the device I’m most likely to get is an iPod touch. Chances are that I might be able to get a used 8MB touch for a decent price. Especially if, as is expected for next Monday, Apple officially announces the iPhone for Canada (possibly with a very attractive data plan) As a friend was telling me, once Canadians are able to get their hands on an iPhone directly in Canada, there’ll likely be a number of used iPod touches for sale. With a larger supply of used iPod touches and a presumably lower demand for the same, we ca
n expect a lower price.

Another reason I might get an iPod touch is that a friend of mine has been talking about helping me with this purchase. Though I feel a bit awkward about accepting this kind of help, I’m very enthusiastic at the prospect.

Watch this space for more on my touch life. ;-)

Edupunk Manifesto?

Noticed, just yesterday, that a number of unusual suspects of some online educational circles were using Edupunk as a way to identify a major movement toward openness in educational material. This video doesn’t “say it all” but it can help.

Changing Expectations

Like Lindsea, I wish more diverse voices were heard. Bakhtin FTW!

Unlike Lindsea, I don’t see it as mainly a generational thing or a “teacher vs. student” issue. In fact, I’m hoping that the social movements labelled by the term “edupunk” will move beyond those issues into a broader phenomenon.

The age/generation component is still interesting, to a Post-Buster like me. Baby Boomers are still the primary target of Punk. Lindsea even talks about Boomer classics:

Don’t you teachers remember when you were young? Hippies? Protesters? Implementers of change? Controllers of the cool, anti-establishment, nonconformist underground culture?

Baby Busters (the earlier part of the so-called “GenX”) have long been anti-Boomers. Not that everyone born during those years readily identify themselves with that “Generation.” But in terms of identity negotiation, the “Us/Them” often follows a concept of generational divide.

But I sincerely hope we can go way beyond age and generation. After all, there are learners of all ages, some of them older than their “teachers” (formally named or not).

Call me a teacher, if you really must. But, please, could we listen to diverse voices without labelling their sources?