Make us three. My lack of ethic flexibility skills really held me back

Somewhat related but I always wondered if I asked a LLM to create a new language with full focus on LLM coding efficiency, ignoring the need for humans to read it, what would it come with? Binary?

...and I obviously asked Gemini about it and it replied:

"A language optimized exclusively for Large Language Model (LLM) efficiency would prioritize Token Density, Context Window Management, and Architectural Alignment. It would not be binary, as standard LLM architectures (Transformers) process discrete tokens from a predefined vocabulary, not raw bits."

Example of it:

  Feature        Human-Readable (Python/C++)       LLM-Native (Hypothetical)
  --------------------------------------------------------------------------
  Logic          if (x > 10) { return true; }      ¿x10†
  Memory         int\* ptr = malloc(sizeof(int));  §m4
  Tokens Used    ~10-15                            2-3

The issue with these LLM-targeting DSLs is that you have to waste a bunch of your context window explaining the grammar and semantics to the LLM, whereas they already speak existing programming languages because they've seen so much existing code. This usually negates the benefits of the DSL.

So Perplexity's openclaw? Hopefully more secure?

> So Perplexity's openclaw? Hopefully more secure?

Given the inherent unpredictability of LLMs, I'm not convinced that an openclaw-like system but with more security features bolted on top is really a positive in the sense that the false sense of absolute security probably outweighs whatever actual security has been added.

It is easier to understand that openclaw is definitely insecure.

Exactly. Psychosis (and other mental illnesses) will find something to attach itself to. The opportunity here is for Google and other LLMs to include safeguards (and be very clear about them) and processes to direct the user, or, in extreme cases, direct health services to avoid a tragedy like this.

That is not new, just new with APIs.

The usual cycle with startups is to:

- Start being very open, as this brings people developing over the platforms and generates growth

- As long as they are growing, VC money will come to pay for everything. This is the scale up phase

- Then comes the VC exit, IPO or whatever

- Now the new owners don't want user growth, they want margin growth. This is the company phase

- Companies then have monetize their users (why not ads?), close up free, or high-maintenance stuff that do not bring margin

- and report that sweet $$$ growth quarter after quarter

...until a new startup comes in and starts the cycle over again, destroying all the value the old company had.

A mix of Enshittification and Innovators Dilemma theories

Some time ago I configured Photostructure on my Synology (with the amazing help of the author, @mceachen) and the most paindful part was rescuing my 1.5TB of photos from Google Photos. Takeout was very cumbersome to use and download 100+ files of 4gb, so ultimately resorted to paying a higher tier at Google Drive, using takeout Google Drive option and the sync to the NAS. I still don’t have a good method to keep everything in sync as Google Photos does not offer a viable option for a cloud-to-premises sync.

I wrote some tips and tricks that I've found to help coax Google Takeouts into working: https://photostructure.com/faq/takeout/

Also: you should try out the latest build! https://photostructure.com/about/v2026.1/

FWIW all of these projects rely on ExifTool (which people should donate to!) and my open-source node.js wrapper (that adds concurrency, does a ton of extra parsing work, and makes things a bit more ergonomic to live with): https://github.com/photostructure/exiftool-vendored.js

For what is worth, google takeout can export in 50GB tgz.

Downloading the takeout files is miserable through, the download link is only valid when being downloaded via human interaction in a web browser.

There is a silly trick. Start the download, pause it. Get the cookies from the page (only need to do that once for the session). Then copy the download link. Now you can curl on your server. When the file is downloaded, you can then cancel the download in your web browser. And do the same for the next file. One at a time.

Warning: google will cancel downloads if you run more than one or two at a time. After 3 download (failed or not) of a file google will delete the whole takeout.

The amount of engineering they must have deployed to purposefully crimple takeout with plausible deniability must be significant.

This makes more sense. I hate when people talk about taxing the “net worth” of some rich guy when a good part of that net worth is locked into invested companies who are (hopefully) being taxed already. The borrow scheme should be the thing being taxed really, because is a shadow realization of profit (they are borrowing against the current value of their assets)

This won't be a problem when Apple migrate all macs to OLED as blacks will be true black (no light). I have a Samsung SD95 that has a glare free chemical coating and it is amazing on rooms with too much light with no greyish black on low light conditions (at least from my personal experience).

No, matte screens having nothing to do with the underlying contrast.

The blacks are getting washed out from light in the room that is diffused by the matte finish. Not light coming from the pixels.

The final black contrast is limited by both the underlying pixel technology and the screen finish. You get true black only with both OLED and glossy.

Not necessarily as gemini might take other variables in consideration. But it certainly will make a lot of intermediaries (between brands and consumers) suffer. This is a huge threat for Amazon.

Well onedrive is nothing more than sharepoint disguised as a cloud drive. So they adapted a legacy pre-cloud era code to create a competitor to dropbox and google drive. Imagibe how well that code works…