Closed akshaybharwani closed 11 months ago
Ah yeah links are broken because @elrido disabled issues in the fork that was the base for this repository.. We could re-enable issues there (which I would have nothing against it) and then archiving it, so issues are no longer writable.
But to not get started on that discussion again what about quickly enabling it, saving it in archive.org and then updating the links?
I tried finding an existing capture in https://web.archive.org/web/20210119224035/https://github.com/elrido/ZeroBin/issues/79 and https://web.archive.org/web/20210223200729/https://github.com/elrido/ZeroBin/issues/79, but it is all 404.
All right, I give up on that[0]. I re-enable the issues (I wasn't happy disabling them in the first place, only to avoid anyone creating new issues ) and archived the repo, so that we can keep these links read-only, preserving the public history of our fork.
Thank you @akshaybharwani for bringing this to our attention.
[0] that being to a) retain a link between ZeroBin and our fork for discoverability and b) me keeping an online backup of the project in case this repo ever gets vandalized or I otherwise loose control of it.
Both links under Why is it named PrivateBin? are broken. I tried to look for the concerned issue in this repo and original Zerobin repo, but couldn't find anything related to it. The link mentioned refers to this repo but they don't have their issues visible publicly.