crecker

Thank you for this comment. For todo comments, Satoshi or whoever was used "//// todo: " so it might be for that too.

Let me ring you in a bit. Can I also order a pizza?

> That's not what's characteristic for a coinbase transaction, many transactions might have only one input.

Yes, you're correct. Thank you for the clarification, however I wanted to mark the check found on the source code. By the way, "bad article": I think you're a little bit over exaggerating.

Great question. I can't say this was intentional or not. To people interested, it was only one line of code missing: he ""forgot"" to include the first transaction to the mapTransactions.

Yes, correct. But why including such specific parts? This was my question after that phrase :)

See my comment https://news.ycombinator.com/item?id=33130641#33131539

Verbose? Explaining data structures to newbie is verbose, isn't it? Off-topic?

And then a different hash from the hardcoded value in the code? Not quite sure. You need to verify your sources. You can easily verify the hash of the pre-genesis block yourself: https://www.reddit.com/r/btc/comments/7o0ejr/has_anyone_trie...

If you mean a different hash from the actual genesis block of Bitcoin, released on 3rd January 2009, of course it's different. We're talking about two different networks.

Hahah it's gohugo but I wanted to customize a little bit. It's a funny easter egg to mention the incredible genius behind Olivetti

Thanks, I might expand this in a new article :) This seemed to be too long for some readers.

Who knows? The person or people behind Satoshi identity. I believe that the person who posted that source code on BitcoinTalk forum has already stated that he merely copied&pasted the code (so he did not introduce any weird formatting).

> Why would someone who obiviously likes the beauty of code and writing in general not fix those?

Because that code is heavily edited, prepared for a review. For sure there are some missing comments (e.g. see "debug print" on line 112 compared to line 1042).

Thanks, I did not know about this!

Hi! OP here, thanks for your comment. Please note that I'm not a native English speaker so probably during translation I might have miswritten concepts as I intended. Let me explain.

The fact that he released the first genesis block on 3rd January 2009 with the sentence of UK Times article is not casual. We can see from the first version of the source code that his network was ready many days before that date. Was he waiting for "fixing issues"? No, he ended up clearly with a release that contained many errors (e.g. amount created in genesis block can not be spent).

> Isn't this completely normal in programming? I only ever use the plural first person in code unless I'm specifically referring to myself as a human (in the same way that academic writing uses the plural).

Yeah, I do agree. However if you notice there are some comments written in a particular style ( with double slashes //) and there are some others written with four slashes. It's really weird to have both styles on codes, unless there are more people (>= 1) that work on the code or that reviews the code.

In addition to this, please understand that none of my content must be taken as the only truth in this world, so I'm open to any discussions about those weird things I noticed :)

Ahh, Adobe.. they have earnings for billions and billions and they can not improve their software suites on performance..

Go Mattermost!

How to Write a Technical Book https://serhack.me/articles/how-to-write-technical-book/

Really similar to one I have already seen on Photoshop. My goal was comparing the pdfs without any Adobe, my editors do not have license for that.

Probably. It's really similar to the approach that munificentbob used in his tool (http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...). It uses mainly a Photoshop action.

Thank you! :) you do not know how many issues I spotted on older books I formatted. Paragraphes randomly moved on the top, images streched as I was build more pdf.. all human errors that can be - at least - spotted.

It looks like I need to watch it with 3d glasses, but I like it!

> It's automatic. As if there were no page boundaries, like in text diffs). But for a paged-based diff-tool it would already be quite useful, if the user could interactively specify pages to ignore, so that the comparison can start again where both docs are the same (e.g. at the start of the next chapter).

Gotcha. I might transform this project from a command-line only to a visual tool. I could implement that, thanks for the idea. I can actually have some sections of the PDF ignored.

I took inspiration from that repository too! :)

Thanks for the feedback. Should the user specify the page boundaries or does pdf-diff automatically checks where page boundaries are?

Thanks for the comment! I think it's not too difficult to build something similar (even with a web server so you can make comparison on fly).

I'm playing with alpha compositing, I'm going to commit some little changes to enchant the experience a little bit.

> ImageMagick's `compare` can do this as well, on a pixel-level.

Yes, thanks for the comment. I wanted to build something with golang :)

Yes, if it causes things to shift, the tool shows every page red. This tool is meant to be ran in the final phase of typesetting, the moment when you want to focus attention on details (e.g. spacing).

> After the first few times comparing PDFs of schematics by eye, I said screw it and wrote a tool to export to PNGs and then compare them pixel-by-pixel. It saved me a ton of time and my sanity.

It saved mine! I usually work with books and sometimes it's really difficult to tell 10 people to check every single page if something has been different to a previous pdf I sent. They will never be able to find all the differences because we're humans, not bot. We make mistakes.

Thanks for your comment! By complicated PDFs, what do you mean exactly? A lot of pages? With forms? I've tried with standard technical books I have bought.

The pdf-diff tool simply captures a sort of "screenshot" of a PDF page and then compares it against to the page from the second PDF file you'd like to compare. Since it works by comparing raw pixels, I guess it'll work with complicated PDFs.

Now "working" does not mean it's a good result for the eye and this is why I asked for help regarding some issues.

I doubt that you could contribute to it, but it's a nice example. Thanks!

I love those! Was wondering if there were any other topics not related to programming that might need the same love.