public email addresses on packages server

[Roger Keays]

Has any consideration been given to concealing email addresses on pkgs.racket-lang.org for privacy purposes?

[Hendrik Boom]

On Sat, Feb 20, 2021 at 11:47:19PM +0700, Roger Keays wrote:
> Has any consideration been given to concealing email addresses on pkgs.racket-lang.org for privacy purposes?

Aren't those email addresses available anyway from github?

-- hendrik

[Sam Tobin-Hochstadt]

Github doesn't require making your email address public.

Sam

> --
> You received this message because you are subscribed to the Google Groups "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/20210223171932.ljgqq77qb5b7wjin%40topoi.pooq.com.

[Tony Garnock-Jones]

No, but it's an interesting thought. It might be quite a lot of design work to come up with something that made sense, but would you like to sketch out a proposal here to make the idea a little more concrete? I can't promise anything, but it'd be good to know the kinds of requirements that might be involved.

[Roger Keays]

I was just thinking along the lines of adding a "name" field to the table with the user/login data. If it is set, then it is displayed instead of the email. You should be able to search by this field too of course.

> --
> You received this message because you are subscribed to the Google Groups "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/080327d5-4d33-48bf-8d2f-870f1532b109n%40googlegroups.com.

[Tony Garnock-Jones]

Hi Roger,

On Wed, 24 Feb 2021 at 15:55, Roger Keays <rac...@rogerkeays.com> wrote:

I was just thinking along the lines of adding a "name" field to the table with the user/login data. If it is set, then it is displayed instead of the email. You should be able to search by this field too of course.

That sounds sensible. Thanks!

The email fields are also currently included in the JSON metadata for each package. For example, here's the (abbreviated) stanza for one of my packages in the catalog's https://pkgs.racket-lang.org/pkgs-all.json.gz file:

   "ansi" : {
      "author" : "tonygarn...@gmail.com",
      "authors" : [
         "tonygarn...@gmail.com"
      ],
      "build" : { ... },
      "checksum" : "c14081de59bc7273f1f9088a51d6d9c202b2b9d0",
      "description" : "ANSI and VT10x escape sequences for Racket.",
      "modules" : [ ... ],
      "name" : "ansi",
      "search-terms" : {
         ":build-success:" : true,
         "author:tonygarn...@gmail.com" : true,
         "ring:1" : true,
         "terminal" : true
      },
      "source" : "github://github.com/tonyg/racket-ansi/master",
      "tags" : ["terminal"],
      "versions" : {
         "default" : {
            "checksum" : "c14081de59bc7273f1f9088a51d6d9c202b2b9d0",
            "source" : "github://github.com/tonyg/racket-ansi/master",
            "source_url" : "http://github.com/tonyg/racket-ansi/tree/master"
         }
      }
   },

There's also an s-expression equivalent.

Do you have any thoughts on what, if anything, should be done about these files?

Regards,

  Tony

[Roger Keays]

I suppose another option would be to use one combined field with an email format like this:

Tony Garnock-Jones <to...@leastfixedpoint.com>

"search-terms" might need some special attention though. You might be able to list two author terms, like this:

"author:tonygarn...@gmail.com" : true,
"author:Tony Garnock-Jones" : true,

If the author has selected not to make his or her email public, then that information would be stripped from the json too.

I'm speculating here, because I have on idea where and how all this code is used. I think it would pay to be consistent with the json and the database in terms of fields and names though. If I were building it from scratch I would have separate fields for author name and email.