daenney (130)

Signed up 191 days ago

  • > Another issue was regarding FFMPEG and m3u8’s open source licenses and dealing with the possibility of a sudden license change.

    I'm not quite sure I follow there. Any existing code's license wouldn't be able to be changed. Contributors could agree to let their contributions be licensed under a dual/new/different license going forward but it won't just close up on you. This is also not something that would happen suddenly. FFmpeg has no CLA that do things like copyright assignment so changing the license would require approval from all contributors. Open source licenses is exactly what allows you to reuse, share and build on top of each other's expertise. If you want to develop your own implementation fine, but this argument seems rather weak to me.

  • I came across this article myself when I needed to figure out some stuff around using GCS, it's very useful and (still) accurate.

  • According to the repository it's a server written in Go though, not a client. It's nice to see projects like these pop up though :).

  • Considering that the standard library since 1.7 has a built-in context which net/http, chi and others use or can be layered in with httprouter, and the fact that we already have gorilla/context which is fairly widely used too and a few others what's the benefit of using this one?

  • That link is never going to work:

    ~ $ curl -vvvv https://groob.io/posts/go-sysadmin

    * Trying

    * TCP_NODELAY set

    * Connected to groob.io ( port 443 (#0)

    * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

    * Server certificate: groob.io

    * Server certificate: Let's Encrypt Authority X3

    * Server certificate: DST Root CA X3

    > GET /posts/go-sysadmin HTTP/1.1

    > Host: groob.io

    > User-Agent: curl/7.51.0

    > Accept: */*


    < HTTP/1.1 301 Moved Permanently

    < Content-Length: 185

    < Content-Type: text/html

    < Date: Thu, 15 Dec 2016 21:16:14 GMT

    < Location: http://localhost/posts/go-sysadmin/

    < Server: Caddy

    < Server: nginx/1.9.15


    Caddy seems to be slightly misconfigured, localhost is quite a different host for me :).

  • There's a fairly extreme lack of documentation on this project. It sounds nice based on what it promises to provide but without some usage example and this sparse a GoDoc I'm not sure what to make of it.