Whatever reason they don’t isn’t a very good one when there’s already excuses being made around AT proto not being scalable beyond a single app.

ActivityPub works today and we are using it right now. There’s basically no incentive to make a new protocol if you aren’t willing to support more than 1 platform that uses it.

I’m not even a bluesky hater, but you have to question why they’re choosing to reinvent the wheel other than disliking the lack of agency that comes with making a (essentially) proprietary protocol. You have to wonder if they ever truly plan to federated at all or if it’s all just lip-service.

Make sure that any exit ventilation isn’t frozen over for the heater. My heater used to do a similar thing and I always thought the heater was broken, but it was actually as simple as the output pipe freezing over due to condensation build up which caused the heater to turn off automatically. Fixing this involves me installing a electrically warmed pipe extender before heavy snow or ice conditions.

Damn, too soon. Let’s at least give it another 2065 years!

It’s very strange that you’ve made a post about bugs but chose not to list any of the bugs.

Like, how can we make a recommendation if we don’t know what types of issues you’re running into? What type of hardware you have? What expectations you have?

It just kind of screams of disgruntled user syndrome. These are community lead projects so, yes, they’ll have bugs. But if people never say what they are or what issues they had with what they used, the best the rest of us can do is just guess!