Re: [Django] #29396: Using date__year comparisons together with OuterRef causes an IndexError

[Django]

#29396: Using date__year comparisons together with OuterRef causes an IndexError
-+-
 Reporter:  Dmitry Shachnev  |Owner:  Windson
 |  yang
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Windson yang):

 * status:  new => assigned
 * owner:  nobody => Windson yang


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d9dcebcd15b00719cf2c5e8adc1a3a2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29408: Add validation of ordering by a field from related model.

[Django]

#29408: Add validation of ordering by a field from related model.
-+-
 Reporter:  Shadi Akiki  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Windson yang):

 I think we can just address this in the document and don't fix it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.2ed8826d14dc60aee882b6620db2d128%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #8936: Add view (read-only) permission to admin

[Django]

#8936: Add view (read-only) permission to admin
-+-
 Reporter:  simon|Owner:  Olivier
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I pushed a commit with some edits. I'm okay with merging this tomorrow,
 although I find the tests a bit lacking. In particular, many of the
 template changes are untested. I added some `assertContains()` assertions
 but more are needed. This could be done after the alpha release, I
 suppose.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.207838d37f4a394d8b8d6a738d0dc2af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21080: collectstatic post-processing fails for references inside comments

[Django]

#21080: collectstatic post-processing fails for references inside comments
-+
 Reporter:  shreyas@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by powderflask):

 Re: comment:6  is a slightly different issue and MUCH easier to patch.

 This issue is caused by generators (like http://jqueryui.com/themeroller)
 that urlencode stuff in a comment block.
 E.g.
 {{{
 /*! jQuery UI - v1.12.1 - 2016-09-14
   * http://jqueryui.com
   * Includes: core.css, accordion.css, ...
   * To view and modify this theme, visit
 http://jqueryui.com/themeroller/?...&iconsHover=url(%22images%2Fui-
 icons_55_256x240.png%22)...
   * Copyright jQuery Foundation and other contributors; Licensed MIT */
 }}}

 The regular expression in storage.HashedFilesMixin matches `url(...)` in
 the comment, but it does NOT unquote the urlencoded quotation mark: `%22`
 The last step of `converter()` unquotes the transformed url:  `return
 template % unquote(transformed_url)`,  converting the urlencoded quotation
 marks back, and thus messing up the filename, as can be seen in the posted
 stack trace:
 {{{
 The file 'jquery-ui-dist/"images/ui-icons_55_256x240.png"' could
 not be found...
 }}}
 (Notice the excess quotation marks in the path.)

 == Patch:
 storage.py line 61
 `-  r"""(url\(['"]{0,1}\s*(.*?)["']{0,1}\))""", `
 `+
 r"""(url\((?:['"]|%22|%27){0,1}\s*(.*?)(?:['"]|%22|%27){0,1}\))""", `

 This matches url encoded single- or double-quotes and fixed several such
 issues with 3rd party packages that included generated CSS files like
 this.

 IF a general fix for ignoring comments in CSS files is implemented, that
 would resolve this issue too.
 But IF NOT, this is a simple fix that prevents `collectstatic` from
 crashing on common 3rd party packages.

 Happy to submit a patch for this if this seems worthwhile.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.4e8d78729f28487a67744ee8c5fcfbb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2361: QuerySet.filter(m2mfield__isnull=False) may return duplicates

[Django]

#2361: QuerySet.filter(m2mfield__isnull=False) may return duplicates
-+-
 Reporter:  daniel.tietze@…  |Owner:  Calvin
 |  DeBoer
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Calvin DeBoer):

 * owner:  Adrian Holovaty => Calvin DeBoer
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.1a464c8240113d2841bd30072f0adecc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29297: Exception ignored in: . at 0x111aafe08>

[Django]

#29297: Exception ignored in: . at 0x111aafe08>
-+-
 Reporter:  kingctan |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shaheed Haque):

 One observation is that when I run the server WITHOUT the PyCharm
 debugger, these errors seem not to occur.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f27370b7656e3be9909965937a71cda4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16470: Make FileResponse set the Content-Disposition header

[Django]

#16470: Make FileResponse set the Content-Disposition header
-+-
 Reporter:  mnot@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a177f854c34718e473bcd0a2dc6c4fd935c8e327" a177f854]:
 {{{
 #!CommitTicketReference repository=""
 revision="a177f854c34718e473bcd0a2dc6c4fd935c8e327"
 Fixed #16470 -- Allowed FileResponse to auto-set some Content headers.

 Thanks Simon Charette, Jon Dufresne, and Tim Graham for the reviews.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.fde10929fa7f89491586601b696cd580%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28743: Clarify the term "deployment server" in the documentation

[Django]

#28743: Clarify the term "deployment server" in the documentation
--+
 Reporter:  Thomas Güttler|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I'm going to close this as wontfix. The proposed PR (whilst fine in
 itself) wasn't any great gain, and just created work for the translation
 teams.

 ''Maybe'' a glossary would be a good addition to the docs — but this would
 need to be contributor driven.

 The best way to push that forwards would be an example of how it would
 begin (some terms and definitions) and then a discussion on Django
 Developers to see if there was support for it. That would be a separate
 issue than this one.

 Short of such a development, I do think "deployment server" really should
 be clear enough.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.901769326d9fdd4ce4e9a03cc0b3fdf1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29410: Provide project_urls in setup.py to improve Django's PyPI page

[Django]

#29410: Provide project_urls in setup.py to improve Django's PyPI page
--+
 Reporter:  Philip James  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Packaging |  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.55d4104dea11ac16ca878cc65c78a071%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29410: Provide project_urls in setup.py to improve Django's PyPI page

[Django]

#29410: Provide project_urls in setup.py to improve Django's PyPI page
-+
   Reporter:  Philip James   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Packaging  |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 The setup.py package spec has allowed for additional project URLs for a
 while now, but they were documented earlier this year.

 https://packaging.python.org/tutorials/distributing-packages/#project-urls

 I suggest adding Django-related project urls to Django's root setup.py, so
 that the PyPI page links people to the source code, fundraising page,
 documentation, and issue tracker correctly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.9393f613d0a3ddee09d0141a10c337f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29409: Support SameSite cookies on 1.11.x

[Django]

#29409: Support SameSite cookies on 1.11.x
+--
 Reporter:  Simon Bennetts  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Uncategorized   |  Version:  1.11
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Per our [https://docs.djangoproject.com/en/dev/internals/release-process
 /#supported-versions supported versions policy], 1.11 is only receiving
 data loss and security fixes.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.481c2f443775472353f8b0bf419fd664%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29409: Support SameSite cookies on 1.11.x

[Django]

#29409: Support SameSite cookies on 1.11.x
--+
   Reporter:  Simon Bennetts  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  1.11
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 SameSite cookies have been implemented on the master branch:
 https://code.djangoproject.com/ticket/27863
 Unfortunately we have various services that are on the 1.11.x stream and
 its non trivial to update them to 2.x
 Is there any chance of backporting SameSite cookies to 1.11.x?
 Are there any reasons why the patch might need to be significantly
 different in 1.11?
 If its essentially the same patch then I'd be happy to look into
 backporting it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.1914ba51ff4f4988f9f9680686185120%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28743: Clarify the term "deployment server" in the documentation

[Django]

#28743: Clarify the term "deployment server" in the documentation
--+
 Reporter:  Thomas Güttler|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Anton Mo Eriksson):

 * status:  assigned => new
 * owner:  Anton Mo Eriksson => (none)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.139b112ea11073af7206cbecfe57132b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29408: Add validation of ordering by a field from related model. (was: ordering by field from related model does not validate if field exists)

[Django]

#29408: Add validation of ordering by a field from related model.
-+-
 Reporter:  Shadi Akiki  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * component:  Uncategorized => Database layer (models, ORM)
 * version:  2.0 => master
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I'm going to accept this provisionally. There's
 
[https://github.com/django/django/blob/2dcc5d629a6439b5547cdd6e67815cabf608fcd4/django/db/models/base.py#L1598-L1600
 a `FIXME` in `models/base.py`] specifically about this:


 {{{
 # Skip ordering in the format field1__field2 (FIXME: checking
 # this format would be nice, but it's a little fiddly).
 fields = (f for f in fields if LOOKUP_SEP not in f)
 }}}

 Added in
 
[https://github.com/django/django/commit/d818e0c9b2b88276cc499974f9eee893170bf0a8
 d818e0c9b2b88276cc499974f9eee893170bf0a8].

 Either we should address this, or remove the comment and close as
 `wontfix` if "fiddly" turns out to be more effort than it's worth.

 A test case and a patch showing what "fiddly" actually entails would be
 great.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.9e88489961d56291259f958546935a1b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28743: Clarify the term "deployment server" in the documentation

[Django]

#28743: Clarify the term "deployment server" in the documentation
-+-
 Reporter:  Thomas Güttler   |Owner:  Anton Mo
 Type:   |  Eriksson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anton Mo Eriksson):

 * owner:  nobody => Anton Mo Eriksson
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d3215a9aab7fef4b68aa5f3b326d6586%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29408: ordering by field from related model does not validate if field exists

[Django]

#29408: ordering by field from related model does not validate if field exists
-+
   Reporter:  Shadi Akiki|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 When the `ordering` class member in `Meta` of a model contains a field
 from a related model, and that field does not exist, django's
 `makemigrations` does not throw an error. However, if it is a direct field
 member of the same class, `makemigrations` does throw an error.
 Example below tested on Django 2.0.5

 {{{
 from django.db import models

 # Create your models here.

 class Agreement(models.Model):
 agreement_id = models.AutoField(verbose_name='ID', serialize=False,
 auto_created=True, primary_key=True)
 #class Meta:
   # generates error in makemigrations
   # app.Agreement: (models.E015) 'ordering' refers to the nonexistent
 field 'id'.
   # ordering = ['id']

 class Order(models.Model):
 agreement = models.ForeignKey(Agreement, models.DO_NOTHING)
 class Meta:
   # does not generate error in makemigrations
   # but does so during runtime
   # e.g. [x for x in Order.objects.all()]
   ordering = ['agreement__id']

 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/057.6f64193eb09411898d970a3a306364d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.