#weeklyreview 08/2025

geez … I’m late with my review again….

Last week was a quiet one, with my friend Sam returning from her trip to Australia. We caught up and got back into our regular gym routine.



Our Sunday winter swimming sessions took place as usual, but this time we had to clear a patch of ice from the lake to get in the water. The ice was 5cm thick and needed to be cut through using axes. We managed to create a small path into the lake, which we used for our short dip. The water temperature was around 0.5-1°C, but it wasn’t too bad once we were in.


The rest of the week was spent experimenting with the Ollama tool. I’ve been testing various machine learning models and user interfaces, trying to get a better understanding of how they work. My goal is to set up a local installation of a LLM (Large Language Model) with Retrieval-Augmented Generation (RAG), which will allow me to securely work with my personal documents.

Thursday was again family dinner time and I made veggie wraps. Fried the fancy looking Enoki mushrooms. They are trick to eat without cutlery. Much too stringy and hard to chew off. Not recommended for wraps


Overall, it’s been a productive week, but mostly focused on testing and experimentation rather than any major achievements.

Adding Environment variables to services in home-brew

I’ve recently install Ollama on my MacBook and need it listen on all network interfaces. The default installation view Homebrew brings a service description for home-brew. And the default behaviour of Ollama is to listen only on localhost. I need to add an environment variable to the Ollama command to make it listen on all interfaces.

The service description for the home brew formulae of Ollama can be found in /opt/homebrew/opt/ollama/homebrew.mxcl.ollama.plist

I search for documentation of this file but could not easily find one. Eventually I had to turn to ChatGPT and that gave me the correct solution.

I needed to add the following structure to the .plist file:

<key>EnvironmentVariables</key>
  <dict>
    <key>OLLAMA_HOST</key>
    <string>0.0.0.0</string>
  </dict>

Then after a restart via brew services restart ollama the service was finally listening on all interfaces.

The Return of Infrastructure Independence: Breaking Free from US Hyperscalers

In the rapidly evolving landscape of technology, we sometimes find ourselves experiencing a sense of déjà vu. The current state of cloud computing and infrastructure management feels remarkably similar to the late 1990s server market—a time of major technological transition that ultimately rewarded those who maintained traditional expertise.

The Great Windows Server Migration of the Late ’90s

Cast your mind back to the late 1990s. Windows NT was gaining significant traction in the enterprise server space. Microsoft’s marketing machine was in full swing, promoting Windows as the future of server technology. The interface was familiar, the management tools were accessible, and the promise was enticing: simplify your infrastructure and reduce costs.

Many companies bought into this vision. They let go of their Unix administrators—the wizards who understood the deep intricacies of system architecture—and pivoted toward the seemingly more accessible Windows ecosystem. Unix expertise was deemed outdated, a relic of computing’s past.

But then something unexpected happened: Linux emerged as a powerful force. This open-source Unix-like operating system combined the robustness of traditional Unix with modern development approaches. Companies that had maintained their Unix expertise found themselves with a significant competitive advantage, while those who had discarded that knowledge scrambled to adapt.

Today’s Dangerous Dependency on US Hyperscalers

Fast forward to today, and we’re witnessing a similar phenomenon, but with far greater geopolitical implications. The cloud market has become dominated by a handful of US-based hyperscalers: AWS, Azure, and Google Cloud Platform. These giants now control the backbone of global digital infrastructure, creating an unprecedented level of dependency.

Organizations worldwide have entrusted their mission-critical systems, data, and intellectual property to these American corporations. This concentration of digital power in the hands of a few US companies presents significant risks:

  1. Geopolitical Vulnerability: Non-US entities are subject to American data regulations, surveillance capabilities, and political whims
  2. Sovereignty Concerns: Nations and regions have limited control over their own digital infrastructure
  3. Single Points of Failure: Global dependence on a handful of providers creates systemic risks
  4. Compliance Challenges: Navigating complex and sometimes contradictory regulations across jurisdictions

Today’s developers and systems engineers often have limited exposure to building and maintaining independent infrastructure stacks. The knowledge of creating self-sufficient, sovereign digital platforms has been sacrificed at the altar of convenience offered by the hyperscalers.

The Coming Era of Regional Digital Sovereignty

As geopolitical tensions rise and concerns about surveillance escalate, we’re approaching a breaking point that parallels the Linux revolution of the early 2000s. The excessive centralization of cloud infrastructure in the hands of US corporations is becoming increasingly untenable for many regions and organizations around the world.

Europe, in particular, stands at a crossroads. With its strong regulatory framework through GDPR and emphasis on digital sovereignty, the continent has the potential to lead a shift toward regional cloud infrastructure. A “European Cloud” built on open standards and operated independently of US hyperscalers could provide a template for other regions seeking digital autonomy.

This is where those 50+ year-old systems engineers—the ones who understand how to build infrastructure from the ground up—will become invaluable again. Their knowledge of architecting complete technology stacks without reliance on hyperscaler ecosystems will be crucial as organizations and regions work to establish independent digital capabilities.

Building Regional Digital Independence

The path to reducing dependency on US hyperscalers requires:

  1. Regional Infrastructure Initiatives: Government-backed programs to develop sovereign cloud capabilities within specific geographic or political boundaries
  2. Open Source Foundations: Building on open source technologies to avoid vendor lock-in and enable collaboration
  3. Knowledge Preservation: Actively maintaining expertise in full-stack infrastructure management
  4. Hybrid Approaches: Developing gradual migration paths that balance hyperscaler advantages with sovereignty requirements
  5. International Cooperation: Creating alliances between nations with shared interests in digital sovereignty

The Role of Experienced Infrastructure Engineers

The systems engineers who remember a world before AWS, Azure, and Google Cloud will play a pivotal role in this transition. Their experience building and managing independent data centers, designing network architectures without reliance on hyperscaler services, and understanding the full technology stack from hardware to application will be essential.

These veterans know what it takes to build robust, independent infrastructure. They understand the pitfalls, requirements, and strategic considerations that younger engineers, raised entirely in the hyperscaler era, may overlook.

Conclusion

The technology industry has always moved in cycles. What seems obsolete today may become critical tomorrow. Just as Linux vindicated those Unix administrators who maintained their expertise through the Windows NT revolution, the growing movement toward digital sovereignty could similarly elevate those who’ve preserved their knowledge of building independent infrastructure.

As regions like Europe work to establish their own cloud ecosystems and reduce dependency on US hyperscalers, the experienced systems engineers who understand how to build truly independent technology stacks will become not just relevant, but essential to our digital future.

The coming years may well see a renaissance of regional infrastructure expertise, as organizations and nations alike recognize that true digital resilience requires breaking free from excessive dependency on the American tech giants that currently dominate our global digital landscape.

See also: https://berthub.eu/articles/posts/you-can-no-longer-base-your-government-and-society-on-us-clouds/

#weeklyreview 07/2025

Not too much going on in week 06. The highlight certainly was the birthday of our daughter. Finally a real teenager. She had wished for a New York Cheesecake and surely got one.



To celebrate she took a friend over to our house in the countryside and we went to the NaturTherme Templin for the Spa and Sauna. Since we got there early it was empty and I had the first two session of sauna all for myself.

Got some reading done and a total of 4 sauna session.

Monday was again family dinner day and K1 was over for and stayed for a session of Trival Pursuit.

Mid week it started to snow seriously in Berlin and by Thursday we had about 15cm of snow. As it was also cold enough the snow stayed and nicely covered the city in a white blanket. That also amazingly quieted down the whole city.

Friday my best friend Sam was back from her long trip to Australia and we had breakfast together. Sooo good to have her back.

Fixing PaperlessNGX Email Processing Issues After Restart

When running PaperlessNGX in Docker, I encountered an issue where certain emails were not processed after restarting the Paperless container in the middle of a batch processing operation. Paperless saw the emails in the inbox but incorrect

ly marked them as already processed.

Identifying the Issue

The first step to diagnose the issue was to check the mail.log file within Paperless. The log provided information on which emails were skipped from processing, including their unique IDs. For example:

[2025-02-17 09:50:03,084] [DEBUG] [paperless_mail] Skipping mail '321' subject 'Email from Epson WF-4830 Series' from 'scanner@example.com', already processed.

Logging into the Database

To access the Paperless database running inside a Docker container, I used the following command:

docker compose exec db /bin/bash

This command opens a bash shell inside the db service container, allowing further interaction with PostgreSQL.

Resolving the Issue

To resolve the issue, I connected to the Paperless database, which was running on PostgreSQL. Using the provided email UID from the mail.log, I deleted the corresponding entries from the paperless_mail_processedmail table to allow Paperless to process the email again.

psql -U paperless_db_user

Here’s the SQL command I used:

DELETE FROM paperless_mail_processedmail WHERE uid = '322';

After running this command for every of the reported mails that are skipped, Paperless successfully reprocessed the emails during the next processing cycle.

Conclusion

If you encounter similar issues with PaperlessNGX not processing certain emails after a restart, checking the mail.log and manually deleting the processed mail entries from the database can be an effective solution.

#weeklyreview 06/2025

Again a mixed week

Took Monday off to drive a friend to an examiner for his insurance to assess that he’s not capable of working in his job. He’s got severe ME/CFS, can’t sit or stand upright without passing out in a matter of minutes, has the attention span of squirrel before his brain fog kicks in etc. The examination was originally meant to be 2 days of 4 hours examinations each. But it was clear from the start that he’d not be able to do that. The bloody examiner sit’s in a non-accessible building in the south of Berlin. My friends needs a wheelchair to move around. Of course the building neither had an elevator nor a ramp or something. So it took my friend about 25 minutes to rob in his bum up to the 3rd floor. Yeah… because he can’t stand upright and just walk. And he’s also a bit heavy so can’t be easily carried. And our brilliant health system also does not pay for transport and carrying him upstairs anymore. You’d need three persons to move him, but the default staff on official ambulance cars is only two.

Overall a rather humiliating and exhausting experience for him. I’ll just hope that he’ll finally get’s the deserved payout from his insurance.

The good thing was though, that I 4 hours to roam around in Friedenau and was able to give my good friend Boerge as visit in his new home 😀

Tuesday & Wednesday I was fighting with work bureaucrats the get an exemption for using my corporate USB Disks to free off space on my internal hard disk for experiments mit LLM models. I get the need for rules and restrictions etc. But there must be a way to not prevent people from doing their work. There is all this mandatory security training and tools etc. But I think there should be a way for people to somehow prove that they know what they’re doing and get rid of the usual corporate shackles that prevent you from doing stuff and cripple your expensive corporate hardware.

Baltic Sea

For the rest of the week (which was the Berlin winter holiday week for schools) my daughter and me took off to Usedom island. This time we stayed in Świnoujście on the polish side of the isle.

The weather left room for improvement the first two days with grey clouds, cold wind and drizzle. But that’s kind of what we came for. The sea is awesome at any weather and our hotel had a Spa area where we spent time in the pool and sauna 🙂 I also got a fair bit of reading done on my kindle in the sauna. “The dawn of everything” is really good.

We explored the local restaurants and roamed around the city, beach and piers a bit.

On Saturday we took a trip to the German side and payed Gulliver a visit and had good pizza on the pier restaurant in Heringsdorf.

In the afternoon the sun finally came out and people were flocking to the beach for a walk. We saw the TF Line ferries coming in and eventually had really good Sushi at the Hilton Hotel Sushi Bar and Grill.

Overall a rather relaxing four days at the Baltic Sea.

But there was not a single node on the whole Baltic Sea. I was carrying my T-Echo the whole time to check for any nearby radios. Nothing, nada, zilch.

#weeklyreview 05/2025

Pretty nice run on Sunday with a friend. The little pond in the forrest was still frozen. Swans on the lake showed us their lift-off skills. And finally some cranes were screeching in the flooded meadows of the other village.

Went swimming right after the run and it was …. freaking cold. Water hat around 2ºC. My Apple Watch decided that that’s too cold to operated and turned off. Fortunately only after I finished the swim and the recording of the session.

Beers with a friend

Sunday evening I went out for beers with a new friend. US American, teacher of art. Was a lovely evening and we had lots of fun talking about the good old early days of desktop publishing. Turns out he’s one of the people who have used Aldus PageMaker in the early/mid 1990s before it was bought by Adobe and layed the foundations for Adobe InDesign.

Dinner

Monday evening the oldest kid came over for dinner and we made roasted potatoes and broccoli/cauliflower casserole. Looks like we’re making these dinners a regular thing now. Nice 🙂

BBQ Ribs

Wednesday was finally time for another session at Chicago Williams BBQ with the colleagues. Still some of the best ribs I ever had.

The little pond

We have a little pond in the forest we own. On Saturday we went checking whether it had gained some water in the last weeks of substantial rain. And it did. Back in autumn last year it was almost completely dried up and only a few puddles and mud at the ground. But now it looks like a pond again. It’s only about 50cm deep water at the moment. But the surrounding deer and boars like it.

Let’s hope it get still some more before they dry season starts.

Antarktis

On Saturday our little village society organised a film evening by a German Astro particle scientist about Antarctica. He had been there several times to carry out Neutrino detection experiments. He also showed us some films of the Antarctica Film Festival and we learned that the German Neumayer Station III is one of the most modern on the continent.