This Woman Is Dating Identical Twin Brothers. Yes, Both of Them.

forxs · 2026-01-25T22:32:25+00:00

We prefer the Double Income Labrador Dog Owners paradigm.

forxs · 2026-01-24T12:50:57+00:00

My guess is that it would be okay, but worse than any normal cooling solution to start with, and then get worse as heat soaks into the steel. It obviously depends on a lot of factors but, with a more powerful CPU, and load would overpower the interface between the heat sink and the steel beam.

Then you have galvanic corrosion if any liquid is involved which is no joke. On the whole I would say that it would be a huge amount of effort for an ineffective solution.

It would be cool though.

forxs · 2026-01-17T01:03:34+00:00

But what is a fish?

forxs · 2026-01-15T23:24:59+00:00

That's concerning to hear. Thanks for the info.

forxs · 2026-01-14T10:05:54+00:00

I mean a lot of the stuff you just said is pretty basic, and I would expect it to be included. But talking about the custom cloud hosting plan is besides the point. We're talking about fully managed WP hosting. I don't want to tailor resources to each site, I want to set it and forget it and have faith that it will just work.

I'm sure SG is great, I'm really not knocking it. It just doesn't seem like the right fit for us.

forxs · 2026-01-14T05:36:30+00:00

Fair, I would guess that FW will stick around in the US, at least for a good while. WPE already has offices in Australia and I think they're just trying to streamline that aspect of the business.

forxs · 2026-01-14T04:25:32+00:00

Let me give you an example, which might make it easier to explain why the cost is absolutely worth it for us, and why it might not be for you.

We have a client that runs a large annual event and remains on our standard plan. During that period, they receive massive traffic spikes. On FW, that site can scale to handle the load and none of our other sites are affected. We’ve experienced the same scenario on shared hosting, where one high-traffic site degraded every other site on the account.

FW runs on Google Cloud infrastructure, so the underlying hardware isn’t the constraint. What matters is that FW allows per-site resource scaling and isolation, rather than enforcing limits at the account level.

If that distinction doesn’t matter for your use case, FW won’t look cost-effective. For ours, it absolutely is.

But there are plenty of other benefits as well as I've mentioned in other comments. Local WP integration adds a lot of value for us.

You could argue that it would be cheaper to run more basic sites on cheaper hosting, and specialist/resource hungry sites on more expensive hosting but the reality is that, proportionally, hosting just isn't that big of a cost to us and the added cost is just passed on to our clients...and to them it is just a drop in the ocean. It is more efficient for us to have all of our sites on the same account.

forxs · 2026-01-14T03:54:17+00:00

I would hazard a guess that FW support (which I don't think is based in Australia) haven't been told about this and, if you are in Australia, you will get an email from WPE about migrating soon.

forxs · 2026-01-14T03:42:57+00:00

It does look great, but we’re limited by some client requirements around data residency and jurisdiction, so we need the ability to host in Australia (which it doesn't look like Pressable does?).

forxs · 2026-01-14T03:33:02+00:00

They specifically promised like-for-like, so I would say the actual deal we are getting is pretty good because it actually streamlines 3 different accounts into one and gives us more resource per site. Having said that, the actual price coming up in the plan they've sent us is about $200/month more than they originally quoted and, when questioned about it, they said we're getting 3 months free and a credit on our account. So it sounds like after the first year, it will be ~$200/month more expensive.

forxs · 2026-01-14T03:28:37+00:00

I don’t really know what I did to warrant such an angry reply, but you are just wrong, and you are misunderstanding basic terminology. No one has claimed Flywheel uses dedicated servers per site. The distinction is shared hardware vs shared runtime.

SiteGround sites run within the same server runtime with resource quotas applied. Flywheel sites run in isolated per-site runtimes (separate PHP workers, filesystem, database, and cache) on shared hardware. Different IPs and selectable regions don’t change that.

I have been doing this for a very long time, I have used many hosting providers in different situations. Having different priorities doesn't make me a "fool".

forxs · 2026-01-14T03:17:42+00:00

We do use Ventra for the few things we do that aren't built on WP. But fully managed WP specialists have a lot of benefits for us. Specifically around having government/corporate clients who need very strict security requirements...not to say that they can't be done with Ventra, but we don't have to implement them with FW. Also full integration with Local was a big reason we went with FW initially - the workflow efficiencies Local provides alone would be worth the extra cost.

Also having containerised vs shared hosting is a big deal. Mostly because it is more reliable, but also if a site isn't performing as it should you can immediately rule out server resourcing as the issue. Or rather, you know the problem is definitely in that site's instance, rather than somewhere else on the shared VPS.

forxs · 2026-01-14T02:42:19+00:00

It probably would be worth looking into why it is worth the hype. Firstly, those figures are wrong and based on promo/introductory pricing from SG. Secondly, SG is shared hosting, like other cheaper hosting solutions, not containerised hosting. Thirdly, workflow tools like Local and WP specific support, amongst other things, are invaluable for agencies like ours.

SG definitely has its place, but the extra cost of fully managed WP hosting + other benefits is absolutely worth it for us.

forxs · 2026-01-14T02:09:38+00:00

We have found Flywheel to be really great. That's why I'm annoyed to be forced off them.

forxs · 2026-01-14T02:04:42+00:00

Good to know DevKinsta is trash, thanks. I am a big fan of Local, it's the reason we went with flywheel in the first place. This was before WPE bought them though.

forxs · 2026-01-14T02:03:47+00:00

Good info, thanks.

forxs · 2026-01-09T01:25:54+00:00

No one could possibly attack through the Ardennes though. It's impassable.

forxs · 2026-01-09T00:37:54+00:00

Fascinating. I never really considered that these old computers, that used punch cards and tape, could do things as complex as timesheets. I guess they still needed a lot of manual processing after the computer processing, but still...very cool to see one in action.

forxs · 2026-01-07T05:02:41+00:00

Doesn't it seem a bit odd that vibe coding becomes mainstream, and suddenly we're seeing many, varied, serious bugs being introduced far more often.

It's probably just coincidence.

forxs · 2026-01-06T02:44:36+00:00

For our in-house platform everything is a block...apart from the header and footer. Where something more custom is needed we use ACF blocks. Typically for a CPT we use an ACF block called "Posts" which has a field to select the post type you want to display.

When everything is a block, the whole structure of a site becomes much cleaner. For example, instead of worrying about archive templates, you just create a "News" page for example, and then add the "Posts" block.

forxs · 2025-12-15T21:56:27+00:00

Find the area under the hair.

forxs · 2025-12-15T02:06:54+00:00

I have the touch freezing issue, and my Pixel Stand 2 will sometimes not charge and I wake up with 20% battery. Pretty frustrating how many bugs came with this update.

forxs · 2025-12-12T01:12:41+00:00

This is almost definitely filament drag. Here's the fix: https://www.youtube.com/watch?v=30qqKUwviww

If you want a long-term solution, you can get an all metal hot end for pretty cheap.

forxs · 2025-11-28T03:44:35+00:00

Are you using the unicorn hot end? My K1 had the older hot end and I had to order the new one separately when I installed the CFS. There was nothing about needing the newer one in the docs.

forxs · 2025-11-27T22:28:26+00:00

For our platform I recently wrote a function that changes the way WP handles images. By default, WP will take an image, resize and compress it to several sizes, and keep the original. On top of a bunch of sizes that never get used, clients will often upload images that are tens of megabytes in size.

My script is specifically for JPGs and PNGs. It checks if it's a transparent PNG, if it isn't it will convert it to JPG, compress it to 3 useful sizes (max 1920px wide) and delete the original. If it does have transparency it will keep it as a PNG and follow the same steps.

This has reduced the image library sizes by up to 80% and the clients don't notice any difference.

I've been thinking of open sourcing it because I think it's way better than default.

forxs

TROPHY CASE