If it’s any consolation, this is the first issue of its kind in the multiple years we’ve been using CS. Still unacceptable, but historically the program has been stable and effective for us. Hopefully this reminds higher ups the importance of proper testing before releases
Adjacently, Nobara is based on Fedora for gaming, uses KDE, and has a lot of packages pre-installed for a nicer end user experience. I used to use Kubuntu as my first foray into Linux desktop but I ran into a few issues. Nobara has been overall more stable and more reliable for my daily use.
Nobara is a very good starting point for Linux. I personally know Linux stuff from an IT perspective, but personal use/driver troubleshooting is not something I care to fiddle with regularly. I started with Kubuntu since it’s familiar, but eventually swapped to Nobara when I had some issues with the few games I play.
Nobara has been seamless and easy. Having all wine and proton dependencies preinstalled is much nicer and a lot of games Just Work ™️ out of the box.
Schlage’s Zwave/Zigbee stuff works really well with Home Assistant. Ours have been hooked up since day 1 and don’t have any issues that I know of
https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/CTRLC.ASM
; The user has returned to us.
So ominous.
; Well... time to abort the user.
Goodbye
Laptops that businesses used are pretty good value for the quality. My SO gets Latitude 5590s from eBay that are in near pristine condition and are workhorses for everything he does. They work great with Linux too.
The order of the comment headers is the other way - above the comment it goes with. If you scroll to the top, you can see it better there. The Microsoft person is Zied Aouina
If there’s an option on the AP to not permit link local routing within a vlan/ssid, that will force all traffic up to the firewall. Then you can block intrazone traffic at the firewall level for that vlan.
I’ve seen this in Meraki hardware where it’s referred to as “client isolation”. Ubiquiti might be able to do this too.
In shorter terms to what the other comment said, your website won’t work in networks that use DNS served by your DC. The website is fine on the Internet, but less so at home or at an office/on a VPN if you’re an enterprise.
“I can’t go to example.com on the VPN!” was a semi common ticket at my last company 🙃
I’ve used HyperX’s Alloy Elite for a few years now and it’s still going strong: https://hyperx.com/collections/keyboards-mice/products/hyperx-alloy-elite-2-mechanical-gaming-keyboard?variant=41031691468957.
Has most of the features you’re looking for. One thing is Linux - I’m not sure if it has “Linux” support like you’re looking for, but it does work like a normal keyboard on Linux. I’ve never used macros or any customizing features for it on Windows, and thus don’t use anything like that on Linux either. Media controls work perfectly fine on Linux.
The other concern is hot swapping switches - I’ve never done that either, I have stuck with my brown switches since I got it. Only real customizing I’ve done is to change the keycaps to pudding style.
Short answer, likely yes. It’s not definitive, you could still slip by after sending enough mail, but you are also very likely to get whacked because that VPS IP doesn’t have an email sending reputation.
Longer answer, email gateways like Google, Microsoft, and Proofpoint don’t really care who owns what IP. Well, they might, but they’re more concerned about the sending habits of an IP. While you might send good mail from that IP, there’s no reputation for it, so you could be whacked for having a neutral reputation (the ol’ credit score dilemma but for email).
In order to have a good reputation, you have to send a large volume of messages very gradually over several weeks to “warm” your IP as a reputable sender. I went over this slightly more in detail in another reply, but this article is pretty concise on how an enterprise accomplishes this with a dedicated IP at a provider like SendGrid: https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address
It’s about sample size. Mail gateways won’t designate an IP as a reputable sending IP until it assesses a large volume of mail sent over a long period of time. You can’t send the quantity it wants all at once or even in a short window because then you’ll be designated as a spammer. So you start small with a few a day and gradually ramp up sending over multiple weeks or months to eventually send several thousands of messages in that period.
Spammers and malicious actors too often spin up new IPs for sending mail, so gateway patterns already implicitly mandate that email should come from IPs it’s already judged reputable.
You as an individual can’t reasonably warm your own IP. This is why services like Amazon SES or Sendgrid exist because they have huge IP pools that are ready to go. Plus, those services are very concerned with reputation and have bounce/complaint metrics defined to warn customers that abuse or poorly configure their sending habits.
This next example is what I’m most familiar with, but I’m sure there are other services like this. If you’re a big enterprise and want your own dedicated sending IP because you’re concerned about using a shared pool, you could use something like Amazon Pinpoint which allocate IPs for your org to use in SES, but they have to be warmed before you switch your production workloads over to it full-time. It automates some of the gradual-ness of warming so you use a mix of SES plus your Pinpoint IPs to keep mail flowing for your product.
It looks like Sendgrid also does dedicated IP warming guard rails too. This article is pretty decent for understanding how it works - https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address The per-day warming limits give you an idea of what scale this kind of process is used for.
Definitely listen to this. IP Warming is a very real problem and you have to send thousands of messages at a very gradual rate for most email gateways to 1) mark you as a proper email sender, and 2) classify you as a reputable one that isn’t sending spam. Using a public/private cloud IP isn’t enough, it should be a service already used for mail sending.
If you self host sending email and ignore using a service for outbound, make sure it isn’t at home. ISPs often block SMTP traffic to keep people from spamming others from their home. A lot of IP blocklists also auto block home IPs so you may not ever get your messages delivered.
Make sure to set up SPF/DKIM/DMARC. At the very least SPF, DKIM if the platform supports it, and ideally all three or SPF+DMARC. It’s not that hard to configure if you do it as you go instead of years down the line after you have a dozen services sending mail as your domain.
Does this mean it’ll work again? Mine have been intermittent for half a year now, no matter if media was just started or has been playing for hours.
We added a tilt sensor to our door that shows the state of the door for the most part. The threshold we have it at doesn’t detect if it’s partly open, but that’s okay for us because we never leave it cracked
Our solution that we set up years ago was to connect a Shelly to circuits on a normal, dumb door opener. The Shelly triggers open/closed itself and since the signal comes from the opener, there’s no crypto nonsense to figure out. It always works, no matter what MyQ/Chamberlain/LiftMaster do. Bonus, it also works if you have a very old opener.
We also supplemented this with a tilt sensor so we know the state of the garage door. The door can still be cracked and not registered as opened, but that’s a compromise we’re okay with since we never leave it intentionally cracked.
Yeah you’d need an L7 application layer filtering firewall to catch DoH since it would detect the SSL packet signature on port 53. Unfortunately that balloons the cost of the device past a reasonable level for a home aficionado.
A workaround for now would be to block known public servers that use DoH like Google DNS, since a lot of devices are adding features to enable DoH by default at the OS level
The good news is, based on the diagram looking like it’s straight from AWS docs, there’s a Cloud formation template for all that.
Bad news, good luck troubleshooting any of it if something breaks
I use a ps5 controller for all my gaming needs and it works great on Linux (Kubuntu/Nobara) and Steam Deck. I use hardwired when playing on my Linux desktop, but when playing on my Steam Deck it’s over Bluetooth while docked. Still works perfectly fine. I even played Crosscode with my controller just fine on both systems.
I primarily use it on my desktop for FFXIV which is why I do hardwired. Bluetooth can be squirrely if the game isn’t launched through Steam