profiles without public full name don't get delivered by the api

[GoogleCodeExporter]

there is an option on the profile page "Display my full name so I can
be found in search (also required to use Google Buzz and Latitude)".
in my opinion disabling this option prevents my profile from being
found on google or the api with my full name.
additionally the name shouldn't be displayed on the profile.
but surprisingly the profile completely isn't available through the
api anymore, even if it's requested with the correct profile id.
the profile page is still online of course without the full name, what is 
correct and what i expected.
it still contains a lot of public information, like the about page and links 
etc, what is normally also delivered in the profile api
request.
why does the buzz api not continue deliver the profile, just without
the full name, like it is on the profile page?

Original issue reported on code.google.com by mixer2 on 20 Aug 2010 at 10:19

[GoogleCodeExporter]

The idea is that by choosing to hide their name they're asking not to be found 
in search. Obviously you can still find them if you know their numeric 
identifier or they comment on something you see. 

I'm marking this as WontFix since we're actually respecting the user's 
intention here.

Original comment by a...@google.com on 22 Aug 2010 at 11:01

• Changed state: WontFix

[GoogleCodeExporter]

hi, that isn't correct.

i can get my profile with the following url:
https://www.googleapis.com/buzz/v1/people/108342835137361545402/@self

if i disable the option i get a 404 error, instead of the result. therefore it 
is NOT possible to still get the profile with "their numeric identifier".
that's why i wrote "but surprisingly the profile completely isn't available 
through the api anymore, even if it's requested with the correct profile id."

since the option explicitly says that the user shouldn't be found with it's 
"full name", he should imho still be found by his email address.
https://www.googleapis.com/buzz/v1/people/mixer2@gmail.com/@self

there are two reasons why getting the profile through the email address doesn't 
conflict with the privacy.
firstly the email address is what we want to protect, not the public id. if we 
already know the email address, it doesn't make sense at all to try to protect 
it against being connected with the profile id it belongs to.
the privacy setting with the full name tries to additionally protect your 
profile to be connected to your real live identity. and has really nothing to 
do with the email address.
the second thing is, that it doesn't protect anything anyway. if we have the 
email address and want to know the users id, we can simply create a @ post 
(which still works), request that post and parse the id out of it. this are 2 
instead of 1 api requests (maybe 3 if you clean up and delete the post after 
getting the id) and produces some spam to the users mail box. don't think that 
this is the way i want PUBLIC user id to be protected ;)

oh and as we're talking about privacy already those @ posts still show my full 
name, even if i have disabled the option Oo
this should really be fixed immediately!!

Original comment by mixer2 on 23 Aug 2010 at 7:30

[GoogleCodeExporter]

and it's not only the @ reply. with the following on google i can still be 
found with my full name:
site:http://www.google.com/profiles christoph stickel

i think the label "Display my full name so I can be found in search (also 
required to use Google Buzz and Latitude)" is very confusing for users, since 
they expect NOT to be found anymore. okey, you can't do anything with all the 
caches out there, but at least for the new stuff and the dynamic content this 
option should replace the full name with the nickname as it is on the profile 
page.

Original comment by mixer2 on 23 Aug 2010 at 7:41