300 million AWS api calls costs $1.00. If they lost even 2 sales because people could just use HA instead, they 100% lost more money in subscriptions than the cost of AWS api calls
300 million AWS api calls costs $1.00. If they lost even 2 sales because people could just use HA instead, they 100% lost more money in subscriptions than the cost of AWS api calls
lol, I have no idea why someone down voted you.
But yea, the plural of code in the context of programming scripts is just code, but if you were to talk about codes like a code to get into a door pin-pad, it has an “s” at the end for plural. To be honest, I’m sure there’s plenty of native English speakers not in the tech world that would likely also call it “codes” when talking about programming.
When you said “I highly doubt it” in response to the first comment, what were you doubting? You comment does not seem to make sense in response to the comment. They said that the open source project has likely cost more money in lost subscription fee’s than in AWS API calls, and you said you doubt it?
Then the person replying to you said “The general population is very much influenced by the Home Assistant community” not that everyone knows about it. But your comment talks strictly about how commonly known things in the tech world are not commonly known in the general population (which I think is pretty commonly known in the tech world as well).
This comment chain does not seem to be talking about the same things.
I think it could definitely be possible to do locally, and I wouldn’t want a car where I have to connect to servers to connect to it. But I am also not sure I want a car that can be opened with a command on the car itself. The code to access your CAR being stored locally on the car itself, with no server side validation, does seem kinda scary. It’s one thing for someone to manage to get into your online login where you can change the password, it’s another for someone to literally be able to steal your car because they found a vulnerability. It being stored locally would mean people would reverse engineer it, they could potentially install a virus on your car to be able to gain access. Honestly, as a tech guy, I don’t trust computers enough to have it control my car.
Generally, an engineer wants their product to work well and work efficiently. They put effort into a product, and it feels good to see people benefit from that work. The ones making the decisions have money on their mind. If a FOSS version of their paid platform costs them too much money, they will shut it down. Not because it was the engineers decision, but because the one’s making the decision likely don’t even know what github is and just know it’s taking away that sweet subscription money.
Not all of us are so lucky. I was hospitalized for 3 weeks until I was able to get my PiHole back up. I was nearly a goner.
They’re saying the only way you can get the games legally is by buying them. But since the products aren’t made anymore, if it’s unavailable for purchase, it will be impossible for you to play (legally).
They were essentially trying to preserve vintage games with a library style check-out system of digital copies of the games you can play with an emulator. The ruling concluded that was not legal, since the preserved games were used for recreational use. As it stands, if the last physical copy of a game is lost, the only one that would legally have the game files would hypothetically be the original publisher (assuming they kept the original files) and it would be entirely up to the publisher how they shared it. If they decided to keep it to themselves, it would be lost to the public (by any legal means, at least).
Their argument doesn’t really make sense to me, though. I guess we should also ban any books that are used for recreational purposes. If a book is not a non-fiction textbook, someone might read it for fun, which is unacceptable. I think we should get rid of 1984 from all the libraries, since people might read it for enjoyment.