7 ms·

These two points alone are honestly just bad news for Golang on the whole >> pkg.go.dev fetches the list of modules from proxy.golang.org: a closed-source prox

These two points alone are honestly just bad news for Golang on the whole >> pkg.go.dev fetches the list of modules from proxy.golang.org: a closed-source proxy through which all of your go module fetches are being routed and tracked >> pkg.go.dev hard-codes a list of centralized git hosting services [that are the only allowed ones]

ergo14 6y ago
Python PyPi downloads are also tracked https://pypistats.org/ https://pypistats.org/. The data is public, nothing wrong with that IMO.
- vosper 6y ago
  I think all the PyPi stats are available in BigQuery, if anyone’s interested in doing some analysis.
  - leetrout 6y ago
    Edit: I had the wrong table. It does have the data https://console.cloud.google.com/bigquery?project=the-psf&p=the-psf&d=pypi&t=downloads20200801&page=table https://console.cloud.google.com/bigquery?project=the-psf&p=...
- X-Istence 6y ago
  If I host a package outside of the PyPi eco-system though as a wheel, pip while happily install it if I provide a full path to it, and at that point it's not part of pypistats.org
LukeShu 6y ago
>> pkg.go.dev hard-codes a list of centralized git hosting services [that are the only allowed ones] So how in the world did git.lukeshu.com get to be on that list? https://pkg.go.dev/git.lukeshu.com/go/libfastimport https://pkg.go.dev/git.lukeshu.com/go/libfastimport
- ddevault 6y ago
  Note that some features are absent here. You can't click on any of the declarations to view their source, for example. This is the degraded view for unknown hosts.
  - throwayws 6y ago
    That does not work in the old godoc.org either: https://godoc.org/git.lukeshu.com/go/libfastimport https://godoc.org/git.lukeshu.com/go/libfastimport So that's not against pkg.dev. Did somebody look into why? Anyway it seems that the repo was not added to pkg.dev automatically: https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 and the automatic fetching should work now: https://github.com/golang/go/issues/37002 https://github.com/golang/go/issues/37002
    - arp242 6y ago
      > Anyway it seems that the repo was not added to pkg.dev automatically: > > https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 The way this works (or rather, worked) is that you first need to "go get" a module and then it gets picked up by the pkg.go.dev system. This works like that for every site, and was kind weird and confusing, although as you mentioned this was improved on recently. Either way: not related to that module being on sr.ht; that's just coincidental.
    - ddevault 6y ago
      See my comment here which explains how "go-source" works: https://news.ycombinator.com/item?id=24024130 https://news.ycombinator.com/item?id=24024130 It doesn't work on godoc.org not because they don't recognize your domain, but because cgit doesn't have go-source meta tags.
      - throwayws 6y ago
        There was a proposal to add a new go-source-2 meta tag, but that was abandoned because a lot of code hosting sites would not have been supported yet: https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/40477 https://github.com/golang/go/issues/40477 That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added. - internal/source: https://github.com/golang/pkgsite/blob/master/internal/source/source.go https://github.com/golang/pkgsite/blob/master/internal/sourc... Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though. Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on Go/pkgsite (haven't checked whether they do)
jand 6y ago
export GOPRIVATE="domain1.com,domain2.com" [1] https://golang.org/cmd/go/#hdr-Module_configuration_for_non_public_modules https://golang.org/cmd/go/#hdr-Module_configuration_for_non_...
d10 6y ago
pkg.go.dev supports fossil-scm (and I believe any "go gettable" source repo). So, the idea that it "hard-codes a list of centralized git ..." needs a citation. Whereas AFAIK godoc.org only supported git. IMHO support for a variety of SCMs makes pkg.go.dev a huge improvement. Support for "go get" and pkg.go.dev via fossil-scm does require some golang-specific meta tags, as TFA exclaims. But why is that a big deal, it's a golang repository after all?

ergo14 6y ago

Python PyPi downloads are also tracked https://pypistats.org/ https://pypistats.org/. The data is public, nothing wrong with that IMO.

vosper 6y ago
I think all the PyPi stats are available in BigQuery, if anyone’s interested in doing some analysis.
- leetrout 6y ago
  Edit: I had the wrong table. It does have the data https://console.cloud.google.com/bigquery?project=the-psf&p=the-psf&d=pypi&t=downloads20200801&page=table https://console.cloud.google.com/bigquery?project=the-psf&p=...
X-Istence 6y ago
If I host a package outside of the PyPi eco-system though as a wheel, pip while happily install it if I provide a full path to it, and at that point it's not part of pypistats.org

LukeShu 6y ago

>> pkg.go.dev hard-codes a list of centralized git hosting services [that are the only allowed ones] So how in the world did git.lukeshu.com get to be on that list? https://pkg.go.dev/git.lukeshu.com/go/libfastimport https://pkg.go.dev/git.lukeshu.com/go/libfastimport

ddevault 6y ago
Note that some features are absent here. You can't click on any of the declarations to view their source, for example. This is the degraded view for unknown hosts.
- throwayws 6y ago
  That does not work in the old godoc.org either: https://godoc.org/git.lukeshu.com/go/libfastimport https://godoc.org/git.lukeshu.com/go/libfastimport So that's not against pkg.dev. Did somebody look into why? Anyway it seems that the repo was not added to pkg.dev automatically: https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 and the automatic fetching should work now: https://github.com/golang/go/issues/37002 https://github.com/golang/go/issues/37002
  - arp242 6y ago
    > Anyway it seems that the repo was not added to pkg.dev automatically: > > https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 The way this works (or rather, worked) is that you first need to "go get" a module and then it gets picked up by the pkg.go.dev system. This works like that for every site, and was kind weird and confusing, although as you mentioned this was improved on recently. Either way: not related to that module being on sr.ht; that's just coincidental.
  - ddevault 6y ago
    See my comment here which explains how "go-source" works: https://news.ycombinator.com/item?id=24024130 https://news.ycombinator.com/item?id=24024130 It doesn't work on godoc.org not because they don't recognize your domain, but because cgit doesn't have go-source meta tags.
    - throwayws 6y ago
      There was a proposal to add a new go-source-2 meta tag, but that was abandoned because a lot of code hosting sites would not have been supported yet: https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/40477 https://github.com/golang/go/issues/40477 That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added. - internal/source: https://github.com/golang/pkgsite/blob/master/internal/source/source.go https://github.com/golang/pkgsite/blob/master/internal/sourc... Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though. Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on Go/pkgsite (haven't checked whether they do)

jand 6y ago

export GOPRIVATE="domain1.com,domain2.com" [1] https://golang.org/cmd/go/#hdr-Module_configuration_for_non_public_modules https://golang.org/cmd/go/#hdr-Module_configuration_for_non_...

d10 6y ago

pkg.go.dev supports fossil-scm (and I believe any "go gettable" source repo). So, the idea that it "hard-codes a list of centralized git ..." needs a citation. Whereas AFAIK godoc.org only supported git. IMHO support for a variety of SCMs makes pkg.go.dev a huge improvement. Support for "go get" and pkg.go.dev via fossil-scm does require some golang-specific meta tags, as TFA exclaims. But why is that a big deal, it's a golang repository after all?