The Open Technology Initiative's Dispatches from the Digital Frontier blog originally published this story by Preston Rhea about his experience working with some neighbors to build their own wireless network in Mount Pleasant in Washington, DC. We hope it inspires others.

If you are not yet familiar with Mount Pleasant, here’s a chance to learn about one of DC’s most vibrant neighborhoods. It’s a diverse area not far from downtown DC, featuring a main street lined with locally-owned businesses. Many of these shops and restaurants are owned and run by the area’s large Latino community, which has long been central to shaping the neighborhood’s character. However, over the past decade rising housing prices have pushed many in the Latino community east towards Georgia Avenue.

In May, I moved to Mount Pleasant and started to learn about the area. In order to encourage community-building and local empowerment and to increase local information-sharing and opportunities for civic engagement, I decided to use skills and ideas garnered from my work at the Open Technology Initiative to organize a community wireless network. Despite my excitement to get started, I didn’t want to rush in without first connecting with the people, the histories, networks, skill sets, and local knowledge already present in the community.

My first step was technical: with the help of my OTI colleagues, I specified the hardware for the network and prepared the technology for installation. The first-stage plan was to install a few “nodes” (wireless access points) in order to establish the form and structure of the mesh network - open, interoperable, unfiltered, and decentralized. Then, at the Mount Pleasant Farmers Market, I handed out fliers directing people to an online survey gauging their interest in organizing a community wireless network in the neighborhood. I also posted a few of the fliers in local businesses on Mount Pleasant Street. But I needed to go deeper in order to really connect with the existing social networks of people and projects.

The Open Technology Initiative's Dispatches from the Digital Frontier blog originally published this story by Preston Rhea about his experience working with some neighbors to build their own wireless network in Mount Pleasant in Washington, DC. We hope it inspires others.

If you are not yet familiar with Mount Pleasant, here’s a chance to learn about one of DC’s most vibrant neighborhoods. It’s a diverse area not far from downtown DC, featuring a main street lined with locally-owned businesses. Many of these shops and restaurants are owned and run by the area’s large Latino community, which has long been central to shaping the neighborhood’s character. However, over the past decade rising housing prices have pushed many in the Latino community east towards Georgia Avenue.

In May, I moved to Mount Pleasant and started to learn about the area. In order to encourage community-building and local empowerment and to increase local information-sharing and opportunities for civic engagement, I decided to use skills and ideas garnered from my work at the Open Technology Initiative to organize a community wireless network. Despite my excitement to get started, I didn’t want to rush in without first connecting with the people, the histories, networks, skill sets, and local knowledge already present in the community.

My first step was technical: with the help of my OTI colleagues, I specified the hardware for the network and prepared the technology for installation. The first-stage plan was to install a few “nodes” (wireless access points) in order to establish the form and structure of the mesh network - open, interoperable, unfiltered, and decentralized. Then, at the Mount Pleasant Farmers Market, I handed out fliers directing people to an online survey gauging their interest in organizing a community wireless network in the neighborhood. I also posted a few of the fliers in local businesses on Mount Pleasant Street. But I needed to go deeper in order to really connect with the existing social networks of people and projects.

The Open Technology Initiative's Dispatches from the Digital Frontier blog originally published this story by Preston Rhea about his experience working with some neighbors to build their own wireless network in Mount Pleasant in Washington, DC. We hope it inspires others.

If you are not yet familiar with Mount Pleasant, here’s a chance to learn about one of DC’s most vibrant neighborhoods. It’s a diverse area not far from downtown DC, featuring a main street lined with locally-owned businesses. Many of these shops and restaurants are owned and run by the area’s large Latino community, which has long been central to shaping the neighborhood’s character. However, over the past decade rising housing prices have pushed many in the Latino community east towards Georgia Avenue.

In May, I moved to Mount Pleasant and started to learn about the area. In order to encourage community-building and local empowerment and to increase local information-sharing and opportunities for civic engagement, I decided to use skills and ideas garnered from my work at the Open Technology Initiative to organize a community wireless network. Despite my excitement to get started, I didn’t want to rush in without first connecting with the people, the histories, networks, skill sets, and local knowledge already present in the community.

My first step was technical: with the help of my OTI colleagues, I specified the hardware for the network and prepared the technology for installation. The first-stage plan was to install a few “nodes” (wireless access points) in order to establish the form and structure of the mesh network - open, interoperable, unfiltered, and decentralized. Then, at the Mount Pleasant Farmers Market, I handed out fliers directing people to an online survey gauging their interest in organizing a community wireless network in the neighborhood. I also posted a few of the fliers in local businesses on Mount Pleasant Street. But I needed to go deeper in order to really connect with the existing social networks of people and projects.

The Open Technology Initiative's Dispatches from the Digital Frontier blog originally published this story by Preston Rhea about his experience working with some neighbors to build their own wireless network in Mount Pleasant in Washington, DC. We hope it inspires others.

If you are not yet familiar with Mount Pleasant, here’s a chance to learn about one of DC’s most vibrant neighborhoods. It’s a diverse area not far from downtown DC, featuring a main street lined with locally-owned businesses. Many of these shops and restaurants are owned and run by the area’s large Latino community, which has long been central to shaping the neighborhood’s character. However, over the past decade rising housing prices have pushed many in the Latino community east towards Georgia Avenue.

In May, I moved to Mount Pleasant and started to learn about the area. In order to encourage community-building and local empowerment and to increase local information-sharing and opportunities for civic engagement, I decided to use skills and ideas garnered from my work at the Open Technology Initiative to organize a community wireless network. Despite my excitement to get started, I didn’t want to rush in without first connecting with the people, the histories, networks, skill sets, and local knowledge already present in the community.

My first step was technical: with the help of my OTI colleagues, I specified the hardware for the network and prepared the technology for installation. The first-stage plan was to install a few “nodes” (wireless access points) in order to establish the form and structure of the mesh network - open, interoperable, unfiltered, and decentralized. Then, at the Mount Pleasant Farmers Market, I handed out fliers directing people to an online survey gauging their interest in organizing a community wireless network in the neighborhood. I also posted a few of the fliers in local businesses on Mount Pleasant Street. But I needed to go deeper in order to really connect with the existing social networks of people and projects.

The Open Technology Initiative's Dispatches from the Digital Frontier blog originally published this story by Preston Rhea about his experience working with some neighbors to build their own wireless network in Mount Pleasant in Washington, DC. We hope it inspires others.

If you are not yet familiar with Mount Pleasant, here’s a chance to learn about one of DC’s most vibrant neighborhoods. It’s a diverse area not far from downtown DC, featuring a main street lined with locally-owned businesses. Many of these shops and restaurants are owned and run by the area’s large Latino community, which has long been central to shaping the neighborhood’s character. However, over the past decade rising housing prices have pushed many in the Latino community east towards Georgia Avenue.

In May, I moved to Mount Pleasant and started to learn about the area. In order to encourage community-building and local empowerment and to increase local information-sharing and opportunities for civic engagement, I decided to use skills and ideas garnered from my work at the Open Technology Initiative to organize a community wireless network. Despite my excitement to get started, I didn’t want to rush in without first connecting with the people, the histories, networks, skill sets, and local knowledge already present in the community.

My first step was technical: with the help of my OTI colleagues, I specified the hardware for the network and prepared the technology for installation. The first-stage plan was to install a few “nodes” (wireless access points) in order to establish the form and structure of the mesh network - open, interoperable, unfiltered, and decentralized. Then, at the Mount Pleasant Farmers Market, I handed out fliers directing people to an online survey gauging their interest in organizing a community wireless network in the neighborhood. I also posted a few of the fliers in local businesses on Mount Pleasant Street. But I needed to go deeper in order to really connect with the existing social networks of people and projects.

Local governments are often looking for low-risk options for expanding broadband access to residents and local businesses. There are not many. Seattle put some extra conduit in the ground as a part of a different project that was tearing up the streets but Comcast was the only provider interested. The problem with a haphazard program of putting conduit in the ground is that while it benefits existing providers, it does very little to help new entrants. And conduit is inherently limited -- only a few providers can benefit from it and when used up, there is no space for more providers. In short, more conduit may slightly improve the status quo but it does little to get us to a future where residents and local businesses have a variety of choices from service providers offering fast, reliable, and affordable access to the Internet. Smart conduit policy can lay the groundwork for lowering the cost of a community network, which can get us where we want to be. It may take time, but will create benefits far more rapidly than private providers will be building next-generation networks in most of our communities. John Brown, a friend from Albuquerque, New Mexico, has offered some tips for communities that want to develop smart conduit policies. Brown runs CityLink Telecommunications, an impressive privately owned, open access, FTTH network that connects residents, businesses, schools, muni buildings, etc. We tend not to support privately owned networks because for all the great work a companiy like CityLink Fiber does, one does not know who will own it in 5, 10, or 20 years. However, we recognize that CityLink Fiber is a far better partner for communities than the vast majority of companies in this space. The following comments are taken from an email he shared with me and is permitting me to republish. Direct quotes are indented and the rest is paraphrased. Not all conduit is created equal. A 2 inch pipe will be sufficient for perhaps 2 providers. If conduit does not have inter-duct, it is much harder for multiple providers to share it. Inter-duct creates channels within the conduit that allows a provider to pull its fiber cables through without disturbing other cables in the conduit.

Local governments are often looking for low-risk options for expanding broadband access to residents and local businesses. There are not many. Seattle put some extra conduit in the ground as a part of a different project that was tearing up the streets but Comcast was the only provider interested. The problem with a haphazard program of putting conduit in the ground is that while it benefits existing providers, it does very little to help new entrants. And conduit is inherently limited -- only a few providers can benefit from it and when used up, there is no space for more providers. In short, more conduit may slightly improve the status quo but it does little to get us to a future where residents and local businesses have a variety of choices from service providers offering fast, reliable, and affordable access to the Internet. Smart conduit policy can lay the groundwork for lowering the cost of a community network, which can get us where we want to be. It may take time, but will create benefits far more rapidly than private providers will be building next-generation networks in most of our communities. John Brown, a friend from Albuquerque, New Mexico, has offered some tips for communities that want to develop smart conduit policies. Brown runs CityLink Telecommunications, an impressive privately owned, open access, FTTH network that connects residents, businesses, schools, muni buildings, etc. We tend not to support privately owned networks because for all the great work a companiy like CityLink Fiber does, one does not know who will own it in 5, 10, or 20 years. However, we recognize that CityLink Fiber is a far better partner for communities than the vast majority of companies in this space. The following comments are taken from an email he shared with me and is permitting me to republish. Direct quotes are indented and the rest is paraphrased. Not all conduit is created equal. A 2 inch pipe will be sufficient for perhaps 2 providers. If conduit does not have inter-duct, it is much harder for multiple providers to share it. Inter-duct creates channels within the conduit that allows a provider to pull its fiber cables through without disturbing other cables in the conduit.

Local governments are often looking for low-risk options for expanding broadband access to residents and local businesses. There are not many. Seattle put some extra conduit in the ground as a part of a different project that was tearing up the streets but Comcast was the only provider interested. The problem with a haphazard program of putting conduit in the ground is that while it benefits existing providers, it does very little to help new entrants. And conduit is inherently limited -- only a few providers can benefit from it and when used up, there is no space for more providers. In short, more conduit may slightly improve the status quo but it does little to get us to a future where residents and local businesses have a variety of choices from service providers offering fast, reliable, and affordable access to the Internet. Smart conduit policy can lay the groundwork for lowering the cost of a community network, which can get us where we want to be. It may take time, but will create benefits far more rapidly than private providers will be building next-generation networks in most of our communities. John Brown, a friend from Albuquerque, New Mexico, has offered some tips for communities that want to develop smart conduit policies. Brown runs CityLink Telecommunications, an impressive privately owned, open access, FTTH network that connects residents, businesses, schools, muni buildings, etc. We tend not to support privately owned networks because for all the great work a companiy like CityLink Fiber does, one does not know who will own it in 5, 10, or 20 years. However, we recognize that CityLink Fiber is a far better partner for communities than the vast majority of companies in this space. The following comments are taken from an email he shared with me and is permitting me to republish. Direct quotes are indented and the rest is paraphrased. Not all conduit is created equal. A 2 inch pipe will be sufficient for perhaps 2 providers. If conduit does not have inter-duct, it is much harder for multiple providers to share it. Inter-duct creates channels within the conduit that allows a provider to pull its fiber cables through without disturbing other cables in the conduit.