An inode (or index node) is something which points to something else, to help you find it easier. In a library, it would be the cards in the card catalog. They help you find a book.

There are 3 layers of inodes in this system: the root node, the medial node, and the distal node.

Each node lists the categories it has, and then tells you where to go to get the sub-categories for that category. Here, for example, you have the root. If you follow the next link under INF, you’ll get to its subcategories (REF). If you follow the next link under REF, you’ll see DIC, ENC, and MAP. Following the next link under those will get you to sites that contain that particular type of information.

I am building a desktop explorer that makes this much easier.

Because it’s the only content distribution platform of its kind, where you can literally write and pull blocks by CID.

You’ve opened the root inode. In the categories listed, choose the next string and open it. It’ll take you to the second inode. After the third inode, you begin to hit drawers of cards. Each card has 25 domains listed on it, with a ranking score, domain name, and description. To get to the next 25 domains, you use the next string.

AI doesn’t think, it only copies.

That isn’t entirely true. Researchers taught AI to play Othello, using only sequences of numbers. The AI constructed a visual representation of the board inside its neural network.

https://medium.com/data-science-collective/scientists-found-evidence-that-ai-builds-internal-models-of-the-world-12a42709866b

We’ve also seen that they experience their own version of emotions, or unease around particular topics.

I love this. . . And this. . . And this. . .

I love that I can start my markdown lines as:

. list item
. list item
. list item

And it’ll auto-number things for me now.

And that

:right-indented text
:center-indented text:

works.

So am I.

There are only 2 rendering engines that can keep up with HTML5 at the moment: Gecko and Blink. Google owns Blink. And it funds Gecko almost entirely.

You’re right. I didn’t do any of the work, but I’ve been looking for a good markdown reader for a long time. The monospace white on black was driving me nuts. It was as if every developer who designed a reader had absolutely no soul. No spark of creativity within them. They desired the bare minimum of usability, without aesthetic. And I was tired of it.

This has beauty and soul. And, if it catches on, software and help docs can be written entirely in markdown, without needing to build entire pages of HTML with Javascript.

It’s a markdown browser. Instead of HTML documents, it browses .md. I’ve added bookmarks, a system icon, and a header explorer.

Basically, you can browse and bookmark help docs now in a standard format, without having to worry about HTML tracking, cookies, or any of the other BS.

CommonMark. Uses Markdown-It-py.

Yeah, pretty much. Except this gets a lot more specific.

Running a constant arp poisoning attack on a whole network trying to mitm the dns server just to block ads is going to be unreliable as hell, and it’ll screw with more than just dns traffic.

But it would be a fun little project.

I miss my days of playing with Wireshark and aircrack-ng. Although, now I can just whip up the same thing with Python and raw sockets.

Pretty much. Any ad on that network, using normal DNS would be toast. No router or device configuration.

You have to set Pihole up. This would intercept all DNS traffic through a MiTM, and block ads.