This is the mail archive of the
mailing list for the GCC project.
Re: gnu-gabi group
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>, Alexandre Oliva <aoliva at redhat dot com>, Pedro Alves <palves at redhat dot com>, Mark Wielaard <mark at klomp dot org>, Joseph Myers <joseph at codesourcery dot com>, Suprateeka R Hegde <hegdesmailbox at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, GNU C Library <libc-alpha at sourceware dot org>, Binutils <binutils at sourceware dot org>
- Cc: <nd at arm dot com>
- Date: Tue, 16 Feb 2016 10:55:37 +0000
- Subject: Re: gnu-gabi group
- Authentication-results: sourceware.org; auth=none
- Nodisclaimer: True
- References: <CAMe9rOr6jj0ax0B=9dFpuMYCu=HJaf9a3g2-NGnvNV2ZWTqwXg at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1602082307130 dot 18645 at digraph dot polyomino dot org dot uk> <CAMe9rOqoABu=bD5tgeBQsQXWZmhd5CHSZuwfobg8ezoCmCHNGg at mail dot gmail dot com> <56BC61F0 dot 3010507 at gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1602111635320 dot 29940 at digraph dot polyomino dot org dot uk> <20160211182033 dot GA23152 at blokker dot redhat dot com> <56BE2824 dot 7080906 at redhat dot com> <orpovyhtng dot fsf at livre dot home> <CAMe9rOotDQp=08SnBZg1nTvAEJdJGj76_r8FJequQ2YEa7sf=A at mail dot gmail dot com> <56C1FA6B dot 1030806 at arm dot com> <20160215173647 dot GS7732 at vapier dot lan>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
On 15/02/16 17:36, Mike Frysinger wrote:
> On 15 Feb 2016 16:18, Szabolcs Nagy wrote:
>> you as a group admin can do that, others cannot join
>> without creating a account at google (which requires
>> the acceptance of the google tos etc).
> that is annoying
i didn't know about firstname.lastname@example.org
(thanks Florian and Joseph)
>> you also have censorship rights over others.
> umm, every mailing list has that. Google Groups is no different.
it's better if admin right is at some discussion related
organization. (e.g. in case anything happens to H.J.Lu)
>> even if you add users to the list they cannot access
>> the archive through standard http or https,
> you're conflating things here. of course access is through "standard
> http or https" -- that's the transport protocol that everyone has to
> implement according to the standard in order to work. Goole is not
> different here.
the contents cannot be accessed with an http or https client.
(unless you know the magic urls below)
> complaining that the web interface executes JS is a bit luddite-ish.
some of us tend to browse the web from terminal (== no js).
>> (so wget does not work).
> every message has a link to the raw message you can use to fetch the
> mail directly.
> perm link:
redirects me to
> which has a link to the raw message:
i didn't know about this raw url, it seems there is
too, so if i always change the urls i can browse the archive.
(this is not discoverable without js as far as i can see)
with the +subscribe@ and the raw msg options i'm no longer
against google groups hosting public discussions (provided
the project documents these somewhere), i still prefer more
accessible alternatives though.
> it's actually nicer than mailmain (i.e. sourceware) as it doesn't do all
> the trivial content mangling (s/@/ at/g). it's not like e-mail scrapers
> today can't reverse that easily.
>> and the url through which you visit a post is not a
>> reliable permanent link so linking to posts is hard.
> every post has a "link" option to get a perm link. needing the location
> in the URL bar be the perm link is a weak (dumb imo) requirement.