This is like the Bronze Age collapse when city-states fell one by one to displaced demand, under the refugee interpretation of the Sea Peoples.

Interesting, I had not heard of this theory.

The Sea Peoples were only a part of the reason, the other reasons included climate change, volcanic eruptions, disease etc. https://en.wikipedia.org/wiki/Late_Bronze_Age_collapse

Can anyone recommended any books?

The historian Brett Devreaux did a good summary article earlier this year:

https://acoup.blog/2026/01/30/collections-the-late-bronze-ag...

1177 B.C.: The Year Civilization Collapsed by Eric H. Cline is great and is exactly on this topic.

I read that book earlier this year and really enjoyed reading it. The audiobook was also spoken by the author.

Also from Cline: After 1177 B.C.: The Survival of Civilizations (2024), ISBN 978-0691192130

For a TLDR https://youtu.be/aq4G-7v-_xI?si=7yNv6FKuGfqbz_rv is generally beloved

They sound exactly the same to me.

Wiktionary gives <should've> as /ˈʃʊdəv/, unstressed <have> as /(h)əv/ and unstressed <of> as /əv/.

one is v the other is f

Spelling is no guide for pronunciation here, though. In North American and Commonwealth dialects of English I don't think there's a context in which the <f> in <of> is really pronounced as a [f]. It is rather a [v].

Only in South Asian varieties of English apparently: https://en.wiktionary.org/wiki/of#Pronunciation

The best of both worlds would be achieved by elastic tabstops. https://nick-gravgaard.com/elastic-tabstops/

If only they took off.

And these are the guys who invented transformers! How?

Invented, failed to make a good product out of it.

Well, estimating string length of tokens is much like counting R's in strawberry.

There's a reason it stands for Bring Over Another Thousand

Yeah referencing is the way to go, as even finetuning probably captures style more than concrete facts. I know with large context windows we don't really RAG anymore, but for owner's manual lookup with a smaller model it seems ideal.

Something every LLM user ends up learning is that they're far better used as search and summarization tools than as knowledge databases in themselves.

The hard part is finding the correct owners manual. Also in many cases the owners manual is generic and covers many options and trim levels.

Edit: this applies to service manuals too

A model's internal knowledge is great! It's useful as initial priors to speed up the REAL search.

But comments should hopefully explain "why", not what or how, and that kind of context is exactly what an LLM is likely to be missing

Yes, but some of that is actually better placed in the git commit messages. But of course not all.

I guess it would need permissions, but you can monitor the photo library with PHPhotoLibraryChangeObserver and check if a new item's subtype is photoScreenshot.

Otherwise userDidTakeScreenshotNotification only fires for your own app

The app actually is notified after the screenshot is taken: https://developer.apple.com/documentation/uikit/uiapplicatio...

Android does it too: https://developer.android.com/about/versions/14/features/scr...

This prevents us from taking scrolling screenshots (a native feature in many smartphones today that is often useful when there is more than one screen of content).

I dislike this hijacking for that reason and wish there was a way to turn it off.

Spotify uses this and it annoys me all the time.

If you screenshot what you are listening to, after the screenshot is taken spotify will open a full-screen popup to "share" the song you are listening to. This is quite dumb, especially since if you wanted to share a song via the screenshot, you can do so in the OS-level screenshot UI, and then you would close it and see Spotify's own similar version of the same UI. Spotify just really wants you to use their own share button so that they can track you.

I’ve seen another app do that but for a different reason. It’s for security cameras and they use it to show a “hey idiot just press the save a picture button, don’t take screenshots” popup, which is also hostile.

I’m not sure why the app needs to be notified. There must be some use but I can’t think of it off the top of my head.

Yeah it’s Snapchat. If you take a screenshot of a (potentially extremely private, intended to be ephemeral) image, it notifies the person who sent it.

Anyone can take a "snap" of the phone screen with another phone's camera so this is a losing battle anyway.

It amuses me that browsers in incognito mode refuse to allow screenshots on mobile. But same browser running incognito on a desktop can be merrily screenshotted. What is the difference they are trying to enforce based purely on device form factor/OS.

Actually I was referring to the Eufy app. How nice there are others.

> I’m not sure why the app needs to be notified. There must be some use but I can’t think of it off the top of my head.

My pet theory: it's because Snapchat got big early, platforms added the feature to facilitate Snapchat's business model, and then banks started abusing it, and it stuck around "because sekhurity".

Yes, it is very annoying. But I think they are already tracking you.

They want use to use the share button so your recipient is more likely to open Spotify (or whatever app) themselves.

Correct.

Though I don’t see how this is anything like a keylogger.