In my experience Uber Eats search may as well not exist.
It is so fundamentally broken that it doesn't actually deliver what customers want.
It doesn't matter what you search for, it's going to mostly deliver bad results. Part of that is going to be bad and integration, but a lot of it isn't.
Search for Pizza, will give you stores that don't sell pizzas. And not even after all the pizza stores.
Search for chicken and I get a vegan only store that doesn't even have any meat terms on any menu item, and never did.
It's a complete failure as far as I am concerned.
That it served a billion queries matters not if they are bad results.
All the home inspectors I looked at (Victoria, where this house is, plus Tasmania) were all quite clear that they would only access areas they could find a way in. Closed up areas, wouldn't be inspected by default.
In fact things like attic hatches are supposed to be sealed ane so even though seen the inspector is not allowed in the attic. (Unless there is other evedence of a problem, though they need to repair the seal in that case.
It's that something regional for specific access type? My Victorian houses always had the roof hatch accessible - it's just another storage area and needs to be available if you want to rewire something.
Attic access has to be weatherstripped - cheap ass builders just seal it.
I ain’t buying’ no pig in a poke. If it’s new construction I can inspect before completion (and you should); if it’s used, I am breaking the seal and crossing the streams. Attics got way too much “fun” to discover.
> Attic access has to be weatherstripped - cheap ass builders just seal it.
True.
> If it’s new construction I can inspect before completion (and you should); if it’s used, I am breaking the seal and crossing the streams. Attics got way too much “fun” to discover.
Don't do this! you can't see much anyway. At least not without walking up there and that disturbs your insulation. Everything you care about is about the roof working, so look at the roof from the outside. Keep the roof in good shape and you don't need to go in the attic.
Also until the house is yours you are not allowed to break that seal. Once it is your house you can do whatever you want, but it is too late.
Nonsense. Every house built in Victoria has an accessible hatch to the roof space. The hatches are not sealed either, it's just a lid resting over the opening, which can be pushed upward. Some have hinges, etc.
Incidentally, I'm in Victoria myself. When I bought my house, the inspector did the works. Multiple roof spaces, got under the house and had a look, full report with photos, phone call consultation to explain everything he saw to me. He even notified the sellers of an urgent issue and they had it fixed that afternoon.
I guess it depends who you hire (and whether or not you want to know about any issues, which is the most compelling reason I've seen in the replies so far for why this was "missed").
If the idea of inside /obervation bee hives interests you, you might enjoy the Youtube channel run by Frederick Dunn. He has an observation hive built into the wall of his recording studio.
It's becoming more and more common for PV systems with a battery system to be able to work in an islanded mode, and more importantly - they're legal and code compliant to do so.
When the grid goes down/out of spec, they disconnect the home from the grid and continue to power locally.
Examples of this include Tesla and Sigenergy.
Some are able to do this in very short periods and able to operate effectively as a whole-house UPS. Some will have a flickr of the lights and maybe some sensitive devices will restart. Others will take some period of time to disconnect from the grid and run in islanded mode.
For general interest, Western Australia's State Power company has a variety of battery application cases that it assists with; home batteries, community batteries, fully stand alone, microgrids (with batteries).
West and South Australia are a fair way down the integrated renewables pathway with a high percentage of household rooftop solar, mixed rural PV farms, wind power, battery farms, etc.
LinkedIn at one point were continually pressuring people into handing over their email credentials in the name of making it easy to find your contacts.
So yeah, LinkedIn have never been exactly a bastion of IT Security.
No user ever had a real use case for seeing a button that says "invite X" that doesn't send an invite on the platform, but instead sends an email to X who doesn't have a Linkedin account.
And if you decline, it asks you again. Two times using different wording.
You'll be surprised how many features "tech" people think nobody uses (Like a share button on a website), are actually very popular. That's likely the reason that feature still exists as everything is most likely A/B tested to death.
I was not only talking about that though, but also that they can build shadow profiles and recommend people to you that way.
For personal use: To know what services you use have been breached.
You can then follow it up with ensuring you rotate the password on that site/service.
If they have other PII of yours, it's a heads up that scammers might target you and/or your family with that information.
For work use: To monitor which sites/services employees use with work email addresses, and use it as a reminder/re-enforcement that they should rotate credentials used on that service, and if they're reusing them at work - to change there, too.
We can debate semantics but if you describe yourself with a job title attached to a company then I suggest that you have an association which looks rather like ... employment.
It's not a job title, it's some Microsoft program, like their MVP program.
The RD site linked from Troy's site isn't loading for me at the moment, but if you search "what is the microsoft regional director program" you get back information making it clear that it's not for MS Employees.
> The Microsoft Regional Directors program recognizes industry professionals for their cross-platform technical expertise, community leadership, public speaking[...]
You can be sure that the confusion is not accidental.
As I see it, it's a way for MS to profit from free labour for it's support service and a marketing stunt to benefit by association from the good reputation of this researcher and his initiative.
Even if it is not the case, people like the one previously will think: it is Microsoft employees that are managing this website, they know security.
Its not semantics at all, you just are excusing your own misunderstanding. He didn't describe himself with a job title, and he even explicitly states directly after listing those awards, that he is not an employee of Microsoft.
Extending your logic, I have a CCIE, so if I ever state I'm a CCIE, I'm an employee of Cisco? I have a masters degree by coursework from a university, so I I ever state I have an Msc, I'm an employee of the university? I have an electrical licences issued by EnergySafe Victoria, so if I say I'm an A-Grade Electrician, I'm an employee of EnergySafe Victoria?
I don't think many people would be confused into thinking a Microsoft Certified Application Developer or an AWS Certified Cloud Practitioner are actually employees of those particular companies
> I'm saying those are bad attempts to argue that it's not a confusing title.
You might want to reread, nobody was arguing that.
> We can debate semantics but if you describe yourself with a job title attached to a company then I suggest that you have an association which looks rather like ... employment.
"Debating semantics" is arguing about which definition to use. There is no valid definition under which you can say that Troy is a Microsoft employee.
You can't say "I'm not wrong, You're just debating semantics", all you can say is "I was wrong because I was confused by a misleading title I wasn't familiar with."
cupofnotjoe pointed this out and got a bunch of responses from people with poor reading comprehension who entirely missed his point.
Edit: I use 'you' in the general sense here, not specifically the person I'm responding to.
> Its not semantics at all, you just are excusing your own misunderstanding. He didn't describe himself with a job title, and he even explicitly states directly after listing those awards, that he is not an employee of Microsoft.
Yes, I agree. (I believe you think I am arguing against this; for clarity, I am not).
> Extending your logic, I have a CCIE, so if I ever state I'm a CCIE, I'm an employee of Cisco? I have a masters degree by coursework from a university, so I I ever state I have an Msc, I'm an employee of the university? I have an electrical licences issued by EnergySafe Victoria, so if I say I'm an A-Grade Electrician, I'm an employee of EnergySafe Victoria?
I think these are poor examples and reinforce that the confusion was reasonable. That is the only point I've been arguing in this thread.
Nobody is really disputing that Microsoft chose a confusing award name. However that name being confusing doesn't mean he is an employee or anything really like an employee.
Directly adjacent to the post it says "Hi, I'm Troy Hunt, I write this blog, run "Have I Been Pwned" and am a Microsoft Regional Director and MVP who travels the world speaking at events and training technology professionals"
That reads to me like he's a Microsoft Employee. It's obviously important/significant enough to include it prominently on his website.
"Microsoft Regional Director" is not a job title. It is an award that Microsoft gives out only to non-employees.
You might think the award has a confusing name, and you would be correct. What you cannot be correct in asserting is that an award makes someone an employee because that award has a confusing name. That isn't a question of "semantics", if you assert that award makes him an employee, you are simply wrong.
I'll repeat what I said in a related thread: I'm not saying it makes him an employee. I'm saying those are bad attempts to argue the title isn't confusing.
I'm not sure what you're rebutting. This is roughly the thread as I understand it:
1. "Extending your logic, I have a CCIE, so if I ever state I'm a CCIE, I'm an employee of Cisco? [other examples follow]"
2. "All your examples are not things that commonly are job titles, so you are not 'extending logic'."
3. "They are the same class"
4. "No they aren't, those are not job titles, thus they don't imply employment"
...
#. "those weren't attempts to argue the title isnt confusing."
I don't know what you're reading but #1 is doing just that; roughly translated: "Why would 'Microsoft Regional Director' imply he works for Microsoft? If I have a CCIE does that mean I'm an employee of Cisco?"
#3 Being a Microsoft Regional Director makes him an employee and any claims otherwise are based on some arbitrary semantic distiction, not a real difference
#4 No, there is a real difference. That award is like these other awards and none of them take you anywhere near being an employee.
#5 the arguemnt in #3 is flawed because MRD is confusing and the example title others aren't. (Which misses the point, that using non-confusing examples is much better than using other confusing examples if you want to explain something.)
#6 that doesn't affect the argument being made in #4
#6 repeat ad nauseum
Troy is not a Microsoft employee, no ammount of semantic wiggling will make him a Microsoft employee, no matter how confused people are by the title of the MRD award. That confusion may be justifiable, but doubling down when your error has been explained is not.
"Microsoft Regional Director" is not a job title, it is an award. You thinking it sounds like a job title doesn't make it a job title, it makes you confused. Being given an award does not make you an employee, especially when that award is only given to non-employees.
You ar correct, "Microsoft Region Director" is an award, not a certification like the others mentioned so they aren't quite the same class, but the analogy still holds. Neither being given an award nor a certification makes you an employee.
I can access any other publicly shared Ecowitt station's data.