Style bug: should DynamicLoad this information via profile instead of using
separate code for display (or if DL is deemed too expensive, check the
preferences first).

Comment 2 Niels Breet 2008-05-05 12:12:23 UTC

I have made planet.maemo.org respect the privacy settings. I probably need to
change comments and news items too.

I'd like to discuss the pros and cons here: 
https://garage.maemo.org/pipermail/maemo2midgard-discussion/2008-May/000282.html

http://maemo.org/news/planet-maemo/?org_openpsa_qbpager_net_nehmer_blog_index_page=106

actual results:
timeless
Why Open Source - an Interview with Engineers
2007-07-27 01:26 UTC 

expected results:
timeless
(timeless)
Why Open Source - an Interview with Engineers
2007-07-27 01:26 UTC 

I think that you should be able to do a one time query: For anyone who has
published a blog article (or done something similar which would publish their
name), if both of their privacy flags (first, last) are at the default value
(private), change them to public to reflect the fact that their information was
published.

For anyone who hasn't published anything, their privacy was maintained and
should therefore be maintained (i.e., don't change their flags). For new
accounts, to aid openness, you could set the default to publish. For people who
have actually changed their privacy settings, you should respect what they've
set.

(I understand you want this in email, I can't easily respond to your thread and
don't want to have to subscribe to a mailing-list which would require me to
disclose more information about myself than I do here.)

Comment 4 Niels Breet 2008-05-07 15:17:35 UTC

(In reply to comment #3)
> http://maemo.org/news/planet-maemo/?org_openpsa_qbpager_net_nehmer_blog_index_page=106
> 
> actual results:
> timeless
> Why Open Source - an Interview with Engineers
> 2007-07-27 01:26 UTC 
> 
> expected results:
> timeless
> (timeless)
> Why Open Source - an Interview with Engineers
> 2007-07-27 01:26 UTC 

Oops, I made a thinko in my code. It should now look like your expected result.

> I think that you should be able to do a one time query: For anyone who has
> published a blog article (or done something similar which would publish their
> name), if both of their privacy flags (first, last) are at the default value
> (private), change them to public to reflect the fact that their information was
> published.

Agreed.

> For anyone who hasn't published anything, their privacy was maintained and
> should therefore be maintained (i.e., don't change their flags). For new
> accounts, to aid openness, you could set the default to publish. For people who
> have actually changed their privacy settings, you should respect what they've
> set.
> 

I'll look into the new user defaults and how I can run this one time query.

OK, it now matches my expected results.

Seems like we can close this now.