On Wed, Jan 15, 2014 at 5:30 PM, Runa A. Sandvik <runa.sandvik@gmail.com> wrote:
On Wed, Jan 15, 2014 at 3:08 PM, Kostas Jakeliunas
<kostas@jakeliunas.com> wrote:
> On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi all,
>>
>> I have set up an Amazon EC2 instance to run a Tor Relay, I chose
>> Obfsproxy Bridges.
>>
>> [...]
>>
>>
>> The second point is: I looked at the configuration, and noticed bridge
>> is set to 1.
>> I though it made the tor relay private, do I have miss-understood
>> something?
>> If I didn't miss-understand, that explains why it is still not listed
>> on atlas.torproject.org, and there is a problem with the provided EC2
>> image.
>
>
> If your bridge is set to publish its descriptor (should be default), you
> might be able to search for it using the new Globe tool:
> https://globe.torproject.org/

Good point! I forgot about Globe. It seems
https://globe.torproject.org/#/search/query=ec2 only lists 43
currently running bridges, while
https://metrics.torproject.org/cloudbridges.png lists more than 300.
Any idea why the numbers are so different?

I haven't checked, but can't the cloud bridge operator change the nickname (just as any other operator can)?

See e.g. https://globe.torproject.org/#/search/query=cloud (non-zero count of bridges there, too. Not sure if related, though.)