I can’t say if the servers themselves reside on US soil but the companies office certainly is, while I admit I was hesitant to give them my money I got tired of being rate limited by Bing/DDG/Startpage on my SearXNG instance, even though I don’t make many requests they do not like aggregator engines, and I sure as hell didn’t want want my server touching Google servers regularly.

Settled with the least worst option available I’d say.

@lowqualityfacts and they caught a cab

Train ride through Switzerland (Brail - St Moritz - Poschiavo): https://www.youtube.com/watch?v=24GNVCriYJM&t=3016

#trains #webcam #switzerland

Ford Ranger WildMac

You have no idea how much I wish I could fit this in my profile picture

Bummed that you can’t seem to catch a break with the server suffering from separation anxiety and throwing a fit every time you leave for work.

Artistic rendering. (had to use catbox since lemmy.cafe doesn’t seem to allow image uploads?)

Base image courtesy of @undthr@horp.sciops.net .

Yeah fair enough. I agree, annoying on your end about the expense.

Bummed that you can’t seem to catch a break with the sever suffering from separation anxiety and throwing a fit every time you leave for work.

That's crazy.

Over a decade of running at a loss. That is only possible for companies, like Google, that are already very rich.

Due to the LLM scrapers I have been thinking that I might have to move to a hybrid system of going through a VPS with only some storage and compute services on my home servers remaining. It is an annoying expense of about 20€/month that I was hoping to avoid, but it will give some other benefits like a fully fixed IP, IPv6 support and DDOS protection.

In such a setup the service would degrade better, like images breaking, but the main service staying up when my home server goes down.

But it is not something I can setup now that the service is already inaccessible.

Be really nice to build some local community so that you can both self host and have this kind of support if you need it

Would be nice, yes. But easier said than done 😓

I think a more realistic option is to move my self-hosting ambitions down a notch and only focus on more redundand backend services that are too costly on a rented VPS.

poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixanle with a remote server restart) until the second I go on a longer business trip and can’t easily access the hardware.

Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn’t the same problem again as in 2025.

What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.

My weight, sent from my own bathroom floor to my own phone, is a strange thing to rent back to me.

Before I bought any connected scale, blood pressure cuff or watch, I'd check three things: whether syncing to Apple Health or Google's health app needs a paid plan, whether I can export my full history as a file, and what happens to that data if I stop paying. Withings still lets every user export a full history as a CSV or PDF, iThinkDiff reported. If you already own a Withings device, I'd hang on to that account, because the exemption follows the account, not the device.

Either is a fair reason to charge for a service on top of the device.

The rule also covers other apps that pull data through Withings' free developer plan, including apps already on the market, iDevice reported, and new users can't get around it by routing their data through Apple Health or Google's system instead. A thread on Withings' own community calls the change unacceptable right in its title.

🌨️ 🌨️🌨️ 🌨️
🏙️🏙️🏙️🏙️🏙️🏙️🏙️🏙️🏙️
🏘️ 🏦🏗️🏘️🏠
🚈🚋🚋
🏪 🏡🏢🏘️🏠 🏘️ 🏬
🚚🛵 🚚 🚲

iThinkDiff reported that a new account on Android also needs it for automatic transfers to Health Connect. A reply marked as Withings' official response, quoted by Engadget, says "automatic sync to third-party apps is part of Withings+."

Gadgets & Wearables reported that Withings says subscription revenue helps fund clinical validation, regulatory work and the infrastructure behind it, and iThinkDiff reported Withings ties the change to API updates and new privacy measures for its AI connector.

Withings wants about $100 a year to sync your scale with Apple Health...

Anyone who creates a Withings account on October 13 or later needs a Withings+ subscription for automatic syncing to Apple Health, MacRumors reported, at $99.50 a year in the U.S. Tech Between the Lines found the App Store listing at $9.99 a month or $99.99 a year. Accounts created on or before October 12 keep syncing for free.