Article 50 of the EU AI Act is already live, and the one grace period in it is narrower than most summaries make it sound.
Article 50 of the EU AI Act became generally applicable on 2 August 2026, and national authorities can enforce it now. It applies whatever your risk classification is, which is the part small teams tend to miss: you do not need to be a "high-risk" system to be covered. The Digital Omnibus that entered into force in July did not change the substance of these duties, according to the law-firm write-ups I read (Goodwin, and Ropes & Gray).
Cheaper near-frontier models make it tempting to send more context on every call. For anything personal, that is the wrong place to spend the savings.
OpenAI announced GPT-6.1 Sol at DevDay on 2 October. Its API page lists $2.00 per million input tokens, $0.10 for cached input and $10.00 for output, with a 1,050,000-token context window. Prompts over 272K input tokens are billed at double the input rate and 1.5x output for the whole request. OpenAI says the model gives near-Astra intelligence at a fifth of Astra's price. That comparison is OpenAI's own claim about its own product, and I haven't seen an independent benchmark of it, so treat it as marketing until someone you trust has run it on your workload.
The same event added computer use to the Agents API, so an agent can operate software through its interface, available through the API and in Codex and ChatGPT Work on Pro 500 and Enterprise plans.
Here is what I think a small team should take from it. When the per-token price drops, the first instinct is to spend the savings on more context: send the whole history, the whole document, the whole account. The model can take a million tokens, so why not use them.
For months, we celebrated our power users at Murror the ones journaling every day, sometimes multiple times a day. They had the highest session times, the most entries, the best retention curves. On paper, they were our success story.
Then we started reading what they were actually writing.
From 1 October, leaving Apple In-App Purchase drops a Small Business Program developer from 15% to 10% in the EU. On a 4.99 euro subscription, a processor's fixed per-transaction fee can eat most of that on its own - and your choice locks for 12 months.
Apple updated the Developer Program License Agreement on 18 August, and the new EU business terms go into effect on 1 October. The coverage I've read frames it as Apple finally opening up. That's true in a structural sense and mostly irrelevant to anyone running a small subscription app, because the interesting question isn't whether you can leave Apple's payment system. It's whether the arithmetic works. For most of us it doesn't, and it's worth being able to say why rather than just having a feeling about it.
Everyone tells you to ship fast. Move fast and break things. Get to market before someone else does.
I believed this for a long time. When we were building Murror, speed was everything. We pushed features weekly, sometimes daily. We celebrated every deploy like a small victory.
The legacy "Block AI bots" switch is deprecated on 15 September, and mixed-purpose crawlers get folded into it. Googlebot, Applebot and BingBot are in scope. Opting out is one click and the window is 25 days.
Sometime in the last two years a lot of us flipped a switch in Cloudflare called "Block AI bots." It was one click, it was free, it was framed as protecting your content, and there was no reason not to. I did it. I never thought about it again.
Google started enforcing app registration in four countries three weeks ago, and the rollout widens in 2027. Most Play apps were registered automatically, but "most" is not the same as "yours".
Google's Android Developers Blog (18 June 2026) set 30 September 2026 as the date developer verification protections begin, starting with users in Brazil, Indonesia, Singapore and Thailand, on certified Android devices. Google's developer verification page says it expands globally in 2027 and beyond.
For months, our most requested feature at Murror was a chat function. Users wanted to talk to the AI the way they talk to a friend. It seemed obvious. Every competitor had it. Every feedback form mentioned it.
When we first built Murror, we stored every journal entry forever. More data meant better emotional pattern detection, smarter insights, richer reflections.
Our AI kept getting better. Our users kept getting quieter.
