the notation is just an array of move tuples, each tuple contains 1 move for white and 1 move for black, where each move is written as <1st letter of piece name><destination square>
> In this Friday’s magic demonstration, I’m going to show how what you see in Privacy & Security settings can be misleading, when it tells you that an app doesn’t have access to a protected folder, but it really does.
Yeah, but don't expect this level of fine granularity from government, any government, thats ridiculous expectations. Heck, I wouldn't expect it neither from any private company as a default state.
I wouldn't expect it from any goverment either, but I would expect it from someone who allegedly read the story and is trying to share relevant information.
My first focus is sharing, search and discoverability.
The biggest issue is that I have thousands of photos but I don't have a good way of filtering by person, date, location, and finding exactly what I'm looking for. Basically browsing my photos like I would browse an online store like Zalando. Search for something and refine with filters.
In addition - I implemented S3-like storage. Makes it cheap and easy to host in the cloud.
It feels so disrespectful sometimes too, having to read a long paragraph that conveys so little meaning knowing full well the original prompt was probably very short and I'm now wasting extra time parsing the hollow LLM text expansion.
That's absolutely what's happening already: write for me for the writer, summarise this for me for the reader. At some point it will become clear how absurdly wasteful we're being (right now, we're being paid to ignore that waste).
> write for me for the writer, summarise this for me for the reader.
It's funny though. For computer to computer conversation, we have invented (deflate+inflate) algorithms to save bandwidth, time and money.
On the other hand for human to human communication, we are in the process of inventing a (inflate+deflate) method and at the same time we are spending insane amounts of time, money & bandwidth to make it possible!
We need to come up with a catchy buzzword salad to market to executives. Something like "increased communication efficiency between workers by direct brain-email-brain interface"
Also the maintainer's ground-up rewrite argument is very flimsy when they used chardet's test-data and freely admit to:
> I've been the primary maintainer and contributor to this project for >12 years
> I have had extensive exposure to the original codebase: I've been maintaining it for over a decade. A traditional clean-room approach involves a strict separation between people with knowledge of the original and people writing the new implementation, and that separation did not exist here.
> I reviewed, tested, and iterated on every piece of the result using Claude.
> I was deeply involved in designing, reviewing, and iterating on every aspect of it.
reply