Ciro Santilli @cirosantilli 37

The guy who coded the initial version of BackRub, the first version of Google Search, but left before the company formed. TODO how did he meet Largey Brage? Why did he leave Google?

In 1997 he cofounded eGroups, a mailing list management website, together with the mysterious Carl Victor Page, Jr., Larry Page's older brother. eGroups was sold to Yahoo! in 2000 for $432m, just before the Dot-com bubble burst.

As of 2021 his net worth was of "only" $1b, even though his original Google shares would have been worth $13b. He must have sold too much too early to do other cool stuff. archive.ph/IgkMI:

When Mr. Page and Mr. Brin founded Google in 1998, Mr. Hassan bought 160,000 shares for $800. When Google went public in 2004, the shares were worth more than $200 million. The shares, now in Google’s parent company, Alphabet, would be valued at more than $13 billion today [2021].

Did Largey give him this nice deal as a way to thank him for helping start the company, or was it just that they had no big hopes and $800 seemed right? youtu.be/pmXDtTD6vQY?t=146 suggests the stocks were part of his compensation for 3 months of coding work. Also mentioned at: nypost.com/2021/08/20/google-founder-created-revenge-site-against-estranged-wife

In 2001, Scott married a Vietnamese chick called Allison Huynh from university and they had three children.

In 2014 Hassan asked for a divorce, and the proceedings were a shitshow, lasting more than 7 years.

In 2004 he tried strike a $20 million^[ref] post-nuptial after Google went public, which she declined, so things were already crappy back then.

Then, during the divorce, Scott even created a revenge website for her as well. He's so petty! Down as of 2024 of course. There are only some weird redirect archives now: web.archive.org/web/20210915000000*/https://allisonhuynh.com redirecting to sites.google.com/view/allisonhuynhcom

The divorce is covered in several major outlets:

To be fair, he did work on a lot of cool stuff after BackRub for which he deserves credit, not the least the company that created the Robot Operating System, which is a cool sounding open source project, which is awesome. But this divorce story is so damning! He should just own up to it, split the cash, and move on... The fact that the Google money came from an investment before marriage likely complicates things.

The fact that he does not have a Wikipedia page as of 2022 is mind blowing, especially after divorce details. Maybe Ciro Santilli will create it one day. Just no patience now. OK, done it June 2022: en.wikipedia.org/wiki/Scott_Hassan let's see if it lasts. The page lasted but ended up being Ciro Santilli's first edit war, how exciting:

December 2022: an anonymous user with IP from California removed divorce details and google share ownership details, both of which had a New York Times source: www.nytimes.com/2021/08/20/technology/Scott-Hassan-Allison-Huynh-divorce.html. Discussion at: en.wikipedia.org/wiki/Talk:Scott_Hassan#Divorce_details_removed_as_%22poorly_sourced_material%22_by_anonymous_user_even_though_they_had_a_source_from_the_New_York_Times It feels exactly like the type of thing Scott would have done himself. And he possibly inadvertently exposed his real IP in doing so: 24.6.226.102. It is pingable, but Nmap analysis shows nothing of interest.
June 2024: another partial revert removing the juicy divorce details by user named "ReversingWrongs". The username choice so incredibly cute and naive it makes Ciro wonder if this is from some woman that loves him (mother, child, new partner?) rather than just a Hassan sockpuppet. OK, perhaps with en.wikipedia.org/wiki/Wikipedia:Biographies_of_living_persons#People_who_are_relatively_unknown the divorce has to be left out? It's always impossible to decide with those wikipedia things. What you can say, is not necessarily what people want to read about, even when it is incredibly well source.

Looking a the history, he just kept revealing different IPs and continuously reverting, which other people put back in. Another of his IPs:

24.234.111.66 is marked as being from Las Vegas online.

There is also an interesting edit from 2600:1700:5470:5c50:7566:9580:1b60:ab41 which mentions without source the little known fact

after working at Washington University's Medical Libraries Group (having been recruited out of SUNY Buffalo for the summer).

so it could be Hassan adding some actually good and interesting information to the article. That one however also has an edit to en.wikipedia.org/wiki/Ernest_Nagel so maybe it's not him.

Figure 2.
Scott Hassan and Allison Huynh posing with a green screen in 2001
. Source. Oh, to be young and feel love's keen sting.

Figure 3.
Screenshot of allisonhuynh.com by the Daily Mail
. Source.

 Read the full article

Send free emails from Heroku by

Ciro Santilli 37 Updated 2025-07-16

 View more

Arghh, why so hard... tested 2021:

SendGrid: this one is the first one I got working on free tier!
Mailgun: the Heroku add-on creates a free plan. This is smaller than the flex plan and does not allow custom domains, and is not available when signing up on mailgun.com directly: help.mailgun.com/hc/en-us/articles/203068914-What-Are-the-Differences-Between-the-Free-and-Flex-Plans- And without custom domains you cannot send emails to anyone, only to people in the 5 manually whitelisted list, thus making this worthless. Also, gmail is not able to verify the DNS of the sandbox emails, and they go to spam.
Mailgun does feel good otherwise if you are willing to pay. Their Heroku integration feels great, exposes everything you need on environment variables straight away.
CloudMailin: does not feel as well developed as Mailgun. More focus on receiving. Tried adding TXT xxx._domainkey.ourbigbook.com and CNAME mta.ourbigbook.com entires with custom domain to see if it works, took forever to find that page... www.cloudmailin.com/outbound/domains/xxx Domain verification requires a bit of human contact via email.
They also don't document their Heroku usage well. The envvars generated on Heroku are useless, only to login on their web UI. The send username and password must be obtained on their confusing web ui.

 Read the full article

Google X by

Ciro Santilli 37 Updated 2025-07-16

 View more

Wikipedia reads:

Any contributor could create and own new Knol articles, and there could be multiple articles on the same topic with each written by a different author.

so basically exactly what Ciro Santilli wants to do on OurBigBook.com. Ominous.

Like any closed source "failure", everything was deleted. wiki.archiveteam.org/index.php/Knol

 Read the full article

Google Docs by

Ciro Santilli 37 Updated 2025-07-16

 Read the full article

Knol by

Ciro Santilli 37 Updated 2025-07-16

 View more

Very similar to OurBigBook.com!

People who worked on it:

Udi Manber: project lead
www.wired.com/2008/07/google-knol/ mentions various engineers. The original page had photos, including the full team photo, but these died, but are visible on the archive: web.archive.org/web/20151220002650/http://www.wired.com/2008/07/google-knol/.
Ben McMahan: "Developed, launched, and maintained Knol", mentioned at:
- x.com/benjmcmahan
- www.benjaminmcmahan.com/ has email ben.j.mcmahan@gmail.com
Michael McNally (2007-2009), "project's technical lead": mentioned at: www.wired.com/2008/07/google-knol/,
github.com/xiangtiandai Xiangtian Dai xiangtian.dai@google.com
Mohsin Ahmed: can't find any online profiles

Video 1.

How to use Google Knol by Hack Learning (2011)

Source. One of the last users of the website for sure! The owner of that YouTube channel is a Mark Barnes:

Video 2.

Jimmy Wales on Google's Knol (2008)

Source.

Replying to a listener phone-in question WNYC radio, mediated by Brian Lehrer.
It was about to launch it seems, and it was not clear at the time that anyone could write content, as opposed to only selected people.

Jimmy then corrects that misinformation. He then clearly states that since there can be multiple versions of each article, including opinion pieces, like OurBigBook.com, Knol would be very different to Wikipedia, more like blogging than encyclopedia.

Video 3.

Google Knol: the future of academic journals? by Doug Belshaw (2010)

Source.

Bibliography:

Wikipedia & Knol: Why Knol Already Failed by gwern.net (2009). So there was some kind of monetary payment on the site. Interesting and sad.

 Read the full article

Organise the world's information by

Ciro Santilli 37 Updated 2025-07-16

 View more

E.g. about.google/ in 2022.

 Read the full article

SourceForge by

Ciro Santilli 37 Updated 2025-07-16

 View more

RIP: www.quora.com/Is-SourceForge-still-relevant-to-open-source-projects/answer/Ciro-Santilli

 Read the full article

Sallie (FutureAI) by

Ciro Santilli 37 Updated 2025-07-16

 View more

Not having a manipulator claw is a major issue with this one.

But they also have a co-simulation focus, which is a bit of a win.

 Read the full article

Financial crisis of 2007-2008 by

Ciro Santilli 37 Updated 2025-07-16

 Read the full article

High-frequency trading by

Ciro Santilli 37 Updated 2025-07-16

 View more

Video 1.

High Frequency Trading by WEED e.V. (2014)

Source.

 Read the full article

There are no known eukaryotes which never had mitochondria by

Ciro Santilli 37 Updated 2025-07-16

 View more

As of 2020, there are no known eukaryotes which have never had mitochondria.

Known eukaryotes without mitochondria, which are very rare, have lost mitochondria they previously had.

Having mitochondria appears to be a requisite for being an eukaryote. This is one of the central thesis of Power, Sex, Suicide by Nick Lane (2006).

 Read the full article

ELF Hello World Tutorial / Generate the example by

Ciro Santilli 37 Updated 2025-07-16

 View more

Let's break down a minimal runnable Linux x86-64 example:

hello_world.asm

section .data
    hello_world db "Hello world!", 10
    hello_world_len  equ $ - hello_world
section .text
    global _start
    _start:
        mov rax, 1
        mov rdi, 1
        mov rsi, hello_world
        mov rdx, hello_world_len
        syscall
        mov rax, 60
        mov rdi, 0
        syscall

Compiled with:

nasm -w+all -f elf64 -o 'hello_world.o' 'hello_world.asm'
ld -o 'hello_world.out' 'hello_world.o'

TODO: use a minimal linker script with -T to be more precise and minimal.

Versions:

NASM 2.10.09
Binutils version 2.24 (contains ld)
Ubuntu 14.04

We don't use a C program as that would complicate the analysis, that will be level 2 :-)

 Read the full article

ELF Hello World Tutorial / ELF header by

Ciro Santilli 37 Updated 2025-07-16

 View more

Running:

readelf -h hello_world.o

outputs:

Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class:                             ELF64
Data:                              2's complement, little endian
Version:                           1 (current)
OS/ABI:                            UNIX - System V
ABI Version:                       0
Type:                              REL (Relocatable file)
Machine:                           Advanced Micro Devices X86-64
Version:                           0x1
Entry point address:               0x0
Start of program headers:          0 (bytes into file)
Start of section headers:          64 (bytes into file)
Flags:                             0x0
Size of this header:               64 (bytes)
Size of program headers:           0 (bytes)
Number of program headers:         0
Size of section headers:           64 (bytes)
Number of section headers:         7
Section header string table index: 3

Running:

readelf -h hello_world.out

outputs:

Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class:                             ELF64
Data:                              2's complement, little endian
Version:                           1 (current)
OS/ABI:                            UNIX - System V
ABI Version:                       0
Type:                              EXEC (Executable file)
Machine:                           Advanced Micro Devices X86-64
Version:                           0x1
Entry point address:               0x4000b0
Start of program headers:          64 (bytes into file)
Start of section headers:          272 (bytes into file)
Flags:                             0x0
Size of this header:               64 (bytes)
Size of program headers:           56 (bytes)
Number of program headers:         2
Size of section headers:           64 (bytes)
Number of section headers:         6
Section header string table index: 3

Bytes in the object file:

00000000  7f 45 4c 46 02 01 01 00  00 00 00 00 00 00 00 00  |.ELF............|
00000010  01 00 3e 00 01 00 00 00  00 00 00 00 00 00 00 00  |..>.............|
00000020  00 00 00 00 00 00 00 00  40 00 00 00 00 00 00 00  |........@.......|
00000030  00 00 00 00 40 00 00 00  00 00 40 00 07 00 03 00  |....@.....@.....|

Executable:

00000000  7f 45 4c 46 02 01 01 00  00 00 00 00 00 00 00 00  |.ELF............|
00000010  02 00 3e 00 01 00 00 00  b0 00 40 00 00 00 00 00  |..>.......@.....|
00000020  40 00 00 00 00 00 00 00  10 01 00 00 00 00 00 00  |@...............|
00000030  00 00 00 00 40 00 38 00  02 00 40 00 06 00 03 00  |....@.8...@.....|

Structure represented:

# define EI_NIDENT 16

typedef struct {
    unsigned char   e_ident[EI_NIDENT];
    Elf64_Half      e_type;
    Elf64_Half      e_machine;
    Elf64_Word      e_version;
    Elf64_Addr      e_entry;
    Elf64_Off       e_phoff;
    Elf64_Off       e_shoff;
    Elf64_Word      e_flags;
    Elf64_Half      e_ehsize;
    Elf64_Half      e_phentsize;
    Elf64_Half      e_phnum;
    Elf64_Half      e_shentsize;
    Elf64_Half      e_shnum;
    Elf64_Half      e_shstrndx;
} Elf64_Ehdr;

Manual breakdown:

0 0: EI_MAG = 7f 45 4c 46 = 0x7f 'E', 'L', 'F': ELF magic number
0 4: EI_CLASS = 02 = ELFCLASS64: 64 bit elf
0 5: EI_DATA = 01 = ELFDATA2LSB: little endian data
0 6: EI_VERSION = 01: format version
0 7: EI_OSABI (only in 2003 Update) = 00 = ELFOSABI_NONE: no extensions.
0 8: EI_PAD = 8x 00: reserved bytes. Must be set to 0.
1 0: e_type = 01 00 = 1 (big endian) = ET_REl: relocatable format
On the executable it is 02 00 for ET_EXEC.
Another important possibility for the executable is ET_DYN for PIE executables and shared libraries.
ET_DYN tells the Linux kernel that the code is position independent, and can loaded at a random memory location with ASLR.
This is explained further at:
- stackoverflow.com/questions/2463150/what-is-the-fpie-option-for-position-independent-executables-in-gcc-and-ld/51308031#51308031
- stackoverflow.com/questions/34519521/why-does-gcc-create-a-shared-object-instead-of-an-executable-binary-according-to/55704865#55704865
1 2: e_machine = 3e 00 = 62 = EM_X86_64: AMD64 architecture
1 4: e_version = 01 00 00 00: must be 1
1 8: e_entry = 8x 00: execution address entry point, or 0 if not applicable like for the object file since there is no entry point.
On the executable, it is b0 00 40 00 00 00 00 00. The kernel puts the RIP directly on that value when executing. It can be configured by the linker script or -e. But it will segfault if you set it too low: stackoverflow.com/questions/2187484/why-is-the-elf-execution-entry-point-virtual-address-of-the-form-0x80xxxxx-and-n
2 0: e_phoff = 8x 00: program header table offset, 0 if not present.
40 00 00 00 on the executable, i.e. it starts immediately after the ELF header.
2 8: e_shoff = 40 7x 00 = 0x40: section header table file offset, 0 if not present.
3 0: e_flags = 00 00 00 00 Arch specific. i386 docs say:
The Intel386 architecture defines no flags; so this member contains zero.
3 4: e_ehsize = 40 00: size of this elf header. TODO why this field needed? Isn't the size fixed?
3 6: e_phentsize = 00 00: size of each program header, 0 if not present.
38 00 on executable: it is 56 bytes long
3 8: e_phnum = 00 00: number of program header entries, 0 if not present.
02 00 on executable: there are 2 entries.
3 A: e_shentsize and e_shnum = 40 00 07 00: section header size and number of entries
3 E: e_shstrndx (Section Header STRing iNDeX) = 03 00: index of the .shstrtab section.