HN user

SteveArmstrong

52 karma
Posts0
Comments19
View on HN
No posts found.
Mayday.us 12 years ago

I know I'm not financially liable, but when the bank has to cancel and reissue my card (with a new number), it's still annoying to have to go and switch it everywhere. Smaller surface area (so less places to change) helps with that pain too.

That means they're less likely to have their servers and data seized by the US Gov't (assuming it's all hosted in Canada, and not an EC2-US instance), but the .com address is a US asset that can still be seized.

With the way the article compared it to donating organs, I figured this was a system for releasing information after death. In that case, the de-anonymizing problem is less of an issue. (Informed consent of this problem would still be needed of course)

3. I think he was referring to aggregate file size (total amount stored) not a single file. If that's the case, his point still stands.

4. He was probably saying that, as the average age of the nodes in the network goes up, the chance of them failing goes up. Also, the duplication you say (hundreds of copies) is in direct opposition to usable space (hundreds of copies means you can only use 1/100 of the space on your node. Because of this, I don't think your files will ever be duplicated on the order of "hundreds", probably less than 10. Also, it's important to keep clear: My node will backup to hundreds of other nodes, but each individual file fragment will only be duplicated to 3 (or whatever) nodes. That smaller number is the important one that keeps getting discussed.

I think that's only true if it was known how many wallets were actually lost. As is, the fraction of worth captured in that wallet can never be re-distributed to other people who own bitcoins, because the wallet is never decommissioned, just dormant.

S4 16 years ago

I was hoping to find a "for example, S4 can be used to" line in there, but I didn't see it initially. I assume filtering the Twitter fire-hose of data could be a common use?