![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I am very silly for taking a couple of hours to realize that londo has left the house for a while and therefore I can move the A/C onto a setting that doesn't require me to be wearing my bathrobe in August.
12 August 2007
I am very silly for taking a couple of hours to realize that londo has left the house for a while and therefore I can move the A/C onto a setting that doesn't require me to be wearing my bathrobe in August.
This is going to be annoying to type with one hand because it is so long, but I'm going to anyway because it is so awesome. (I did look into Dasher, but it has a high learning curve. Making this a voice post would be too scattered to follow, too long for you all to listen and transcribe, and reference too many names for the auto-transcriber to do it. Basically, I'm gonna type.)
First off, a quick explanation. But if you just want to skip onto my great idea, you don't have to ( read this. )
If you didn't read the cut: this post is about a hypothetical event.
The problem is, the people who would be invited to a wedding I have are scattered. I have very important friends on the west coast, most of my relatives and more important friends in the center of the US, and of course my current home is here in Boston. Assuming nothing about whomever I end up having the wedding with, any place I decide to hold the event will cause a bunch of people a bunch of hassle. If I held it here, it's unlikely that people from the west coast would be able to make it, and neither would lots of friends from the Mid-West and many of my family members (including my elderly grandfather who doesn't fly.) It would be equally silly to hold a wedding in Oklahoma and exclude most of my life here in Boston. It's stupid to plan a whole wedding on the other coast where only a few (yet important!) people live, and the idea of holding it somewhere equally inopportune for all is hamstringing myself.
While washing dishes today and thinking about this, I pondered whether a road trip to visit the west-coasters could perhaps be the honeymoon. Suddenly, I had a flash of insight. Of course! A mobile wedding!
Why have one big party when a few smaller parties will do? The main part I want, anyway, is the reception. The vows don't have to be viewed by anyone but whomever is legally required. So combine the reception with the honeymoon and travel the states (or the world) having a reception in each part! One "wedding" here, with all the Boston and other east-coast folks. Then road trip to Oklahoma for the "wedding" there, featuring all the relatives and high school and college friends. Finally, road trip out to California for the final "wedding" with folk out there.
Bonuses of this plan:
* More assurance that people will be able to make the wedding, since seeing the people is what's important to me. Societal pressure can only get someone so far to attending their friend's wedding if they're on the wrong coast and not rolling in money.
* Multiple smaller parties should be about the same cost (and stress) as one huge one, yes? Especially since I don't give a damn about things like flowers, decorations, a fancy cake, and other things that often drive up the price. (Note: I've never actually thrown a wedding to know where the price comes from.)
* Instead of one expensive fancy bridal gown that will only get worn once, 3+ nice pretty party dresses that could feasibly be worn again somewhere!
* Ease in inviting internet friends.
* Instead of trying to spend quality time with all these old friends and family over the space of one day (or weekend), it's spread out to be able to spend time with all of them!
I am super excited about my great plan. It helps that I don't actually have to think about implementing it any time soon, just daydream about how well it would work. However, since problems are best solved early, let me know if there's something that would go horribly wrong that you see but I haven't. I would of course require on-site party planners, but I think I could get those. :)
First off, a quick explanation. But if you just want to skip onto my great idea, you don't have to ( read this. )
If you didn't read the cut: this post is about a hypothetical event.
The problem is, the people who would be invited to a wedding I have are scattered. I have very important friends on the west coast, most of my relatives and more important friends in the center of the US, and of course my current home is here in Boston. Assuming nothing about whomever I end up having the wedding with, any place I decide to hold the event will cause a bunch of people a bunch of hassle. If I held it here, it's unlikely that people from the west coast would be able to make it, and neither would lots of friends from the Mid-West and many of my family members (including my elderly grandfather who doesn't fly.) It would be equally silly to hold a wedding in Oklahoma and exclude most of my life here in Boston. It's stupid to plan a whole wedding on the other coast where only a few (yet important!) people live, and the idea of holding it somewhere equally inopportune for all is hamstringing myself.
While washing dishes today and thinking about this, I pondered whether a road trip to visit the west-coasters could perhaps be the honeymoon. Suddenly, I had a flash of insight. Of course! A mobile wedding!
Why have one big party when a few smaller parties will do? The main part I want, anyway, is the reception. The vows don't have to be viewed by anyone but whomever is legally required. So combine the reception with the honeymoon and travel the states (or the world) having a reception in each part! One "wedding" here, with all the Boston and other east-coast folks. Then road trip to Oklahoma for the "wedding" there, featuring all the relatives and high school and college friends. Finally, road trip out to California for the final "wedding" with folk out there.
Bonuses of this plan:
* More assurance that people will be able to make the wedding, since seeing the people is what's important to me. Societal pressure can only get someone so far to attending their friend's wedding if they're on the wrong coast and not rolling in money.
* Multiple smaller parties should be about the same cost (and stress) as one huge one, yes? Especially since I don't give a damn about things like flowers, decorations, a fancy cake, and other things that often drive up the price. (Note: I've never actually thrown a wedding to know where the price comes from.)
* Instead of one expensive fancy bridal gown that will only get worn once, 3+ nice pretty party dresses that could feasibly be worn again somewhere!
* Ease in inviting internet friends.
* Instead of trying to spend quality time with all these old friends and family over the space of one day (or weekend), it's spread out to be able to spend time with all of them!
I am super excited about my great plan. It helps that I don't actually have to think about implementing it any time soon, just daydream about how well it would work. However, since problems are best solved early, let me know if there's something that would go horribly wrong that you see but I haven't. I would of course require on-site party planners, but I think I could get those. :)
This is going to be annoying to type with one hand because it is so long, but I'm going to anyway because it is so awesome. (I did look into Dasher, but it has a high learning curve. Making this a voice post would be too scattered to follow, too long for you all to listen and transcribe, and reference too many names for the auto-transcriber to do it. Basically, I'm gonna type.)
First off, a quick explanation. But if you just want to skip onto my great idea, you don't have to ( read this. )
If you didn't read the cut: this post is about a hypothetical event.
The problem is, the people who would be invited to a wedding I have are scattered. I have very important friends on the west coast, most of my relatives and more important friends in the center of the US, and of course my current home is here in Boston. Assuming nothing about whomever I end up having the wedding with, any place I decide to hold the event will cause a bunch of people a bunch of hassle. If I held it here, it's unlikely that people from the west coast would be able to make it, and neither would lots of friends from the Mid-West and many of my family members (including my elderly grandfather who doesn't fly.) It would be equally silly to hold a wedding in Oklahoma and exclude most of my life here in Boston. It's stupid to plan a whole wedding on the other coast where only a few (yet important!) people live, and the idea of holding it somewhere equally inopportune for all is hamstringing myself.
While washing dishes today and thinking about this, I pondered whether a road trip to visit the west-coasters could perhaps be the honeymoon. Suddenly, I had a flash of insight. Of course! A mobile wedding!
Why have one big party when a few smaller parties will do? The main part I want, anyway, is the reception. The vows don't have to be viewed by anyone but whomever is legally required. So combine the reception with the honeymoon and travel the states (or the world) having a reception in each part! One "wedding" here, with all the Boston and other east-coast folks. Then road trip to Oklahoma for the "wedding" there, featuring all the relatives and high school and college friends. Finally, road trip out to California for the final "wedding" with folk out there.
Bonuses of this plan:
* More assurance that people will be able to make the wedding, since seeing the people is what's important to me. Societal pressure can only get someone so far to attending their friend's wedding if they're on the wrong coast and not rolling in money.
* Multiple smaller parties should be about the same cost (and stress) as one huge one, yes? Especially since I don't give a damn about things like flowers, decorations, a fancy cake, and other things that often drive up the price. (Note: I've never actually thrown a wedding to know where the price comes from.)
* Instead of one expensive fancy bridal gown that will only get worn once, 3+ nice pretty party dresses that could feasibly be worn again somewhere!
* Ease in inviting internet friends.
* Instead of trying to spend quality time with all these old friends and family over the space of one day (or weekend), it's spread out to be able to spend time with all of them!
I am super excited about my great plan. It helps that I don't actually have to think about implementing it any time soon, just daydream about how well it would work. However, since problems are best solved early, let me know if there's something that would go horribly wrong that you see but I haven't. I would of course require on-site party planners, but I think I could get those. :)
First off, a quick explanation. But if you just want to skip onto my great idea, you don't have to ( read this. )
If you didn't read the cut: this post is about a hypothetical event.
The problem is, the people who would be invited to a wedding I have are scattered. I have very important friends on the west coast, most of my relatives and more important friends in the center of the US, and of course my current home is here in Boston. Assuming nothing about whomever I end up having the wedding with, any place I decide to hold the event will cause a bunch of people a bunch of hassle. If I held it here, it's unlikely that people from the west coast would be able to make it, and neither would lots of friends from the Mid-West and many of my family members (including my elderly grandfather who doesn't fly.) It would be equally silly to hold a wedding in Oklahoma and exclude most of my life here in Boston. It's stupid to plan a whole wedding on the other coast where only a few (yet important!) people live, and the idea of holding it somewhere equally inopportune for all is hamstringing myself.
While washing dishes today and thinking about this, I pondered whether a road trip to visit the west-coasters could perhaps be the honeymoon. Suddenly, I had a flash of insight. Of course! A mobile wedding!
Why have one big party when a few smaller parties will do? The main part I want, anyway, is the reception. The vows don't have to be viewed by anyone but whomever is legally required. So combine the reception with the honeymoon and travel the states (or the world) having a reception in each part! One "wedding" here, with all the Boston and other east-coast folks. Then road trip to Oklahoma for the "wedding" there, featuring all the relatives and high school and college friends. Finally, road trip out to California for the final "wedding" with folk out there.
Bonuses of this plan:
* More assurance that people will be able to make the wedding, since seeing the people is what's important to me. Societal pressure can only get someone so far to attending their friend's wedding if they're on the wrong coast and not rolling in money.
* Multiple smaller parties should be about the same cost (and stress) as one huge one, yes? Especially since I don't give a damn about things like flowers, decorations, a fancy cake, and other things that often drive up the price. (Note: I've never actually thrown a wedding to know where the price comes from.)
* Instead of one expensive fancy bridal gown that will only get worn once, 3+ nice pretty party dresses that could feasibly be worn again somewhere!
* Ease in inviting internet friends.
* Instead of trying to spend quality time with all these old friends and family over the space of one day (or weekend), it's spread out to be able to spend time with all of them!
I am super excited about my great plan. It helps that I don't actually have to think about implementing it any time soon, just daydream about how well it would work. However, since problems are best solved early, let me know if there's something that would go horribly wrong that you see but I haven't. I would of course require on-site party planners, but I think I could get those. :)