codyjones

A search engine could be distributed and any person running a node would be rewarded with a "SearchCoin". In other words, combine the financial rewards and distributed nature of running the BitCoin network but with a search engine as the proof of work.

The question is, how do you prevent bad actors from delivering biased results or malware to users? Should a client query N nodes and only accept the result if they match? And if the search algorithm is public, is it still possible to prevent that algorithm from being gamed by SEO results?

I liked Tales from the Loop and A Very English / Very British Scandal. The Marvelous Mrs. Maisel wasn't my cup of tea, but it seemed well done.

It would carry more weight to someone who has never heard of Substack or doesn't know how big a company it is. They'd assume it was a large company because of who was reporting about it.

Someone has to read and like your PR to approve it. Presenting your work as a series of simpler steps helps the PR recipient (and you!) mentally verify it.

This is very reminiscent of Wendy Carlos's "Switched on Bach". If you liked the video, but have never heard the album, I recommend you track down a copy. Tragically it never seems to be available on streaming services (at least the ones I subscribe to).

Anna von Hausswolff has done some great work with real church organs too.

It's likely the Firefox developers use more of its shortcuts because they are more familiar with the product and are more interested in optimizing their workflow than a typical user. Exploring, which includes backtracking, is the core of the web browsing experience so I'm not surprised people are doing that far more than, say, searching for a substring.

It's also worth pointing out there isn't a great opportunity to learn the keyboard shortcuts Firefox provides. Traditionally you'd learn shortcuts by seeing them next to menu items, but the menus are hidden behind the Alt key, and many actions simply aren't listed there. For example, "Find Again" / F3 is omitted.

One of my kids learned Scratch at home. He tried some local classes, hoping they would teach more advanced material, but they were introductory and he spent his time tutoring the other kids (not a bad lesson in itself!)

We briefly tried GameMaker Studio 2, however we had no prior experience and finding out what functions were needed or called made it a high friction experience.

He has been playing Minecraft since a young age, and creates elaborate redstone mechanisms. I like how this mixes creativity, spatial planning, and boolean logic, and doesn't require learning a new UI or language.

Most recently we tried creating a Minecraft mod in Java using Forge. I cannot state strongly enough: do not do this. The Forge architecture is fundamentally broken, whereby it adds some functionality but otherwise forces you to code directly against decompiled Java classes.

Most tutorials only work with a specific version of Forge/Minecraft. There are no release notes or documentation, because there is no API. (To be fair, the Forge aspect is documented, though I only found it useful once I already knew what it was trying to explain.)

So what started out as an exciting father-son project became something I dreaded.

There is a scene half way through "The Tale of the Princess Kaguya" that blew my mind. A little context is necessary though.

Like many Ghibli women, the princess was free spirited. However, she let herself be reformed into a bland and meek woman. She did this only to please her well-meaning but dim father.

Eventually her mind breaks and she runs away. Her expensive clothes fly out from behind her. The formerly restrained artwork becomes wild, thick charcoal lines that jump around. Even the normally static moon shakes in the sky. It was beautiful, and I loved how the style changed to match the princess' emotions.

The reviewer is not wrong, though it certainly clouded his judgment of the book. The book needed more editing.

Between the two journals, I really recommend The Making of Kareteka instead. It's more concise, and it shows Mechner at more of a formative age. Many of the things he did are easily related to, like not knowing what path to choose in life, cutting classes, taking transit because he didn't have a driver's license, or moving out for the first time. And even though it's a diary, it ends like a good story.

Making of PoP is a hundred pages longer. Though interesting, Mechner's attempt to enter the movie industry, international travel, and the development of PoP 2 made the book unfocused. At the end it peters out and abruptly stops.

I wonder if, of the two, it gets more attention because Prince of Persia is familiar to more people?