Hacker Newsnew | past | comments | ask | show | jobs | submit | sprovoost's commentslogin

It already has the "fix" inherited from the Bitcoin code they reuse. Though you shouldn't count on that feature to not have bugs: the Dogecoin codebase is old and poorly maintained. If you run it on a cloud service, always turn on billing limits. https://github.com/dogecoin/dogecoin/blob/master/doc/reduce-...


This script asks a node for the 2000 headers between block 783,569 and 785,568.

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


You're confused about the roles here. An editor is someone who works either directly for the author or they work for the publisher. In any case they don't work for the printer / distributor, which is KDP.

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.


My only experience in the field is working for an "old school" publisher, where copyright concerns like the one described in the blog post would be the responsibility of the acquisitions editor (an employee of the publisher). Our printers were a separate company, who, like you say, had no editorial responsibilities. "Old school" publishers do typically coordinate distribution, though. There are also some that support print-on-demand (for example, Manning).

I think it's instructive here that KDP stands for Kindle Direct Publishing, not Kindle Direct Printing.


I think their name is deceptive, see my other reply :-)


I guess Hackernews doesn't render the tl&dr I wrote: <meta name="description" content="How a KDP infringement claim led to kafkaesq dialogues with support. I could not speak to a human and was never told what the offence was."/>


Maybe I was not clear enough on this: I'm not claiming my book was censored, at least not in the traditional political sense of the word.

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).



You take everything literally I assume?


So you're saying that Amazon will communicate their requirement to a "real" publisher, but not to fake publisher like me? Some sort of old boys network I should just pay to join?


If Amazon wanted more detailed proof, they could just ask for that. There's no limit to how pedantic one can be in evaluating evidence. Maybe they need a physical wet signature from a specific bureaucrat at the US copyright office, sent by courier. Without knowing what constitutes evidence in their eyes, there's simply too many permutations of things they might want to see. I tried a few of those permutations and then gave up.

> 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.


It's not even that the evidence isn't good enough, or that the archive appears inauthentic, it's that the evidence you've supplied doesn't even attempt to support your claim. Nothing in the archive you linked implies the whitepaper is under MIT.

(And: if you think this archive may be inauthentic, perhaps you should've chosen another for your evidence.)


Ah, I see your point.

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.


Nowhere do I predict Amazon to become a monopoly. The prediction is that all other publishers will start following their model of screening content. Perhaps against some global blacklist, more or less following the model social media companies use.


Yes, because Amazon doesn't scan paper books, this route still works. But there aren't that many companies that can print books. It's a matter of time before they all scan the content before printing. At least, in the dystopian scenario.

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.


Why would they scan paper books to proactively look for copyright violations? Have you ever heard of a bookstore doing that?

There's a different standard of due diligence if you publish a book vs just selling copies of it.


I did not say: "They will all scan physical books"

I said: "It's a matter of time before they all scan the content before printing."


I think the distinction between printer and publisher is being lost here. KDP is a publisher, and a very cost-conscious one at that. You would have a very different experience with the editorial process of a different publisher, as most don't use Amazon-level automation.


I wouldn't even call them a publisher. They're a printer, drop-shipper and a book store. I am both the writer and the publisher and I hired my own editor. A lot of companies call themselves "publisher" but really aren't.

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.


I stopped reading at “James Damore, who was sacked after he circulated the misogynist iniquitous 33,000-word memo” as it reveals this journalist has an overt agenda and doesn’t mind lying to achieve it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: