Re: Wither berkeleylug.ORG - keep/drop decide by: 2019-04-17T04:39:28Z - currently expires 2019-05-17T04:39:28Z

["Michael Paoli" <Michael.Paoli@cal.berkeley.edu>]

So ... "that time" draws closer.
Deciding by end of the upcoming BerkeleyLUG meeting could be
good ... especially if anyone wants to fork over the $$
to (transfer+)renew BerkeleyLUG.org

And that (at least approximate) cost (to keep/renew):
$17.20 USD transfer+renew --> gandi.net (my preference)
$12.00 USD + tax (renew @ domains.google.com) ($$ to Google & keep where is)

That would cover an additional year.

And ... stats!  Have some (web) stats on BerkeleyLUG.com now,
this covers like oh ... some week(s) or so now:

data from other than my own IPs or those of site itself

471 "hits"

120 unique source IPs

top 10 "hits" by source IPs:
count, IP, "reverse" DNS (if any found):
46 61.160.207.85
32 51.254.15.86 ip86.ip-51-254-15.eu.
29 211.214.160.164 ns.thundernet.co.kr.
29 151.80.56.51 51.ip-151-80-56.eu.
27 61.160.221.73
26 61.160.247.137
26 185.234.218.100
20 192.99.35.63 ns559656.ip-192-99-35.net.
20 192.99.0.107 ns500498.ip-192-99-0.net.
16 93.158.161.168 93-158-161-168.spider.yandex.com.

target domain:port, by count:
    376 berkeleylug.org:80
     50 www.berkeleylug.org:80
     39 berkeleylug.org:443
      7 www.berkeleylug.org:443

Traffic seems to mostly be bots ... good and ... not.
counts of request types:
298 GET (136 for /, 134 for /robots.txt)
167 POST
  7 HEAD (all for /)

If we keep it ... not all that much planned for it:
add DNSSEC (staged, not yet implemented)
add additional DNS servers (to RFC compliant 3 or more)
If we're instead, to let it expire, I won't bother with additional
nameserver(s), might not bother with DNSSEC, and other than that
would let it expire, and presuming it does so, then basically
drop its little bit of infrastructure once expired and moot
(DNS, web redirection)

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> Subject: Re: Wither berkeleylug.ORG - keep/drop decide by:  
> 2019-04-17T04:39:28Z - currently expires 2019-05-17T04:39:28Z
> Date: Tue, 02 Apr 2019 00:54:58 -0700

> I'm relatively inclined to agree ... though some may think/feel
> otherwise.
>
> I'll let the money talk - if folk(s) put up the $$ to renew
> (some person(s) have said they would - but I've not seen the $$ ... yet)
> (or transfer+renew), it shall happen, ... otherwise it goes bye-bye.
>
> > From: ace36 <acohen36@gmail.com>
> > Subject: Re: Wither berkeleylug.ORG - keep/drop decide by:  
> > 2019-04-17T04:39:28Z - currently expires 2019-05-17T04:39:28Z
> > Date: Fri, 29 Mar 2019 18:32:12 -0700
>
> > On Thu, Mar 28, 2019 at 10:06 PM Michael Paoli <
> > Michael.Paoli@cal.berkeley.edu> wrote:
> >
> > > So ... berkeleylug.COM isn't going anywhere soon (other than where things
> > > are hosted may shuffle about).
> > >
> > > But ... what of berkeleylug.ORG?
> > > It expires 2019-05-17T04:39:28Z.
> > > We ought to, by about 2019-04-17T04:39:28Z decide to either
> > > o let it go (expiring 2019-05-17T04:39:28Z), or
> > > o renew it (possibly also transferring registrar from domains.google.com)
> >
> > IMHO, I think Berkeleylug.ORG should just be left to disappear.
> > While a few other vocal advocates have put forward cogent arguments to the
> > effect that it doesn't really hurt to keep around Berkeleylug.ORG (e.g.,
> > due to cybersquatting, misdirecting site visitors,...etc), I rather see it
> > that .ORG can be safely discarded without any significant loss of
> > popularity compared to BerkeleyLUG.COM. Never even really knew for certain
> > that BerkeleyLUG.ORG existed before, myself.
> >
> > Just my own 2 cents.
> > -A

--
You received this message because you are subscribed to the Google Groups "BerkeleyLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to berkeleylug+unsubscribe@googlegroups.com.
To post to this group, send email to berkeleylug@googlegroups.com.
Visit this group at https://groups.google.com/group/berkeleylug.
For more options, visit https://groups.google.com/d/optout.