I did something with my Bosch washing machine (not like the OP). My washing machine is at the other end of the house from my home office. Sometimes I would put a load of washing on, and despite setting an alarm, might forget (perhaps I am in an important meeting etc).
So I decided to solve it.
Using the Bosch API - I can tell both when a cycle is complete, and if the door is open. Currently I use their default version, but there is a local hosted option I'll be switching too now the proof of concept works.
So using Home Assistant I have a simple script that detects when a washing machine cycle is complete AND the door has NOT been opened. This implies my washing machine has wet clothes still in it.
So Home Assistant will alert my phone (and my wife only if she is home based upon presence detection) once every 15mins that there are wet clothes waiting in the washing machine.
Excluding the part of how the access was gained (i.e. fault of end user etc) - I would have thought Stripe would have far better security measures in place for obvious signs of fraud?
If someone changes the bank account of a business for funds to be sent to - why not have a short (?48 hours) delay in allowing funds to be sent there. Especially if the business has been running a while (not sure in this specific case) with no bank account changes - then its not unreasonable for a built in delay for new accounts to be used.
Coupled with some basic stuff of "new bank account, new express accounts, spike in charges, sudden request(s) for withdraws" seems like something that a smart team in Stripe with their development experience could easily implement as an automated security trigger, and hold the funds pending additional security checks?
"They might not have "known", but come on, you're selling radiation-hardened chips to NASA. "
But do people ever actually "invoice NASA" for components. It was probably one of 100 different sub contractors building the actual circuits to NASA specifications, i.e. it was lower in the chain rather than NASA itself.
(Doesnt excuse the non-disclosure to those subcontractors)
So does this mean if they allowed the game to run on "full moon days", it would be expected to eventually get a higher score (if the full moon day allowed that through the actual game mechanism)?
So for ML to work, it has to know all permutations of a game? Does that mean ML is useless for non-deterministic games with random outcomes or procedural generation?
I'm not a machine learning person - so I'm confused about this.
As someone who doesnt understand ML - I have always assumed the whole point of ML is to try different things in the game, almost randomly, and over (long) periods of time the AI gets better and better at the game.
If having a single unexpected event causes such a large swing in outcome, and the AI cant "explain" what is different to cause the swing, then what exactly is the ML doing for it to fail on such a seemingly simple change? Doesnt that defeat the whole purpose of this?
I'm obviously missing something obvious - because I would assume the real goal of ML is that it can teach itself the game, even if that involves unexpected situations, as a human does?
I'm trying to find games for my kids that would have the same influence. Fortnite etc is all so popular - but I feel that Police Quest, Hero Quest etc are a big part of my logical reasoning skills I have today...
What I find strange about this is you dont need it to be "deepfake".
Just an inside job.
If a large company allows a single employee to transfer millions to a new bank account/vendor that has no history, on "their belief" the instruction came from an approved person (i.e. their boss, CFO etc) - that company has major governance issues that are not related to deepfake.
Imagine the more simple scenario - an employee transfers millions, knowingly fraudulantly, to some people they are working with. They then simply supply some "deep fake" pictures and a story how it was an accident - and boom; you walk away with millions.
Checks and balances exist for many reasons - deepfake doesnt overcome those by itself. This company is just missing basic steps that would have protected itself here.
edit: in fact- its even more obviously some inside job; put the deepfake aside for a moment. How was the meeting even booked? Their PR person said "none of our internal systems were compromised". So this meeting magically appeared in someone's calendar? Using their internal video system (Skype or Teams or whatever). And the criminals knew to target this person, with enough knowledge of random office people to deep fake them? Come on...
> I don't want music recommendations from something that can't appreciate or understand music. Human recommendations will always be better.
I find Spotify's "discover weekly" list to be generally pretty good. Sure, there are some songs I dont like, but there are often 3-4 great songs each week that get added to my regularly playlist.
Its all good an well to say that human recommendations are better, but I'm not paying someone $50 per week to spend 3-4 hours finding me new and good songs. I get something that is maybe 80% as good included, and the reality is that is good enough.
I feel like one of the reason AI is doing well is it doesnt need to be better, it just needs to be "good enough" at a fraction of the price..
But think about it from the end user perspective. Literally the most simple instruction; near fault proof. On an airplane that is thousands of feet from remote IT support (plus "costs").
The instruction to staff; problem with "the Internet"? - press the "Interest Reset" button.
Far better than "router restart", "renew DHCP leases" or "reboot IT"
When attempting to login to your Microsoft account, instead of typing your password you can do an optional "one time password" generation thing from Microsoft. So instead of typing your password +2FA - they email you a 6 digit "one time password" that you can use instead.
You cant disable this.
So all Microsoft accounts could have a daily 1 in 1 million chance of been overtaken.
Odds are low - but if you then spam this across thousands of attempts per day - they would statisically "get lucky" from time to time...
Yeah - and what is crazy is when you think about it - Microsoft generates a 6 digit code.
So it is a "one in a million" to randomly guess what the code is on any given login.
But it is "one in a million" for each Microsoft account you know about - and if they have millions of email addresses, and automate it each day (I also get attempts 1-2 times per day).
Yes - the odds are small - but there is a greater than 0% chance someone can randomly get into your Microsoft account - and there is no way to stop it - even with 2FA etc - this bypasses all of that!!!
Doesnt that just mean you need to validate the source of the video? If LTT says to stay way from a product on the LTT main youtube channel - that would seem valid?
If the video was a re-post or hosted elsewhere - then you would start to reconsider it?
I mean - isnt that how all DR is essentially configured? You need it "somehow" connected to Prod depending on the failover, config, system etc. And in many of these complex systems DR can be on a subsystem etc - not an "all or nothing" approach?
I've been using the old v4 "standalone" edition for a long time. About a month ago I finally allowed myself to switch to the SaaS model on a 'family' plan. Its amazing, and more importantly I can now help manage my kids security etc. Loving it.
So I decided to solve it.
Using the Bosch API - I can tell both when a cycle is complete, and if the door is open. Currently I use their default version, but there is a local hosted option I'll be switching too now the proof of concept works.
So using Home Assistant I have a simple script that detects when a washing machine cycle is complete AND the door has NOT been opened. This implies my washing machine has wet clothes still in it.
So Home Assistant will alert my phone (and my wife only if she is home based upon presence detection) once every 15mins that there are wet clothes waiting in the washing machine.
Very simple - works perfectly.