I’ve been noticing a pattern in Ukraine supporters in Europe in that many of them are actual closeted Nazis from Germany who hate Slavs and see Ukraine (or at least Galicia) as being of Germanic, whom they’d consider “Aryan”, and not Slavic stock.

Two different capacity expansion announcements today across $TSEM and $AAOI. Tower Semi, supported by the Japanese government, announced expansion of its 300mm Silicon Photonics (SiPho), Silicon Germanium (SiGe), and advanced packaging capabilities. Targeting $1.2B net profit, and $3.6B revenue in 2028 (with a ~$28B MC, that's ~23.3 2028 forward p/e). AAOI announced the commencement of its buildout, roughly 400,000 square feet of manufacturing to make 800g/1.6T production go brrr. The overall expansion is also supported by the local city government in Texas. (they also $20.85M worth of subsidies from the State earlier). This one isn't exactly as materially new as Tower, since AAOI originally announced these plans before. Just commencement of it. Regardless, glad to see both of these companies in their Anime training arc phase as they power up.

Oktoberfest with Eva. The dirndl doesn't stay on. 🎬 🎬 #oktoberfest# #dirndl# #germangirl# #aiwaifu# #aigirl# #aibabe# #aiporn# #aigenerated# #nsfwai# #nsfw# #porn# #adult# #pov#

The saddest Book Cover series in history... The History of the Decline and Fall of the Roman Empire is a monumental historical work by Edward Gibbon, published between 1776 and 1789, that traces the long collapse of the Roman Empire from its height in the 2nd century AD to the fall of Constantinople in 1453. Gibbon argued that the empire declined gradually due to a combination of internal weaknesses and external pressures, including political corruption, economic troubles, military overexpansion, reliance on mercenary forces, and invasions by Germanic and other groups. One of his most famous and controversial ideas was that the rise of Christianity shifted focus away from civic duty toward spiritual concerns, weakening traditional Roman institutions. The book is still widely read for its narrative style and scholarly influence, even though many of its interpretations have been revised by modern historians. #archaeohistories#

What’s it like getting a haircut at a regular Shanghai barbershop when your Chinese is not so good? 😂 This German guy’s haircut vlog is packed with heartwarming conversations, local vibes, and check out how great the haircut turns out to be. #ShanghaiLife# #ChinaVlog# #GermanInChina# #BarbershopStories# #LanguageGoals# #48thWordSkillsCompetition# Video cr. 付瑞赛

As agents become the biggest users of software, then all software has to be available in a headless fashion. Agents won’t be using your UI, they’ll be talking to your APIs. So the question becomes what is the business model of software and this headless approach in the future? Here are a few thoughts on how everything plays out based on what we’re seeing and doing at Box, but also conversation with other platforms. 1) Seats don’t go away for *people*. Seats are still a convenient and efficient way to have a customer use technology predictably for a set of users within a baseline set of usage. The key, though, is that when the customer pays for a seat, it has to come with a set of usage of APIs on behalf of that user that the agent can use on their behalf. The user will need to be able to interact with their data and the underlying tool via any agent they work with, and an embedded amount of usage will come with the seat. I would imagine most software -Box included- will enable seats to work with their data at a relatively high volume via systems like ChatGPT, Codex, Claude, Gemini, Cursor, Copilot, Perplexity, Factory, Cogniton, et al. quite seamlessly. If you don’t do this, you’re DOA. 2) Agents may have “seats” if they are doing stateful work in the system, but they will be priced very differently than people. Seats (or the equivalent) can make sense when you have an agent that has its own workspace, stores its own data, needs a different set of permissions compared to the user, and so on. If a company wants this agent to be around for long period of time, that may very well look like another “user” in the system. Openclaw-style agents highlight what this future could look like. The only issue on pricing here is that one customer could decide to do all their work in 1 agent, and another might split it into 1,000 agents. So pricing like a human seat is nearly impossible and impractical; each company will have a different approach for this as it gets tricky perfectly trying to capture all the value within an agent seat. 3) The dominant pricing for headless use that goes above the seat allotment, or when an agent is firmly acting on their own, will be a consumption model. Many enterprises software platforms have previously operated like this with PaaS options, and agents will look like another machine user of their system. In some cases the APIs might get priced just as they did previously, but in other cases there may need to be new types of APIs that represent the work an agent would do in one go -more akin to an outcome- instead of a series of API calls. This is especially germane when the headless software also has an agentic use-case embedded within in, such as orchestrating the process within their own system via AI. Overall the growth of this usage pattern is effectively unbounded as the use-cases for agents operating on data in these systems will dramatically exceed what people do with their data and tools today. Every platform that goes headless (which will be anyone that wants to take advantage of agents) will need to adopt a model like this. Some may fight it initially but it’s an inevitably as there will always be more and more agents outside your platform than people. Overall, there’s a lot of really interesting changes left to come in software due to headless use of these systems. Early days.