Thanks for trying to keep these services up! And for chosing some other solution (?) than anubis/haphash which fights CPU/energy-burning AI monsters by inserting a man-in-the-middle CPU/energy-burning JavaScript on my laptop... see https://www.cl.cam.ac.uk/~rnc1/talks/040720-ProofWork.pdf or https://github.com/emintham/Papers/blob/master/Laurie%2CClayton-%20%22Proof-of-Work%22%20Proves%20Not%20to%20Work.pdf for history leason.
Paul Gevers <[email protected]> writes: > First, all Debian CI data pages, except the direct links to test log files > (such as those provided by the Release Team's testing migration excuses), now > require users to be authenticated before being accessed. This means that the > Debian CI data is no longer publicly browseable, which is a bit sad. However, > this is where we are now. Would it be possible to export the logs to some static host perhaps CDN-based somehow? Or implement a "publish publicly" button in logged-in mode to mark a particular log for public publication? Maybe such a short list of logs won't be problematic. It could even be "publish publicly for 1 month". I often include links to debci logs in upstream bug reports, and without details I think solving issues will be harder... sometimes bugs cannot be reproduced outside of the debci infrastructure, and allowing upstream to see real logs is useful. /Simon
signature.asc
Description: PGP signature
