by duskdozer 2 days ago

I think at this point the group of devs+ who are not fully on board with control by and dependence on big tech/VC is a small niche unfortunately.

my-huge-pony 2 days ago

I don't think this is true. From my experience, developers are the people who care about this topic the most. Just look at HN, almost everyone (who speaks out) is against.

  • akerl_ 2 days ago

    I'm very in favor of this work, but don't generally comment because these comment threads are full of folks strawmanning the work being done, and in my experience those folks aren't really interested in productive discussion.

    I'd be wary of trying to estimate the split of opinions based on who comments.

    • rcxdude 1 day ago

      Can you explain the misconceptions? Currently what I see is a) a checkmark box that can only come from a large provider, and b) no good idea of what that checkmark box means in a practical sense, or why I should care or why pypi cared to implement it. What is the threat that this prevents? To me this seems to not particularly improve security but that it does create this pressure towards using a small subset of providers (even if that pressure is pretty light at the moment).

      (I've had a quick read through the various links but they mostly seem to emphasize what it's not, which is why I say that it doesn't seem to improve security, and especially I don't really see a motivation for why these other parties need to be involved in the way they are: the only benefit I can imagine is a third-party attestation that some artifact corresponds to some source code, which seems to be partly besides the point and partly solvable through better means)

      • akerl_ 1 day ago

        I didn't reference misconceptions, for what it's worth. I referred to strawmanning, and if you're curious for some examples:

        https://news.ycombinator.com/item?id=50499144

        https://news.ycombinator.com/item?id=50500622

        https://news.ycombinator.com/item?id=50499218

        If you're curious to dig into what the checkmark means, why you should care, and why they implemented it, I'm not going to be able to do a better job than https://docs.pypi.org/attestations/security-model/

        • rcxdude 1 day ago

          All that page really says is "the signing does what it does", i.e. that it verifies that the package was signed by one of the 'trusted publishers'. It doesn't do anything to explain why I should care if a package came from github or whatever. Especially it doesn't explain why it should be github and not pypi or the original author that does this signing, since really what I care about is whether the author/maintainer of the package has changed, not their publishing platform, and presumably pypi already has at least the means to authenticate them.

      • lexicality 1 day ago

        FWIW they have at least significantly reduced the size and prominence of the checkmark. The original design had a giant green checkmark front and centre with a bunch of smaller green checkmarks all showing how super special and trustworthy the project was.