Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 27/05/2025, 22:40:38 UTC
Testnet 4 was done in the same defective ways to an extent, correct?
It seems foolish to me to do something the same way twice and expect different results(?)
It solved an immediate problem for them-- the fact that it would go the same way isn't the biggest deal since it doesn't cost anything for the developers just switch to another one.  It probably would have been superior to implement a better approach, but I guess they thought it was better to address it immediately than immediately take the extra time for a more generalized solution.

When tn3 was created it was proposed by some to just reset the chain accepted by the software every major version.    I think discussion on that just landed on that the project could switch to doing that later if problems continued.  For a decade the problems didn't continue. Now that they are back I suspect the project will end up doing something like that.

Quote
Whoever intentionally left bugs or "features" in should probably reconsider that in some fashion.  Bugs are a two way door IMO.
It's a test harness, the only purpose exists for is the developers testing.  It's often the case that test harnesses have intentional defects to facilitate testing.    It seems to have worked out fine so far.

To be clear, no one cares whatever flavor of shitcoining you're interested in.  If you want to eat peercoins topped with clam sauce or whatever, that's your own business.  But bitcoin devs aren't interested in shitcoining, and aren't interested in maintaining software for shitcoins themselves, and just won't continue to use any testnet thing that has economic trade that makes testing cost money that ought to be free.

Original archived Re: Bitcoin Testnet is the first ever altcoin & only alt Satoshi is 100% linked to.
Scraped on 27/05/2025, 22:35:53 UTC
Testnet 4 was done in the same defective ways to an extent, correct?
It seems foolish to me to do something the same way twice and expect different results(?)
It solved an immediate problem for them-- the fact that it would go the same way isn't the biggest deal since it doesn't cost anything for the developers just switch to another one.  It probably would have been superior to implement a better approach, but I guess they thought it was better to address it immediately than immediately take the extra time for a more generalized solution.

When tn3 was created it was proposed by some to just reset the chain accepted by the software every major version.   I think discussion on that just landed on that the project could switch to doing that later if problems continued.  For a decade the problems didn't continue. Now that they are back I suspect the project will end up doing something like that.

Quote
Whoever intentionally left bugs or "features" in should probably reconsider that in some fashion.  Bugs are a two way door IMO.
It's a test harness, the only purpose exists for is the developers testing.  It's often the case that test harnesses have intentional defects to facilitate testing.   It seems to have worked out fine so far.