Blogging will likely be light for a few days or even weeks. Sigh.
My laptop died. Specifically, "Internal hard disk drive not found."
It's not as bad as it could be, for a few reasons. First, it's the university's computer, so I am not responsible for the troubleshooting, rebuilding, and/or replacement that might be deemed necessary. In fact, the machine is already on its way to its destination (whatever that may be).
Second, Facebook saved my life. Saturday night, as I was shutting down for the evening, I opened a tab that was already on facebook, and noticed that someone on my feed posted the end of a long day recovering their data from a virus-infected computer. "hmmm," I thought. "I haven't backed up in ages, and I've written a LOT of new material in the last weeks." So I popped in my data key, and downloaded the contents of My Docs. And went to bed.
The next morning, when I awoke, the computer had tried to reboot, and failed. A clicking sound emanated from the hard-drive side of the machine, and the black screen of death (apparently worse than its blue cousin) taunted me. It was 6:30 and I was on baby duty while everyone else slept. Junebug was kind enough to let me check to make sure that the data on the key was ok, and it was, so my early morning panic was mitigated.
What I don't have backed up: A few somewhat important documents that were only on the desktop (my to do list/calendar, and the zero draft document for freewriting and brainstorming the book project), my large library of PDFs which had not been backed up recently, my email archives older than 6 months, and my iTunes, which is mostly still safe on my actual iPod. So the losses, if they are irretrievable, are not earth-shattering.
But the timing, with the book project running just a little behind schedule, the semester starting in two weeks, and my annual report due at the end of the month, could've been better. Today, which should've been a writing day, has been a day of sending the laptop off to OIT, of checking my files to see what I do have, and have lost, and of a belated freaking out, which is better now. I'm working on Willow's netbook, which is tiny and slow, but adequate, so I have some access, but I feel electronically homeless, or at least itinerant, for now, and that will mean that some of my goals are just going to have to change. We'll see how it goes.
If the purpose of art is the same as the purpose of teaching, is teaching therefore an art?
Monday, August 09, 2010
Saturday, August 07, 2010
Flying Solo
Long-time readers of this space surely know that I harbor an interest in performances of white masculinity (particularly middle class, hetero, white masculinity) in American culture, specifically how bourgeois men perform when they think they are being watched in specific ways.
So having posted about academic masculinities, and masculine performances in the gym and the locker room, I hadn't touched the subject here in a while, though I think about it constantly, as this is a campus that takes its particularly masculine (but sometimes female) mascot very seriously.
But wandering through airports for large chunks of the previous three days sparked an observation that I think is worth pondering a bit: Airports are the perfect place to observe bourgeois masculinity.
First off, airports are full of men traveling alone, often on business. There seem to be fewer women traveling on their own, and it seems that women more often have traveling companions. And for reasons I'll suggest a bit below, the women who do travel alone are frequently not responding in this particular way to these circumstances, because....
Men traveling alone have virtually nothing at stake in airports--that is, if we taken as a tenuous given that much of the way that white middle class hetero men style themselves for public is a play for, and display of, power. Posture, gait, vocal inflection, clothing, even facial expression, are all finely tuned mechanisms for negotiating social empowerment. But because men flying solo are surrounded by people they don't know, with virtually every logistical arrangement already in place, their behaviors mean almost nothing is at stake. Aside from making it onto the flight or not, the hours preceding boarding for the single man are virtually consequenceless, at least based on the kinds of micro-behaviors that we so carefully modulate otherwise.
And yet, at the same time, these men are completely out of context, which means that there are no other clues to their behaviors: the observer of such figures has nothing to go on except for the man himself, which means that the things we might observe about them individually, guess about them, hypothesize about them, can only be discerned from, well, the text itself. If there is a new critical cultural studies--the text and nothing but the text--this is the place for it.
One might imagine, then, that without context and without stakes, single men in airports exist in their pure, true state. With nothing to gain or lose, and no meaningful context with which to interact, men and their behaviors can teach us loads about a whole (quite powerful) swath of our culture, and presumably, about individual men as well.
What's interesting, though, is that if this is the case, if the single male traveler waiting at the gate has nothing impinging on his performance of masculinity, he, well, kind of stops performing. In short, outside of its cultural-rhetorical negotiations, masculinity stops functioning, and given these conditions, many men stop functioning in any meaningful way as well. This is not to say that there is no there there, that such men lack interiority (after all, I devised this theory in precisely these conditions). But rather, there's nothing for them to do. Look around the waiting area; so many of these guys look completely adrift. Tired, frequently, and uncomfortable largely, but with nothing to do but wait, their faces are largely blank, and their postures are largely slouching, limp.
We could read this a few ways: Robert Bly once might have said that this was clearly evidence that modern society had robbed men of their true natural habitat, and we need to go beat some drums. perhaps. I choose to read this as the absence of a kind of a priori masculinity that burns within the bodies and souls of individual men. More usefully, I think, this suggests the deeply mythical nature of the importance of the self-sufficient male subject as an ideal. For without social maneuvering and negotiation to engage in, airport guy (I probably should have named him earlier. Mitch, maybe), Mitch has nothing to do, no purpose.
But watch him as his cell phone rings, and a switch flips, and his whole posture changes. Cancel Mitch's flight, and the whole army of Mitches go into hyperdrive, with a range of tactics, approaches, strategies in play to find a new flight, to negotiate a better situation (mine was to wait out the loonies and then flatter and empathise with the harried attendant, who seemed to be nicer to me for my comparative kindness to him).
Why masculinity in particular? Because my sense is that while men in such situations are prone to seeing no function for themselves, women are largely conditioned to a) be more aware of themselves as objects of the gaze in such situations, in ways that men are not, and b) bored men with a sense of consequencelessness are dangerous. So while Mitch might really be letting his guard down, the female business traveler across the aisle must remain wary.
The point is, what Mitch at the airport tells me is that masculinity is more than anything a social code, precisely the opposite of the facade of solitary sufficiency that it seeks to project; that the behaviors of real men--especially in a white, hetero, bourgeois context--demonstrate not that men are islands, but that their very function exists in building better bridges.
So having posted about academic masculinities, and masculine performances in the gym and the locker room, I hadn't touched the subject here in a while, though I think about it constantly, as this is a campus that takes its particularly masculine (but sometimes female) mascot very seriously.
But wandering through airports for large chunks of the previous three days sparked an observation that I think is worth pondering a bit: Airports are the perfect place to observe bourgeois masculinity.
First off, airports are full of men traveling alone, often on business. There seem to be fewer women traveling on their own, and it seems that women more often have traveling companions. And for reasons I'll suggest a bit below, the women who do travel alone are frequently not responding in this particular way to these circumstances, because....
Men traveling alone have virtually nothing at stake in airports--that is, if we taken as a tenuous given that much of the way that white middle class hetero men style themselves for public is a play for, and display of, power. Posture, gait, vocal inflection, clothing, even facial expression, are all finely tuned mechanisms for negotiating social empowerment. But because men flying solo are surrounded by people they don't know, with virtually every logistical arrangement already in place, their behaviors mean almost nothing is at stake. Aside from making it onto the flight or not, the hours preceding boarding for the single man are virtually consequenceless, at least based on the kinds of micro-behaviors that we so carefully modulate otherwise.
And yet, at the same time, these men are completely out of context, which means that there are no other clues to their behaviors: the observer of such figures has nothing to go on except for the man himself, which means that the things we might observe about them individually, guess about them, hypothesize about them, can only be discerned from, well, the text itself. If there is a new critical cultural studies--the text and nothing but the text--this is the place for it.
One might imagine, then, that without context and without stakes, single men in airports exist in their pure, true state. With nothing to gain or lose, and no meaningful context with which to interact, men and their behaviors can teach us loads about a whole (quite powerful) swath of our culture, and presumably, about individual men as well.
What's interesting, though, is that if this is the case, if the single male traveler waiting at the gate has nothing impinging on his performance of masculinity, he, well, kind of stops performing. In short, outside of its cultural-rhetorical negotiations, masculinity stops functioning, and given these conditions, many men stop functioning in any meaningful way as well. This is not to say that there is no there there, that such men lack interiority (after all, I devised this theory in precisely these conditions). But rather, there's nothing for them to do. Look around the waiting area; so many of these guys look completely adrift. Tired, frequently, and uncomfortable largely, but with nothing to do but wait, their faces are largely blank, and their postures are largely slouching, limp.
We could read this a few ways: Robert Bly once might have said that this was clearly evidence that modern society had robbed men of their true natural habitat, and we need to go beat some drums. perhaps. I choose to read this as the absence of a kind of a priori masculinity that burns within the bodies and souls of individual men. More usefully, I think, this suggests the deeply mythical nature of the importance of the self-sufficient male subject as an ideal. For without social maneuvering and negotiation to engage in, airport guy (I probably should have named him earlier. Mitch, maybe), Mitch has nothing to do, no purpose.
But watch him as his cell phone rings, and a switch flips, and his whole posture changes. Cancel Mitch's flight, and the whole army of Mitches go into hyperdrive, with a range of tactics, approaches, strategies in play to find a new flight, to negotiate a better situation (mine was to wait out the loonies and then flatter and empathise with the harried attendant, who seemed to be nicer to me for my comparative kindness to him).
Why masculinity in particular? Because my sense is that while men in such situations are prone to seeing no function for themselves, women are largely conditioned to a) be more aware of themselves as objects of the gaze in such situations, in ways that men are not, and b) bored men with a sense of consequencelessness are dangerous. So while Mitch might really be letting his guard down, the female business traveler across the aisle must remain wary.
The point is, what Mitch at the airport tells me is that masculinity is more than anything a social code, precisely the opposite of the facade of solitary sufficiency that it seeks to project; that the behaviors of real men--especially in a white, hetero, bourgeois context--demonstrate not that men are islands, but that their very function exists in building better bridges.
Friday, August 06, 2010
What I did with my 36-hour research trip (that took 55 hours)
So on Wednesday morning, I hopped a flight to NYC for a brief research trip, mostly to look at the files that an Off-Broadway company kept on a play they had commissioned in the late 90s that has only very recently been published, and now will get the treatment in the book. In fact, I'm close enough to that part of the ms. revision (ch 6) that I hope to get all of this trip's fruits incorporated into the prose by the end of the month.
But the actual archive time was very brief: only about three hours. There wasn't too much of interest (though precisely what I needed), I was allowed to make photocopies, and they had me set up in the front lobby of their small admin offices, so I felt a bit intrusive (though they assured me I wasn't). At any rate, that left me enough time to do the following things (keeping in mind I was on a very tight budget and was lugging around my only bag w/ books and laptop the whole time).
Read two very different but wonderful novels: Sarah Shun-Lien Bynum's Ms. Hempel Chronicles which is very different from her amazing previous novel is still lovely and affecting, and which I polished off in its entirety on Wednesday; also, David Markson's Wittgenstein's Mistress, which like the other work of his I've read, This is not a Novel, is brilliantly cerebral, remarkably propulsive, and despite being barely narrative at all, still manages to tell an incredible, mysterious story.
Also: got lost behind Lincoln Center, sweated through two shirts, took a break from 95 degree heat in Central Park, took a lovely dinner with my friend Sue in the Village, lounged around the Columbia campus for a while, noticed how disproportionate were the hands and feet of The Thinker, looked for Fornes plays at the 66th St. Barnes and Noble, failed to enjoy several cab rides, and spent more time than I'd like in airports.
The last thing was an unwelcome cap on a nice little trip: Because it was so hot yesterday and I was so tired, I headed off to the airport at 3 for a 7:30 flight. It was air conditioned, it was free, and there was wi-fi (not free). Except that my flight was canceled. Fortunately, my friend Sue had room on her sofa for a visitor, and at 5:00 am, I woke up to try again, and finally made my way home (the extra airport time facilitating the completion of the Markson novel).
So, good trip, a little longer than expected. Lots of reading (two novels and multiple drafts of a play, plus a couple of academic articles and a bunch of supplementary materials), and some good research.
And remind me to do that post about men flying alone. A veritable sociological study there.
But the actual archive time was very brief: only about three hours. There wasn't too much of interest (though precisely what I needed), I was allowed to make photocopies, and they had me set up in the front lobby of their small admin offices, so I felt a bit intrusive (though they assured me I wasn't). At any rate, that left me enough time to do the following things (keeping in mind I was on a very tight budget and was lugging around my only bag w/ books and laptop the whole time).
Read two very different but wonderful novels: Sarah Shun-Lien Bynum's Ms. Hempel Chronicles which is very different from her amazing previous novel is still lovely and affecting, and which I polished off in its entirety on Wednesday; also, David Markson's Wittgenstein's Mistress, which like the other work of his I've read, This is not a Novel, is brilliantly cerebral, remarkably propulsive, and despite being barely narrative at all, still manages to tell an incredible, mysterious story.
Also: got lost behind Lincoln Center, sweated through two shirts, took a break from 95 degree heat in Central Park, took a lovely dinner with my friend Sue in the Village, lounged around the Columbia campus for a while, noticed how disproportionate were the hands and feet of The Thinker, looked for Fornes plays at the 66th St. Barnes and Noble, failed to enjoy several cab rides, and spent more time than I'd like in airports.
The last thing was an unwelcome cap on a nice little trip: Because it was so hot yesterday and I was so tired, I headed off to the airport at 3 for a 7:30 flight. It was air conditioned, it was free, and there was wi-fi (not free). Except that my flight was canceled. Fortunately, my friend Sue had room on her sofa for a visitor, and at 5:00 am, I woke up to try again, and finally made my way home (the extra airport time facilitating the completion of the Markson novel).
So, good trip, a little longer than expected. Lots of reading (two novels and multiple drafts of a play, plus a couple of academic articles and a bunch of supplementary materials), and some good research.
And remind me to do that post about men flying alone. A veritable sociological study there.
Thursday, July 29, 2010
Making an intervention
My strength as a writer and as a theorist has typically been in the form of synthesis, bringing together ideas that haven't been considered together, or that have been previously regarded as incompatible. Indeed, the bulk of this book project has been work on the latter: considering alongside one another essentialist and constructivist notions of the individual subject on the feminist stage. That in itself is a critical intervention, but one that is characterized by an attempt at critical harmony rather than dissensus.
The current chapter, however, is one in which I am actively refuting a major critical commonplace, not just on the criticism of one text, but on how we read a whole body of texts. And this is a big one, too. When I presented an early version of this argument recently, the response was measured, and in conversation about the idea, one similarly early-career scholar said only, cryptically, "Oh...Bold." The insinuation there was, "Oh...mind-blowingly stupid and wrong-headed." On the other hand, the reader who reviewed the book proposal and sample chapters felt that this particular argument was "nothing short of brilliant" which is overstatement, I think, but good to hear.
At any rate, while I'm committed to this argument, and find it both logical, compelling, and important to make, I am made anxious about the argumentative strategy. Actually refuting "critical orthodoxies" and "post-structuralist dogma" feels, well, not my style. On the one hand, it feels rhetorically like the kind of thing that overconfident first-year grad students do with concepts they haven't entirely grasped, and so in that way, it feels brash. On the other, it feels like the thing that I should be doing, by making an actual intervention in the discussion, making a real, contestable argument rather than playing the critical peacemaker.
I imagine that in fact much of my writing career will be filling that critical peacemaker role--synthesis has always been my intellectual forte, and frankly, it's what I do in interpersonal relationships, too (ENFJ's are harmony seekers, so the Meyers-Briggs test says). But in this chapter, I'm doing things I haven't done well before: stake out a claim, refute the conventional wisdom, and make some noise.
And honestly, it's making me nervous.
The current chapter, however, is one in which I am actively refuting a major critical commonplace, not just on the criticism of one text, but on how we read a whole body of texts. And this is a big one, too. When I presented an early version of this argument recently, the response was measured, and in conversation about the idea, one similarly early-career scholar said only, cryptically, "Oh...Bold." The insinuation there was, "Oh...mind-blowingly stupid and wrong-headed." On the other hand, the reader who reviewed the book proposal and sample chapters felt that this particular argument was "nothing short of brilliant" which is overstatement, I think, but good to hear.
At any rate, while I'm committed to this argument, and find it both logical, compelling, and important to make, I am made anxious about the argumentative strategy. Actually refuting "critical orthodoxies" and "post-structuralist dogma" feels, well, not my style. On the one hand, it feels rhetorically like the kind of thing that overconfident first-year grad students do with concepts they haven't entirely grasped, and so in that way, it feels brash. On the other, it feels like the thing that I should be doing, by making an actual intervention in the discussion, making a real, contestable argument rather than playing the critical peacemaker.
I imagine that in fact much of my writing career will be filling that critical peacemaker role--synthesis has always been my intellectual forte, and frankly, it's what I do in interpersonal relationships, too (ENFJ's are harmony seekers, so the Meyers-Briggs test says). But in this chapter, I'm doing things I haven't done well before: stake out a claim, refute the conventional wisdom, and make some noise.
And honestly, it's making me nervous.
Wednesday, July 14, 2010
Writing!
I know, I'm a bit of a one-note blog these days, in part because I'm often writing here as a "cool down" from other writing sessions--it's something of a rewards for writing, rather than a warm-up. Anyway, as you can see from the writing progress bar, pages are shifting from the unwritten italics count over to the red revised count. The key accomplishment is that I've completed a draft of chapter 3, which was, frankly, the most terrifying part of the whole process at summer's start. And now, that shift should continue in dramatic fashion over the next couple of days, as the 20 pages of drafted material in chapters 2 and 3 should be pounded out by next Monday.
Between now and then, and soon after, some other concerns will intervene. We're sending the twins on a weeklong vacation with my folks, which will on the one hand free up some time otherwise devoted to parenting, but will also require trips to and from the ancestral home to drop them off this Friday, and pick them up the following Saturday (any DC folks interested in getting together Friday night?). Then Junebug's beloved godmother is coming in for a visit, which will still allow for writing time, but also provides opportunities for distraction.
Also, I have a book review deadline on August 1, and a very short research trip to NYC on August 4 and 5, so my hope is to do all of those things, and come back to chapter 4 (if I haven't started it already) when I return. At that point it's only 2 more weeks until the semester starts, and so I hope to at least have chapter 4 drafted by then, with only Chapters 6, 7, and the conclusion to polish off in August and September. It wasn't my ideal schedule for the beginning of the summer, but I think it's still doable.
So yes. Writing! it goes.
Between now and then, and soon after, some other concerns will intervene. We're sending the twins on a weeklong vacation with my folks, which will on the one hand free up some time otherwise devoted to parenting, but will also require trips to and from the ancestral home to drop them off this Friday, and pick them up the following Saturday (any DC folks interested in getting together Friday night?). Then Junebug's beloved godmother is coming in for a visit, which will still allow for writing time, but also provides opportunities for distraction.
Also, I have a book review deadline on August 1, and a very short research trip to NYC on August 4 and 5, so my hope is to do all of those things, and come back to chapter 4 (if I haven't started it already) when I return. At that point it's only 2 more weeks until the semester starts, and so I hope to at least have chapter 4 drafted by then, with only Chapters 6, 7, and the conclusion to polish off in August and September. It wasn't my ideal schedule for the beginning of the summer, but I think it's still doable.
So yes. Writing! it goes.
Thursday, July 08, 2010
Headway
I have read, written and revised for two days in a row now, largely working on the chapter whose argument itself needed the most overhauling (Chapter 3, or Section1 chapter 2, depending on how you're counting). I at once feel pretty good about the work I'm doing, even as I cringe at some of the prose I wrote on the subject when I first drafted it. This chapter itself was written in the final throes of dissertation revision (7 years ago, now), and are at once naively composed and wildly out of date. Some of the central argument and most of the close readings remain valid, but damn, so of the phrases written there sound, frankly, like a 1975 consciousness-raising tract. Revision is indeed good.
Speaking of, I've drawn up a revision tracker over there on the right, which shows how much is revised and current, how much is drafted but needs revision, and how much I expect to draft from scratch. According to that, as of yesterday, I had about 105 pages of updated prose, another 75 that will need some kind of revision and polishing, and about 70 left to write from scratch for a goal of roughly 250 pages or 8000-9000 words. So watch me as I write, and I'll try to update that occasionally and at periodic intervals, post tallies at the bottom. Fingers crossed!
Speaking of, I've drawn up a revision tracker over there on the right, which shows how much is revised and current, how much is drafted but needs revision, and how much I expect to draft from scratch. According to that, as of yesterday, I had about 105 pages of updated prose, another 75 that will need some kind of revision and polishing, and about 70 left to write from scratch for a goal of roughly 250 pages or 8000-9000 words. So watch me as I write, and I'll try to update that occasionally and at periodic intervals, post tallies at the bottom. Fingers crossed!
Tuesday, July 06, 2010
Ready, Steady, Go!
Three processes resume today:
1) Writing: The summer course now done, grades submitted, and comments returned, the time has not come to write. After a tiny anxiety attack this morning (so distracted by it was I, that I sideswiped a mailbox after dropping off the kids. The mailbox is fine, but the side mirror on my car less so), I did some warm up writing on my tenure documents, and sat down with the book chapter du jour. Chapter 1.2 (or chapter 3, depending how you count) actually requires less work than I had imagined, mostly in the form of bulking up the theoretical grounding and stakes, and adding a major final section at the end to account for an extremely important new direction in both performance and in scholarship, that will make this section much more than a retread of existing scholarship or a retread of the dissertation chapter. This is significant work, to be sure, but less involved than, say, rebuilding the chapter from the ground up that I thought I'd have to do. Instead of writing a 35-page chapter with a handful of usable paragraphs, I've actually got to write 15 new pages to accompany the 25 I must revise and expand. Very doable. Moreover, I began the process of polishing up some of those older pages, and identifying a handful of sources to supplement the writing. I'll pick those up this afternoon on a trip to the library with Junebug.
2) Tenure: My external evaluators for tenure have been determined and confirmed, which means that today I am sending out the packet of my published work with a cover letter to frame it. Our department does not require the book for tenure, but in creating the narrative of my scholarly project, I have come to realize that the subject matter of the book forms a center to my work around which other material constellates. Since earlier articles published before I arrived do not count for my tenure case (something I understand is somewhat unique to this institution), but came from the dissertation-turned-book-project there appears to be a large absence that would otherwise tie my work together. I have tried to frame the existing publications within a narrative suggests that they cluster around this bigger project descried under future work, but I sure don't want evaluators to say, "well if only he had that book!" This is my only serious worry about the tenure process, and submitting these packets today (the other thing to do on my trip to campus with Junebug) is the great leap that the tenure process will entail for me. Everything else seems by comparison like bureaucracy.
3) Other great leaps into the unknown: Junebug took two very tiny, very tentative steps this weekend. He will walk all over the place either holding onto a single hand or cruising along the furniture, so full-on speed-walking is mere days away. I tremble. The coming weeks will be an adventure indeed.
1) Writing: The summer course now done, grades submitted, and comments returned, the time has not come to write. After a tiny anxiety attack this morning (so distracted by it was I, that I sideswiped a mailbox after dropping off the kids. The mailbox is fine, but the side mirror on my car less so), I did some warm up writing on my tenure documents, and sat down with the book chapter du jour. Chapter 1.2 (or chapter 3, depending how you count) actually requires less work than I had imagined, mostly in the form of bulking up the theoretical grounding and stakes, and adding a major final section at the end to account for an extremely important new direction in both performance and in scholarship, that will make this section much more than a retread of existing scholarship or a retread of the dissertation chapter. This is significant work, to be sure, but less involved than, say, rebuilding the chapter from the ground up that I thought I'd have to do. Instead of writing a 35-page chapter with a handful of usable paragraphs, I've actually got to write 15 new pages to accompany the 25 I must revise and expand. Very doable. Moreover, I began the process of polishing up some of those older pages, and identifying a handful of sources to supplement the writing. I'll pick those up this afternoon on a trip to the library with Junebug.
2) Tenure: My external evaluators for tenure have been determined and confirmed, which means that today I am sending out the packet of my published work with a cover letter to frame it. Our department does not require the book for tenure, but in creating the narrative of my scholarly project, I have come to realize that the subject matter of the book forms a center to my work around which other material constellates. Since earlier articles published before I arrived do not count for my tenure case (something I understand is somewhat unique to this institution), but came from the dissertation-turned-book-project there appears to be a large absence that would otherwise tie my work together. I have tried to frame the existing publications within a narrative suggests that they cluster around this bigger project descried under future work, but I sure don't want evaluators to say, "well if only he had that book!" This is my only serious worry about the tenure process, and submitting these packets today (the other thing to do on my trip to campus with Junebug) is the great leap that the tenure process will entail for me. Everything else seems by comparison like bureaucracy.
3) Other great leaps into the unknown: Junebug took two very tiny, very tentative steps this weekend. He will walk all over the place either holding onto a single hand or cruising along the furniture, so full-on speed-walking is mere days away. I tremble. The coming weeks will be an adventure indeed.
Taxonomy:
munchkins,
tenure,
Writing/ Presenting/ Editing/ Publishing
Subscribe to:
Posts (Atom)