chaospatterns @ chaospatterns @lemmy.world

Posts

25

Comments

155

Joined

2 yr. ago

On Android, you can specify which applications you want included or excluded. Or you can specify that you only route your home LAN IP ranges through wireguard. Both of those would accomplish your goal.

Kind of but it's not fair to put it all on the manager. Multiple people decided to hire the person. Somebody else approved that code review. People approved the technical design. Why didn't the tech lead raise concerns with the manager about someone's under-performance, etc. it's unfair to just put all blame on the manager.

The idea of extreme ownership is about not saying "not my problem I won't do anything" or blaming your reports. It's about saying I can and should do anything and everything in my ability to fix problems.

This is my biggest challenge with this extension. What's clickbait to one person is not to another. Several times I've come across titles that get mangled when rewritten to lose key points. Or the image gets replaced with a random screen grab. There's a difference between somebody doing the YouTube face and a title with "the craziest stunt you've ever seen" and an artist photo with a title saying the "a crazy stunt jump through a burning hoop". I'm okay with the latter but dearrow will often remove crazy. The is just an contrived example

One person could still say "crazy" makes it clickbait, but having some adjectives are fine

If you are port forwarding. I recommend not exposing it on the default port of 25565 and instead expose it as a random port. Then, assuming you have a domain name, create an SRV record that points to your IP and port. This will cut down on the drive by scanners who scan by ports, but won't totally eliminate it. If you do use the SRV record, your friends won't even notice there's a different port.

The alternative is to let certain countries de facto claim a region because others are too afraid to call them on their BS

Ah yeah. Mono didn't support WPF, but Mono did support running WinForms apps natively on Linux without using Wine.

.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That's pretty much it. Anything new should go straight to .net core.

There's a set of special topics under homeassistant/ that devices also publish to that describe what each topic does and how HA should present it. HA will subscribe to everything under that root topic to discover all your MQTT devices.

Just updated and it looks like this one fixed the log spam:

    
json_loads was called from hacs, this is a deprecated function which will be removed in HA Core 2025.8. 
Use homeassistant.util.json.json_loads instead, please create a bug report at https://github.com/hacs/integration/issues

  

It's a little weird they don't have a download update button on the new HACS dashboard for an individual repository, now you have to go to Settings > Updates. I also wish I could hide new and available repositories and only show the ones I have installed (you can't seem to select Pending Restart, Pending Update, and Downloaded at the same time.)

As a professional software dev, I worked with pretty much every OS daily. My personal computer was a Windows, my work laptop was a Mac, and I ran my code on Linux so I was familiar with the things I liked and disliked about each. I also ran my own set of server with my websites, mail servers, and various research projects to learn and grow.

Then I decided it was time to order a new laptop and I didn't want to go to Windows 11 because I felt Microsoft was going too much into features I didn't want like Ads, more tracking, pushing AI. Don't get me wrong, I like AI, but it was too much about forcing me to use it to justify their stock valuations.

I also was working on reducing my usage of big tech, setting up self hosted services like pi-hole, Home Assistant, starting to work my own Mint alternative. It just felt natural to get a Framework laptop and try running Linux on it.

I still have a Windows desktop for games and other things, I still use Mac at work. I still like the Mac for it's power efficiency and it doesn't get as hot. Linux has some annoyances here and there, like dbus locking up, or weird GNOME issues, or for a while my screen would artifact until set some kernel params, or the fact that my wifi card would crash and I had to replace it with an Intel card, but I'll stick with it.

I actually have a double sided male A cable. I was shocked when I got it but I have this laptop cooler that has two A ports on it, presumably to allow a pass through but I'm always nervous that I'll plug it in and fry something.

There's two main ways of doing geo-based load balancing:

1. IP Any-casting - In this case, an IP address is "homed" in multiple spots and through the magic of IP routing, it arrives at the nearest location. This is exactly how 1.1.1.1 and 8.8.8.8 work. It works fine for stateless packets like DNS, however it has some risks for stateful traffic like HTTP.
2. DNS based load balancing. A server receives a request for "google.com", looks at the IP of the DNS server and/or the EDNS Client IP in the DNS query packet and returns an IP that's near. The problem is that when you're doing Wireguard, it goes phone -> pi-hole (source IP is some internal IP) -> the next hop (e.g. 1.1.1.1 or 8.8.8.8), which sees the packet is coming from your home/pi-hole's public IP. Thus it gets confused and thinks you're in a different location than you really are. Neither of these hops really knows your true location of your phone/mobile device.

Of course, this doesn't matter for companies that only have one data center.

Sorry, what do you mean route it directly? Maybe I didn't clarify well enough.

My DNS is routed over the VPN but Internet traffic is routed directly. The problem is the load balancing is done based on where the DNS server is so say Google even though the traffic egresses directly to the internet bypassing the VPN it still goes to a Google DC near my home. Not all websites do this so its not always an issue.

Yes, but if you hit a company doing DNS based load balancing, DNS is going to return an IP that's near to your DNS server which may not be near your device. That's going to add to the latency.

I have Wireguard and I forward DNS and my internal traffic from my phone over the VPN to my pi-hole at home. All other traffic goes directly over the Internet, not the VPN. So that means only DNS encounters higher latency.

However, because a lot of companies do DNS based geo load balancing that means even if I'm on the east coast all my traffic gets sent to the West Coast because my DNS server is located there. That right there has the biggest impact on latency.

It's tolerable on the same continent, but once I start getting into other continents then it gets a bit slow.

Yes fiduciary duty to the shareholder is sometimes misunderstood but this is in scope.

Everything can be securities fraud:

https://archive.is/p2YHV

Or:

https://www.bloomberg.com/opinion/articles/2019-06-26/everything-everywhere-is-securities-fraud

Or just used wired connections. This is targeting wifi cameras and doorbells.

Right, it's a lot better to give somebody a better alternative first if you want the public on board. Build up public transit, build up regional and high speed rail and leave planes for long distances that are unfortunately suited for trains and cars (e.g. international, cross-continental, etc.)

They could and clearly they should have done that but hindsight is 20/20. Software is complex and there's a lot of places that invalid data could come in.

If you're using it, Home Assistant natively supports Wake On Lan. This would only be able to handle the shutdown/sleep side of things.