sprovoost
It's normal for a node to request headers in chunks of 2000, either as part of syncing the entire chain from scratch, or when catching up after being offline for more than two weeks.
https://github.com/bitcoin/bitcoin/blob/fc06881f13495154c888...
It's not the most efficient (asymmetric) way to waste bandwidth either. For each ~100 byte header request you get a 160 KB reply. You can instead ask for a block using a shorter message and get up to 4 MB. This way you can download the entire blockchain at 500+ GB multiple times.
Those with limited upload bandwidth (and for some reason not behind a NAT) can use -maxuploadtarget to limit the total upload.
I'm not sure how the available bandwidth is distributed between peers, but it's generally quite hard to dominate all connections of all nodes (search for "eclipse attacks"), even with a botnet [0].
So that leaves CPU draining as a possible goal (or stealing Bitcoin from random script kiddies who run untrusted code and dependencies from the internet).
[0] = which isn't free, probably not their most economic use case and some of their operators may not like it when you attack a cryptocurrency they themselves may want to use
Indeed the experience with other printers has been better. Same with e-books (so far). In fact at this point I'm quite happy I didn't use Amazon.
Here's a January 6, 2009 snapshot from the Way Back Machine. This was before he publicly released the code. The entire project is MIT licensed and only contained one file: the whitepaper. https://web.archive.org/web/20090106201347/http://sourceforg...
I should have linked to that.
> if you think this archive may be inauthentic
I don't think it's inauthentic. I'm saying Amazon could think it's inauthentic, and not tell me.
An editor or "professional" publisher may be able to explain the author what the problem is, but if they upload the book to KDP, they'll the exact same information I do. Unless there's some old boys network of course.
There may also be publishers that have an in house printing service. But then you lose the distribution advantage Amazon offers, because they can get a book from the printing press to the customer much faster (without inventory).
As I pointed out in the blog, it takes Amazon about 3-4 days from their printer in Poland to my home in Utrecht, and that includes 1 day in some sort of intermediary Amazon delivery warehouse in Rotterdam. IngramSpark needs two weeks to get book into the EU, but even in the US - when a customer orders from Amazon - they seem to need about a week. Old school publishers are probably even slower, if they can do print on demand at all.
I said: "It's a matter of time before they all scan the content before printing."
What I'm saying is that the way the book got blocked, is a harbinger of what future physical book censorship could look like. Once the techniques developed for social media moderation make their way into physical book publishing. Amazon happens to be ahead of the curve there, whereas other printer companies are probably still a bit old fashioned (which is good news).
> The whitepaper is not in the nov08 distribution or the bitcoin-0.1.0.tgz,
How do you know this? The original link in Satoshi's email points to a file that no longer exists and afaik he didn't publish a checksum. So maybe it WAS in there. But is that what the Amazon robot was worried about? Probably not...
Also, unless you were on the mailinglist yourself at the time, you can't even know that the email archive is real.
Book printers should be an easier choke point than social media companies, given that they have far less content to screen. It's just that no western government or advocacy group has bother to do the choking, as they are too busy pressuring social media companies to moderate content.
Show HN: Bitcoin Core on single board using Armbian
Bitcoin Core and Lightning and Rails on AWS
Historical Bitcoin Core Client Performance
Please steal €100 from my first smart contract
Four hypotheses and two experiments of why my app hasn't made me rich yet
Idea one sounds most useful to me, if it hasn't been done yet. Given your experience in teaching people iOs development in real life, you could start with that topic.
Normal books have code samples; perhaps the book can have assignments that you can code and run inside the book? I believe there are some web based iOs development or simulator systems out there; can you leverage those? Or instead of running code, just parse the answer to see if it is correct.
Or you can even use crowdsourcing to have humans grade student assignments as an in-app purchase.
A few other possible explanation that crossed my mind and I'm sure are wrong and already thought about:
* the distance between both sides was measured very accurately, above ground. The earth is not flat, so the distance underground is shorter. I'm too tired to calculate how much shorter.
* relatistic effect of the beam going deeper underground on its way over; I read elsewhere that they already considered the effect of altitude difference between the two stations and that it was orders of magnitude smaller.
* some other mistake in distance measurement; have they tried sending other, easier to measure, signals over to figure out the distance? Or some other independent way to measure that distance?
It is however pretty easy to see why inflation is good for people in power, in particular governments; it's a hidden tax. And yes it does encourage people to spend, in fact it encourages people to borrow and then spend. Even borrow so much that it crashes the system.
So as far as I'm concerned the fixed money supply is about the only good property of Bitcoin. Other than that it's a ponzi scheme and it's a lot more cumbersome than electronically traded gold.