3 ms·

This is a great idea. A lot of businesses heavily rely on old versions of open source packages always being available. The one time someone deprecated an npm pa

by sly010 10y ago

This is a great idea. A lot of businesses heavily rely on old versions of open source packages always being available. The one time someone deprecated an npm package, half of the nodejs stacks went with it. edit: Didn't mean to hit reply. Sorry.

vog 10y ago
Just delete your comment and put it on toplevel again.
- sp332 10y ago
  You can't delete comments that have been replied to.
  - vog 10y ago
    You can, and the reply would remain. The tree then looks like this: comment1 [deleted] comment3 However, you can delete comments only until a certain amount of time. If you wait too long, you can't delete anymore (and this is what happened here).
    - sp332 10y ago
      That's how it used to work, but I'm pretty sure it doesn't work like that anymore.
      - vog 10y ago
        I wonder if I'm the only one who is annoyed by the continuing lack of transparency at HN, wasting my time and other people's time with guesswork like this. I just took the time to start an "Ask HN" entry on that topic: "Ask HN: Where can I follow the changes of HN itself?" https://news.ycombinator.com/item?id=13460588 https://news.ycombinator.com/item?id=13460588
        vog 10y ago
        While that "Ask HN" entry got quite a few upvotes, this comment received downvotes. Why is that? Could anyone explain what's wrong with this comment?
notheguyouthink 10y ago
It doesn't really solve that use case though, does it? Eg, IPFS isn't permanent hosting - it's purely hosting as long as there are seeds, like bittorrent. Hypothetically if a package is very old there may be no seeds for it anywhere. Someone (NIXOS/etc) will still have to pay for hosting.
- IanCal 10y ago
  It does provide a solution though. If someone is still hosting it, you can access it in the same way. Nobody can pull, independently, a specific version down. They could remove their copy and hope nobody else is also providing it, but if it was a big problem other people could quickly start providing it and nobody else would notice the difference. Perhaps an equivalent thing for "someone will still have to pay for hosting" is that although that's true, anyone can put money into the pot to keep it going or bring it back, it's not reliant on the original creator to keep paying for it.

by sly010 10y ago

vog 10y ago

Just delete your comment and put it on toplevel again.

sp332 10y ago
You can't delete comments that have been replied to.
- vog 10y ago
  You can, and the reply would remain. The tree then looks like this: comment1 [deleted] comment3 However, you can delete comments only until a certain amount of time. If you wait too long, you can't delete anymore (and this is what happened here).
  - sp332 10y ago
    That's how it used to work, but I'm pretty sure it doesn't work like that anymore.
    - vog 10y ago
      I wonder if I'm the only one who is annoyed by the continuing lack of transparency at HN, wasting my time and other people's time with guesswork like this. I just took the time to start an "Ask HN" entry on that topic: "Ask HN: Where can I follow the changes of HN itself?" https://news.ycombinator.com/item?id=13460588 https://news.ycombinator.com/item?id=13460588
      - vog 10y ago
        While that "Ask HN" entry got quite a few upvotes, this comment received downvotes. Why is that? Could anyone explain what's wrong with this comment?

notheguyouthink 10y ago

It doesn't really solve that use case though, does it? Eg, IPFS isn't permanent hosting - it's purely hosting as long as there are seeds, like bittorrent. Hypothetically if a package is very old there may be no seeds for it anywhere. Someone (NIXOS/etc) will still have to pay for hosting.

IanCal 10y ago
It does provide a solution though. If someone is still hosting it, you can access it in the same way. Nobody can pull, independently, a specific version down. They could remove their copy and hope nobody else is also providing it, but if it was a big problem other people could quickly start providing it and nobody else would notice the difference. Perhaps an equivalent thing for "someone will still have to pay for hosting" is that although that's true, anyone can put money into the pot to keep it going or bring it back, it's not reliant on the original creator to keep paying for it.