Subdomains don't need to get created that often. There'd be an initial big push, but then 1 or 2 people managing the DNS could handle it easily and reasonably. A 24-48 hour turnaround seems manageable, given there is already an expectation that propagation can sometimes take a while.
We could also require that all subdomains be approved by GAs.
An online request form for subdomain requests would be a fairly straight forward thing.
A link to the GA minutes online would be required + contact info for requestor.
An IP to point the subdomain to.
I'll volunteer to work on this, if there is interest.
The are potential political issues, i.e.
Do we as occupations all want to be harmonized, standardized, etc?
Does the NY occupation want to restrict use of occupy.net
for thier services only? For federated services only?
I'm thinking foremost of the good it will do a bunch of small cities with urls like:
On Nov 8, 2011, at 3:28 PM, Clayton Dewey wrote:
using occupy.net for local occupations is a great idea because some jerk bought up a lot of the common occupy names and has put up some weird occupy political party stuff. very annoying!!
On Tue, Nov 8, 2011 at 1:07 PM, Devin Balkind <firstname.lastname@example.org>
Evy, point taken about the word "leaks." I won't use it anymore - I'll use the term "disclosures".
Andrew, we agree about the potential for occupy.net to host subdomains for occupations. I just requires a lot more organizing of developers.
On Tue, Nov 8, 2011 at 2:59 PM, Andrew Mallis <email@example.com>
just a thought, but occupy.net
as a base URL would seem to support occupation-specific subdomains quite well, i.e.
some cities have a hard time securing a short, logical domain name.
Ows_solutions mailing list