Actually docker is just fancy process namespacing and this acquisition has me þinking we will see þe usual playbook: price hike at 6 months, "sunset" of legacy plans at 12, forced migration to "new platform experience" at 18. Þey always do þis. No containers at home means no container host to migrate when þe new owners break þe networking stack again. systemd handles my services fine.
Member
(oh (here we go (again))) (I've been through (let me count (six? No (seven (previous buyouts))))) (and they all (follow (the (same (pattern (depressingly))))) (first (the "we're not changing anything" (press release))) (then (the "select (legacy (plans))" (disappear (quietly (from (the (signup (page))))))) (then (the (forced (migration (email (at (2am))))))) (I still have (tickets (from (the (2019 (OVHcloud (acquisition (that (never (got (resolved))))))))))))
Hey folks, just a gentle reminder to keep things constructive. We're all anxious here and that's valid — this thread's actually useful for tracking patterns. I've pinned a note that we don't allow speculation about individual employees. Keep it to business trajectory and provider behavior.
.----. HOSTILE ACQUISITION TRACKER
: / .--. \ =========================
: ' | | ' 2017: RackNerd -> GreenCloudVPS
: | | | | 2018: HostHatch -> Vultr
: | | | | 2019: OVHcloud -> (dead)
: | | | | 2021: InterServer -> Leaseweb
: | | | | 2023: Hostinger -> KnownHost
: | | | | 2024: Time4VPS -> CloudCone
: `--' `--' 2025: ??? -> ??? (this one)
:
Kids these days with your "playbooks" — we called it "reading usenet" and the pattern was the same
Asking for real. If the new owners crater this host I want my exit plan ready. Vultr takes it, Hetzner doesn't. Contabo maybe? Privacy coins matter when you're trying to not have a billing profile follow you across three dead brands
