网站综合信息 gregable.com
    • 标题:
    • Greg Grothaus: Gregable 
    • 关键字:
    •  
    • 描述:
    • If you don't find programming algorithms interesting, stop reading. This post is not for you. On the 
    • 域名信息
    • 域名年龄:17年1个月18天  注册日期:2007年09月04日  到期时间:2019年09月04日
      邮箱:registrar-abuse  电话:+1.8772376466
      注册商:GOOGLE INC. 
    • 备案信息
    • 备案号: 
    网站收录SEO数据
    • 搜索引擎
    • 收录量
    • 反向链接
    • 其他
    • 百度
    • 1  
    • 590,000  
    • 快照:无首页快照  
    • Google
    • 0  
    • 0  
    • pr:3  
    • 雅虎
    • 0  
    •  
    •  
    • 搜搜
    • 0  
    •  
    •  
    • 搜狗
    • 27  
    •  
    • 评级:1/10  
    • 360搜索
    • 0  
    •  
    •  
    域名流量Alexa排名
    •  
    • 一周平均
    • 一个月平均
    • 三个月平均
    • Alexa全球排名
    • 3,567,593  
    • 平均日IP
    • 日总PV
    • 人均PV(PV/IP比例)
    • 反向链接
    • dmoz目录收录
    • -  
    • 流量走势图
    域名注册Whois信息

    gregable.com

    域名年龄: 17年1个月18天
    注册时间: 2007-09-04
    到期时间: 2019-09-04
    注 册 商: GOOGLE INC.
    注册邮箱: registrar-abuse
    联系电话: +1.8772376466

    获取时间: 2016年10月11日 03:45:17
    Domain Name: GREGABLE.COM
    Registrar: GOOGLE INC.
    Sponsoring Registrar IANA ID: 895
    Whois Server: whois.google.com
    Referral URL: http://domains.google.com
    Name Server: GENE.NS.CLOUDFLARE.COM
    Name Server: MAREK.NS.CLOUDFLARE.COM
    Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
    Updated Date: 2016-02-21
    Creation Date: 2007-09-04
    Expiration Date: 2019-09-04

    >>> Last update of whois database: Mon, 2016-Oct-10 19:48:49 GMT <<<

    For more information on Whois status codes, please visit https://icann.org/epp

    Domain Name: gregable.com
    Registry Domain ID:
    Registrar WHOIS Server: whois.google.com
    Registrar URL: https://domains.google.com
    Updated Date: 2016-02-21T08:00:00Z
    Creation Date: 2007-09-04T07:00:00Z
    Registrar Registration Expiration Date: 2019-09-04T07:00:00Z
    Registrar: Google Inc.
    Registrar IANA ID: 895
    Registrar Abuse Contact Email: registrar-abuse
    Registrar Abuse Contact Phone: +1.8772376466
    Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
    Registry Registrant ID:
    Registrant Name: Contact Privacy Inc. Customer 124161046
    Registrant Organization: Contact Privacy Inc. Customer 124161046
    Registrant Street: 96 Mowat Ave
    Registrant City: Toronto
    Registrant State/Province: ON
    Registrant Postal Code: M4K 3K1
    Registrant Country: CA
    Registrant Phone: +1.4165385487
    Registrant Phone Ext:
    Registrant Fax:
    Registrant Fax Ext:
    Registrant Email: 77jvdj1ubty2
    Registry Admin ID:
    Admin Name: Contact Privacy Inc. Customer 124161046
    Admin Organization: Contact Privacy Inc. Customer 124161046
    Admin Street: 96 Mowat Ave
    Admin City: Toronto
    Admin State/Province: ON
    Admin Postal Code: M4K 3K1
    Admin Country: CA
    Admin Phone: +1.4165385487
    Admin Phone Ext:
    Admin Fax:
    Admin Fax Ext:
    Admin Email: 77jvdj1ubty2
    Registry Tech ID:
    Tech Name: Contact Privacy Inc. Customer 124161046
    Tech Organization: Contact Privacy Inc. Customer 124161046
    Tech Street: 96 Mowat Ave
    Tech City: Toronto
    Tech State/Province: ON
    Tech Postal Code: M4K 3K1
    Tech Country: CA
    Tech Phone: +1.4165385487
    Tech Phone Ext:
    Tech Fax:
    Tech Fax Ext:
    Tech Email: 77jvdj1ubty2
    Name Server: GENE.NS.CLOUDFLARE.COM
    Name Server: MAREK.NS.CLOUDFLARE.COM
    DNSSEC: signedDelegation
    URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
    >>> Last update of WHOIS database: 2016-10-10T19:47:58Z <<<

    For more information on Whois status codes, please visit
    https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

    Please register your domains at: https://domains.google.com/
    This data is provided by Google for information purposes, and to assist
    persons obtaining information about or related to domain name registration
    records. Google does not guarantee its accuracy.
    By submitting a WHOIS query, you agree that you will use this data only for
    lawful purposes and that, under no circumstances, will you use this data to:
    1) allow, enable, or otherwise support the transmission of mass
    unsolicited, commercial advertising or solicitations via E-mail (spam); or
    2) enable high volume, automated, electronic processes that apply to this
    WHOIS server.
    These terms may be changed without prior notice.
    By submitting this query, you agree to abide by this policy.
    同IP网站(同服务器)
    其他后缀域名
    • 顶级域名
    • 相关信息
    网站首页快照(纯文字版)
    抓取时间:2016年10月11日 03:45:15
    网址:http://gregable.com/
    标题:Greg Grothaus: Gregable
    关键字:
    描述:If you don't find programming algorithms interesting, stop reading. This post is not for you. On the other hand, if you do find algorithms interesting, in addition to ...
    主体:
    Greg Grothaus: Gregable
    Discussing geekery, the environment, and life in Silicon Valley.
    Aug 22, 2012
    rel=canonical as a browser feature
    I informally propose that rel=canonical become a tag that not only search engines respect, but also browsers.
    For a little while now HTML5 browsers seem to have a feature where javascript can modify the displayed URL of the page using window.history.pushState.  The changes are of course subject to same origin policy rules (ie: the protocol, hostname, and port cannot be modified, only the path and parameters). 
    Originally javascript folks hacked this in with older browsers by shoving text after the "#" symbol in the URL.  Even though there are a number of problems with this, it was useful enough that it became somewhat widely used.  With modern browsers this is no longer required.
    To see what I mean, click on this little demo: http://kurtly.tumblr.com/sticky-history and look at the URL bar.  If you aren't running an outdated browser, you should see the URL changing every few hundred msec.  The page is not being re-fetched from the server.
    The rel=canonical link tag has been telling search engines basically "I know you are fetching the URL http://gregable.com/foo, but I'd suggest you should pretend this URL is http://gregable.com/bar in your search index".  Basically the same idea as the window.history.pushState functionality, only for search engines.
    I propose that a rel=canonical link tag on any HTML page which satisfies the same origin policy should visibly change the URL in the browser.  All the same motivations exist for this as they do in the browser.  If a user copy/pastes the displayed URL, they'll get a more satisfying experience.  If the user mis-types an URL (ie: .html vs .htm), sending them to the correct one generally requires a 301 redirect which adds latency.  The javascript solution is less reliable as users sometimes surf with javascript off, and the javascript may not execute until the page has finished loading either.
    Are there any obvious reasons I'm missing why this is a horrible idea?
    Are there any regular Gregable readers who work on browser standards and might want to propose this more formally?
    Posted by
    Greg
    at
    8:08 PM
    2
    comments
    May 8, 2012
    LED Bulbs
    I've just been trying out some LED light bulbs and they seem to have progressed a great deal since the last time I played with them.  For recessed fixtures that have a narrow angle of lighting, they seem to be a pretty good deal.
    Previous generations of LED light bulbs had problems:
    Blueish color of light
    Delay after turning on the wall switch
    Wouldn't work with dimmer controls
    Not as many lumens (brightness) as desired.
    I've bought a couple different bulbs off of Amazon and tried them out.  I ended up really liking these ecoBrites: http://www.amazon.com/gp/product/B003THZHOU.  No affiliation / kickbacks for me at all, I'm sure there are other great options out there too.
    They seem to solve all of the above problems, though they do look a li

    © 2010 - 2020 网站综合信息查询 同IP网站查询 相关类似网站查询 网站备案查询网站地图 最新查询 最近更新 优秀网站 热门网站 全部网站 同IP查询 备案查询

    2024-10-17 07:53, Process in 0.0066 second.