gbaz
Yep, your approach sounds cleaner. I'd also want to store when someone was vouched for, just for more audit trail here. I like this approach, and think it could help...
i believe the intended meaning is: "have the database store a map of users to the list of those that have vouched for them"
Right -- in the event we get a spam package we can trace up the tree to find the malicious approvers and cut them off.
That package was removed from hackage because it was a proprietary package mistakenly uploaded. I'd welcome a PR to make the mirror client robust to such missing things.
I think for now ignoring 500 is fine.
Would this let us implement https://github.com/haskell/hackage-server/issues/727 as well?
I think we really should merge this. Sorry for letting it languish. Can you explain what "The queryExplain API apparently changed fractionally, which affects searchPackagesExplain." means in more detail? (the...
underlying/related issue in tar https://github.com/haskell/tar/issues/6
We have a plan to tackle the CDN issue so that shouldn't be a blocker on this.
Hackage server doesn't have a notion of special urls for special package docs -- anything we do should be able to be uniform for all docs. I don't think its...