Simple: make friends with someone with high speed internet who’s not very savvy, keep up the charade until they allow you to borrow their computer. Then you install a headless vpn server with logging disabled. Boom, high speed local VPN that doesn’t point to you. Just buy them a $2.50 beer once a month to keep up pretenses in case you need to do maintenance.
It’s in there
You up voted “how did “step” porn become so popular when we did such a good job keeping scat and insest porn out of the mainstream for so long” and “I didn’t forget your birthday either.”
And down voted “seamless seeking”
I can say you’re not subscribed to the like two communities on my instance. Subscription (follows) mostly only go to the instance hosting the community in question. Voting goes everywhere though.
What thrift store isn’t nowadays.
So OP is one of the only 25 people who used it?
deleted by creator
Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.
I primarily use groups by room and floor. Since I only ever use groups for voice, for individual lights I don’t worry about brevity. I usually describe the fixture they’re in or type of light. Like I have “Standing Lamp Top”, “standing lamp side”, “living room candle #”, “kitchen downlight #”. The only semi creative name I have is “Ziggy” for these sorta zigzaggy adjustable lamps.
You can try using openssl s_client -connect domain:443 to help debug what the issue is. Without your domain it’s hard to guess what specifically is causing a TLS issue.
Where did you get your certs? Do they match exactly the domain you’re using? Are they expired or self signed? Are your details in the double curly brackets all correct?
You can try to use ssllabs, check cipher compatibility with browsers and such… though I think that requires things are working to a certain level first.
XMSirius just changed their terms and subscriptions are no longer cancelable or refundable starting 3/15/24, even if you sell your vehicle and have no way to use the account.
That’s absurd and untrue. They’re decreasing when you can get a prorated refund. So (aside from a initial window) when you cancel midterm you don’t get money back. That’s not great but that’s a far cry from removing the ability to cancel a subscription.
They’re already being sued for their cancelation process being an utter pain in the ass, removing the ability to cancel would be tossed out immediately.
That will always happen with something exposed to internet. Attackers scan every IP and domain they can looking for vulnerabilities to exploit. There’s software you can put in place to block requests that look like exploit attempts. Cloudfare WAF is one example. But those are mitigations only and not perfectly effective. Beyond that there’s not much you can do. Always make sure anything you expose to the internet is configured securely and kept up to date. If it makes you uncomfortable, reconsider exposing it like that.
I have oil heat too and I struggle to imagine how you would add a sensor to it. That tank is solid and thick, trying to get anything inside it is a horrible idea and trying to sense through the metal is going to be prone to problems. In the past I’ve just pointed a camera at the main gauge.
There’s 6 of them
Keep at it!
19 has federation bugs. Mainly outgoing but I’ve also seen incoming federation gradually fail. Restart the docker container routinely (cron job) until fixes come out.
Not sure I follow what the issue is, it sounds like permissions are working as expected. If you want your normal user account to have permissions you can create a group with ID of 1000 in the host OS, add your user to that group, and set permission to 770.
Your app and DB should be deployed together in the same datacenter to minimize latency between app and DB. Nothing should be hitting your DB besides your app and any etl tools if applicable. So latency to your DB shouldn’t be an issue.
If you need to add redundancy with a deployment in another region you should consider having separate environments between regions with totally separate data which allows you to better manage data protection/export regulations appropriately.
If that doesn’t work you’ll need a multi region database, a vendor with support for that such as aws rds would be the sanest method but you can always hack it yourself.
There’s other options but those require an architecture designed to be heavily distributed and that depends a lot on the nature of your application and you’d ideally hire an architect experienced in such deployments.
Oh God I hope you’re banned quickly
“cock box” they sound… Reputable.
I wonder if you applied inflation from the time that idiom was first popularized what the modern price would be.