twohearted

Example: Patrick Stewart on Sesame Street https://www.youtube.com/watch?v=hA7lv1SDzno

This is why I switched to codex --yolo running in a container/vm. Now it does what it needs to do without bugging me and I can do other stuff. When it pings me I know there is something to review.

Yes I know they can escape containers, but that's not what I'm tasking them with.

This is a great idea and great work.

Context is intuitively important, but people rarely put themselves in the LLM's shoes.

What would be eye-opening would be to create an LLM test system that periodically sends a turn to a human instead of the model. Would you do better than the LLM? What tools would you call at that moment, given only that context and no other knowledge? The way many of these systems are constructed, I'd wager it would be difficult for a human.

The agent can't decide what is safe to delete from memory because it's a sort of bystander at that moment. Someone else made the list it received, and someone else will get the list it writes. The logic that went into why the notes exist is lost. LLMs are living the Christopher Nolan film Memento.

You can use sqlcipher on the command line along with the global password which can be found here https://x.com/m1guelpf/status/1854959335161401492

I looked at Screenpipe but it doesn't fill me with confidence. The ideal solution would be a device-agnostic self-hosted service for archiving and searching screenshots. Would make data migration super simple. And then the app snapping the screenshots could be almost trivial.

They call it mellow yellow

It's a bundle of 24 high quality games, by talented, diverse and motivated game developers for ~$8 each. And it comes with a free console. Art is worth paying for.

I feel like this is missing the point of Vim a little bit. It's not about using hjkl instead of arrow keys. It's about progressively learning a vast and useful language specifically made for editing text efficiently. And then realizing you can use every single part of that language in a macro. And then realizing you can use that same language to orchestrate those macros.

The music industry has been fighting against the natural economic theories of capitalism ever since the mp3.

Digital files have infinite supply. Draw a classic supply and demand diagram using that information and look at where the price should be. The supply curve is a vertical line at infinity on the x-axis. The demand curve crosses it at $0. Everyone knows and feels this intrinsically.

The artist is the thing with extremely limited supply. Something like Patreon will end up being the correct model.

I assume this has been tried but what happens if you give MuZero a goal like "keep the system/process that spawns me running as long as possible?"

I did the same thing but it just records it directly into Apple's Health app. Then you get the graphs for free!

My cynical take is that they are intentionally:

A) Making the camera protrusion ungainly so that most people think "I'm going to put a case on this to make it look and feel better."

B) Changing the shape of the protrusion periodically to force people to get a new case.

Therefore adding an invisible extra $40-50 profit on millions of iphones sold.

I bet they considered putting a secondary password confirmation field on the next screen, but that might have been too cruel.

from TFA: "One year ago, we announced that Keybase is supported by the Stellar Development Foundation."

Don't have to look much farther for motives. However, may I suggest a slight amendment to your statement and thinking:

The association with keybase.io does much to give the appearance of credibility, trustworthiness and stability to cryptocurrency.

Without those other "negligible" aspects there is no incentive for anyone to run nodes to validate the chain. There is no blockchain. It's those very things that allow these systems to function.

BofA still offers this but it's a shameful desktop-only tiny popup that only works with flash. They call it shopsafe.

Oh boy. If people think this is an example of being unacceptably direct and gruff, I need to reexamine the way I talk during technical discussions.

I've always thought it best to just cut straight to the core of issues like he's doing. I suppose it's a jerk move to corner people into admitting they're wrong even when it's obvious. Maybe there's a nicer jedi-mind way to do it.

Faecebook

keyfile in addition to a strong password.

The analogies damage this article because they feel wrong. For example the "never synchronous" example is more like this:

You order a burger at the cashier window, then go to the pickup window. If the burger is already made, it's already at the pickup window when you get there.

The author wants a special case where if the burger is already made, they hand it to you immediately at the cashier window. This might seem more efficient, but both in the restaurant and in code it makes logic way more complex.

Absolutely, click "No extra automation" on the last version and play it normally. It makes you question everything you previously thought was a random guess. Makes the game vastly better, because you're richly rewarded for thinking through every possibility. And you're incentivized to spend time thinking because you're not punished when it ends up being a truly random choice. Great, great work. Too bad minesweeper is not suited to mobile devices because I'd play this version all the time.

That is exactly what the cryptocrazies are stipulating. It's cryptocurrency vs fiat. Seen from the fiat perspective, it's an obvious bubble. But if you're on the cryptocurrency side, it's barely the start of a massive and inevitable shift.

If you consider BTC to be the stable currency then it is USD that is crashing.

Stop loss means get out NOW to stop losses. Trying to finesse a nickel out of a trade at that point is a sucker's game.

Getting "stopped out" is fine, it's part of investing. You need to stop your losses. I'm just saying don't put the order on the books for the exchange to pluck like a ripe berry.

This has always been a worry in the traditional stock market. With a stop loss order you're basically creating a "secret" order to sell at below market value. Anyone who knows about it has a direct incentive to profit from it.

Stop-losses are very important in investing but I'd recommend always executing them manually at market rate. Set a price alert to notify you. Of course if the exchanges are down you're sol, but if BTC is on a bullet train to $10 your exchange stop-loss probably won't fill at your price anyway.

Interesting thought experiment. If beggars accepted NFC payments I bet they'd make a lot more money.

I really like this idea. It's a relatively simple approach that could work with any fs/backup strategy. It would be great if it wasn't dependent on Time Machine.

ZFS/Raid + ECC ram are complicated and expensive and are not even a 100% guarantee against bit rot.

The real gut punch is many parts of this tutorial will probably be obsolete within six months. Fast forward a couple years and this will look like the equivalent of "Backbonejs tutorial - Step 1: bower install requirejs".

Sometimes I feel bad complaining about this. Things are evolving fast for a reason. Everyone is trying to make every part of this process better. The backbone joke above illustrates the point. Would you go back in time and freeze the evolution just to regain sanity for today's devs?

This is very close to what I'd consider the ideal photo organizer. However there's a feature I'd like to see that I'm not sure is possible without a database. Tell me what you think.

How does this handle dupes and near-dupes? People have photos scattered all over. Can I throw a random old folder of photos at this and trust that it won't overwrite an otherwise identical jpg with a bit-rot corrupt one for example?

You mention idempotence in your blog post, if I run this twice using the same 'unorganized' source folder, will it copy all the files again the second time?