• 2 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle
  • First thing you should do is read the bylaws. There should be some that define how the HOA should operate when it was incorporated. You don’t want to break any bylaws. For two units I doubt it’s that big of a document. You also should also get organized about all docs and record keeping especially if you have any sort of finances.

    My understanding thus far is that we should build up our funds and then put some of that money in CDs and brokerage accounts, eventually

    I don’t know how much big of a budget you’re going to have, but with larger HOAs like mine, we have operating costs and reserve expenses both with their own accounts. Reserve is for long term expenses like you need a new roof. Operating for paying things like shared landscaping. Reserve studies can help you identify how much time until you need to replace the roof or the siding or whatever other things are common with your building.

    Don’t invest in the stock market, but at a certain account size CDs for long term investments are a good idea. We use that to help offset dues increases.

    It doesn’t have to be complicated but you are technically running a business.




  • Different Operating Systems call it different things. Windows calls it Alternate. Even if it was only used when the primary was down, DNS doesn’t provide any sort of guidance or standard on when to switch between primary and secondary. Is one query timeout enough to switch? How often do you reattempt to the first DNS server? When do you switch back? With individual queries, you can timeout and hit another NS server, but that’s a lot easier at an individual level than to infer a global system state from one query timing out.





  • There’s no guarantee bugs get fixed in a newer version, but there’s a higher chance of a software feature working if it’s been out for awhile with a few patch releases than it is for a brand new feature to work day one on a YYYY.MM.0 release. Home Assistant generally holds new features for those YYYY.MM.0, but patches get backported.


  • Past vulnerabilities doesn’t mean there is active mpdern vulnerabilities especially ones in widely tested operating systems that’s exploited by as many apps as people claim are listening when security researchers also regularly reverse engineer and analyze the source code of popular apps to figure out what they’re doing. You can decompile Android apps pretty easily to see what they’re doing. Some are obfuscated so it takes some effort.

    Its one thing to claim there’s some a system level bypass for the icon that the NSA uses to spy on its enemies, it’s another thing to claim that it’s being exploited on a wide scale by a tech companies on different apps, iOS and Android, multiple versions/devices.

    The reality is that we leak tons of info through other mediums that are easier and cheaper to collect than through microphones.


  • update 2.1.3 once update 2.1.4 becomes available

    I wouldn’t use that policy because what if 2.1.4 includes a fix for an issue in 2.1.3?

    My update policy is wait until a month comes put, then update to the newest previous month’s version. Patches for bugs go into mainline and are backported so this minimizes bugs in the new features.