Think of a good name for the obfs-flash meta-proxy and create a repo for it

added component::circumvention/pluggable transport in Legacy / Trac flashproxy in Legacy / Trac fog in Legacy / Trac owner::RushingWookie in Legacy / Trac priority::medium in Legacy / Trac resolution::fixed in Legacy / Trac status::closed in Legacy / Trac type::project in Legacy / Trac labels

P.S. George and I are not allowed to name software.

My recommendation for the new name is "Anima".

Trac:
Cc: asn, infinity0 to asn, infinity0, griffinboyce@gmail.com

metaproxy? metapt? metatransport? metasomething? meta is cool!

Replying to asn:

metaproxy? metapt? metatransport? metasomething? meta is cool!

Metapod. The rule is that all new transports have to be named after Pokémon.

Replying to dcf:

Metapod. The rule is that all new transports have to be named after Pokémon.

Ha but please no; I don't think Nintendo employs the kind of lawyers who have a sense of humor about that kind of thing. :)

To be mildly constructive, how about something derived from "metamer" -- it's one section of a plant or animal with a segmented body, which kind of describes the architecture you wind up with this thing.

http://en.wikipedia.org/wiki/Metamerism_(biology)

Also see http://en.wikipedia.org/wiki/Metamerism_(color)

It's also an old word for what chemists now call an "isomer".

I also like "metaphase" (a stage in mitosis), "metaphrase" (a word-by-word translation), "metaphyte" (multicellular plant), "metasome" (the hindmost body segment in a segmented animal), and "metazoon" (multicellular animal).

Replying to nickm:

Replying to dcf:

Metapod. The rule is that all new transports have to be named after Pokémon.

Ha but please no; I don't think Nintendo employs the kind of lawyers who have a sense of humor about that kind of thing. :)

Okay, nickm, you win. We'll call it Chainchomp.

EDIT: Actually I change my vote to Metallica.

metazord?

metamorphosis might also be suiting. it has both meta and it resembles obfuscationary situations! unfortunately it's too lengthy and it sounds like a black metal song name.

We can also name it 'fog' which stands for the function composition of 'f' and 'g' which is usually denoted as 'f o g' = f(g(x)). Fog is also quite obfuscationary. It hides things!

Or maybe we shouldn't name this at all, and just use the hash of the codebase as the identifier for each release. That should show the users that didn't like obfsproxy or flashproxy!

Replying to asn:

We can also name it 'fog' which stands for the function composition of 'f' and 'g' which is usually denoted as 'f o g' = f(g(x)). Fog is also quite obfuscationary. It hides things!

asn you're a genius.

"fog" is actually pretty brilliant.

Trac:
Cc: asn, infinity0, griffinboyce@gmail.com to asn, infinity0, griffinboyce@gmail.com, isis

metamorphosis is indeed too long, but metamorph is just the right length and gets a similar point across.

That said, fog has a lot going for it -- it sounds like one of those names that's actually a good name for things.

(I think I may not be allowed to name things either ;)

Trac:
Keywords: N/A deleted, pt-combiner added

assigning to our GSoC student :) You get to name a Tor product!

Once you've decided on a name, you can rename the program files (obfs-flash-{client,server}), update any old names in the other files (don't forget to the documentation), and rename your github repo. I'll then rename my own repo, and submit a bunch of more tickets to our sysadmins to do the same for our self-hosted repos.

Trac:
Owner: asn to RushingWookie
Status: new to assigned

Alright I'll start brainstorming

So far:

IncogniTor

Trac:
Username: RushingWookie

Replying to RushingWookie:

IncogniTor

Usually it's best to leave the substring "Tor" out of the name -- it confuses people into thinking that everybody should do it, and pretty soon nobody can tell which things were written by the Tor people and which things were written by other folks. And in some cases the line is blurry, so it's a habit I'd like to get people out of in general.

https://www.torproject.org/docs/trademark-faq

(Also, you don't like fog? :)