Christianity does apply to you, even though you don’t want it to.
No wonder a bunch of you lot have trouble understanding consent.
rs5th
joined 2 years ago
I believe there are a few Honeywell models that are Z-Wave, so that'd be fully local. I'm using EcoBee, which does have cloud control, but I've added it to Home Assistant via HomeKit, and that is local control. It's a little annoying because EcoBee doesn't expose it's fan setting via HomeKit, so I can't have HA kick on the fan when the AC isn't running, for example.
It's two-way due to the limited options in the Lemmy software. New content from those two remote instances will no longer sync to Beehaw's instance where you can view it.
On my personal instance, this hasn't been the case. I'm fully federated with communities that show "subscription pending". I get comment updates with sub-minute delays. I think this is sometimes just a cosmetic issue.
I've seen this if you don't have the specific nginx rules set up on the ingress. Check this out and see if it solves your problem: https://lemmy.kutara.io/comment/700
Oh sure, I totally get it. Once I was fully bought in to k8s and GitOps for one environment, it just made sense to have my other ones use the same tooling.
I believe there's a bug where that happens if the username you've selected is already in use.
So just let randos from open instances post pictures of their cocks all over the place? I don’t know that I’d call preventing that a lot of curation.
Community applications would be sweet.
I think the larger issue was users from those external instances interacting with posts / comments in Beehaw’s communities. Since they’re open registration, bad actors could just create new accounts after being banned from Beehaw.
Better tools would give the admin team more options. Like blocking users from lemmy.word from interacting with Beehaw, but Beehaw users still being able to interact with lemmy.world.
What all are you gonna use em for?