Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 1 Post
  • 218 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle
  • dan@upvote.autohomeassistant@lemmy.worldBryant Heat Pump integration
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    10 hours ago

    I’d make sure there’s an officially supported integration, or one that’s 100% local (no cloud needed).

    It’d be frustrating to spend money and get everything set up only for Bryant/Carrier to decide that they don’t like Home Assistant any more and block an unofficial integration.

    Maybe someone else has better advice for your particular setup.

    For my house, it had central heating so I ended up replacing that with a central heat pump HVAC system that uses a regular thermostat (Gree Flexx with an Ecobee). I didn’t want to deal with anything proprietary. The Ecobee supports local control via HomeKit, which Home Assistant supports natively (no Apple device needed).










  • “legitimate interest” is a sketchy, unclear term. It’s not defined by any legislation.

    There’s a type of cookie called “strictly necessary”. These are things that the site needs to work - for example, to keep you logged in, to remember your shopping cart, etc. Sites do NOT need to offer a opt out from these, and if they’re the only cookies the site uses, they don’t have to show a banner or cookie consent notice.

    I think “legitimate interest” is really trying to trick people into thinking the cookies are “strictly necessary”, when in reality there’s some non-necessary tracking cookies lumped into the “legitimate interest” category.


  • Those two links are talking about fingerprinting.

    Cookies can contain fingerprints, but they’re also used for a bunch of other things, like keeping you logged in, remembering your shopping cart rather than clearing it every page load, storing preferences, remembering if your device has a high DPI screen (so a fresh page load knows to serve higher quality images), etc. Anything where small amounts of data have to be persisted and shared across both the client-side and server-side. They’re not always evil.


  • Give a pigeon a button that when pressed gives sometimes nothin or some food and they go haywire and become addicted to pressing the button.

    My dog goes nuts when I’m in one particular part of the kitchen because her treats are in one of the drawers, even though 9/10 times I’m doing something other than getting a treat for her. The payout is often enough that she puts on a show to try and get a treat out of me lol



  • pro consumer policies

    What pro-consumer policies does Steam have? They still have a lot of games with DRM, although I guess that’s the publisher’s choice, not theirs.

    Their refund policies aren’t great. Not being able to get a refund if you encounter a game-breaking bug just because you’ve played the game for more than 2 hours isn’t a good policy. Thankfully it’s been ruled illegal in some countries like Australia - in those regions, you can get a refund for major issues regardless of how much you’ve played or how long you’ve had the game for.

    I agree that they’re better than some of the competition, but at the end of the day they’re still giving you a license that they can revoke at any time. GOG gives you actual ownership.


  • You don’t absolutely need a central repository for Git. It’s decentralized. You can learn the basics (committing, branching, rebasing, amending, merging, resolving merge conflicts) entirely on your computer.

    My advice would be to get familiar with using Git locally first. Simulate things like merge conflicts - have two branches that both change the same line in a text file, then merge them together and resolve the conflict.

    Once you’re more comfortable with using it locally, learn about code forges like Github or Forgejo.