paranoidrobot

You're being unkind to the parrot. Parrots are known for mimicking others in their environment.

One might reasonably expect it to scream/shout and swear if one mentions PHP.

Long time Kindle user. I have deeply disliked the touch-only interface since it was introduced - the only reason I switched to them was because the old one with page turn buttons toon a swim.

The touch interface is great for typing, but for turning pages I find myself either accidentally pressing on the screen or it not recognising the touch at all. Touching in the wrong spot can also result in it clicking links or similar.

The idea they might be bringing out a case that has the buttond seems great, except it's only for the signature editions.

Not happy about that one.

Define crime though, because one particular action could be both a crime and not, depending on a range of factors that the LLM might not be aware of.

Even having a million legal experts on call weighing in on every prompt/response will not agree on everything.

Even things like "go and break into this system, use whatever means you need to" might not be a crime.

As much as the collective dumping on LastPass for yet another breach, and how they're totally irresponsible for handing customer data to some third party is amusing.

I think if people took a moment to actually look at what happened, they might realise that the story everyone has in their heads is quite different from reality.

Klue is one of those CRM services that so many sales teams are using. Yes, you have to hand them customer records (email of the customer contacts, finance teams, etc). That show Klue delivers it's "market intelligence" thing about that customer.

If you go to your sales teams and see what random stuff they have hooked up to your systems, I bet you will find similar things.

Whether or not this is a good idea (I firmly dislike it), this is how sales teams work these days. If you try to take it away you will be fighting the entire sales organisation.

I am more surprised that these breaches don't happen more often.

It doesn't impact LastPass's actual password databases.

(No affiliation with any of the entities involved in this)

I would counter this by saying we might all be better off if consumer protection laws were stronger and actively enforced against this.

I don't really have a problem with offering discounts to members of X program, or if insurance is pre-selected.

But the advertised price should be inclusive of everything (taxes, fees, charges, etc) and the price available to the general product before membership-exclusive pricing.

So if you advertise a product for $100 then any normal person can pay $100 and get it for that.

Want to sell it from cheaper to members of your reward program? Go ahead. But it can't be the most prominent price advertised for it.

You want to sell insurance pre-selected? No problem but again the default advertised price needs to include it. Even if they can opt out for a cheaper price.

There are sure to be edge cases. But the point being is that the price you advertise most prominently needs to be the all-inclusive price any member of the public can get without having to fight to select the correct option.

We don't accept misleading and deceptive practices in other areas, why do we let airlines, hotels and hire car places do it?

> It’s not like we have a term like “individual contributor” or anything in the industry.

Perhaps I'm missing something here.

To me "individual contributor" means anyone who is NOT: A (technical) "Lead", "Chief", "Architect", or (possibly) "Staff" anything, and has no management or team-leader responsibilities.

I'm in Australia but similar sounding system is in operation at our two major supermarkets.

I scanned a drink, heard the beep, put it in the bag. I scanned a loaf of bread, heard a beep, put it in the bag.

Now, instead of the typical "Unexpected item in the bagging area" it now shows the overhead replay and locks the system out until an employee comes over to review.

Combined with their exit gates that don't open if they think you've not paid for something, and cameras that track you through the store it's feeling very unfriendly.

I don't read HTML all the time, and I don't expect it to be easy to read when outside of a browser.

Markdown though, that's my slightly fancy readme. It has just enough structure that I can easily read and understand it on the command line.

I can easily grep it without need for an advanced parsing engine.

If you need something with font and style weight then go for HTML.

But if I see README.html with a project, it's going to put me off wanting to contribute. I do not want to learn that project's style guide for how to add some new parameters to a table or remember that they want to specify italics in one of a dozen different ways.

> I believe a VPN should stay hidden if it works, no need to have it visible.

Which is fine if you only have one VPN client or one VPN network and you don't need to turn it on/off or change it regularly.

My current day job has one VPN client but five different networks.

At a previous job I had two different clients I would need to switch on and off.

It is very on-brand with Apple though that there is one right way to do things, and everyone else either needs to change the way they do things or go elsewhere.

> It is a shame articles like this imply that all men act this way

It's not implying that at all.

Add-ons (now apps) can't be done without HAOS. It's one of those non-obvious things.

There's other things I forget which are also more difficult/annoying to manage on the container version.

I have a rather large docker compose stack so my first experiments with HA were as running it there.

That lasted maybe a week before I went and ran it as a VM instead.

I haven't done it either. But it should just be a case of passing the device to the container. You might need to disable the host from using it and pass admin rights to the container too.

But it was also quite easy to pass a USB device to the HAOS VM in Proxmox.

I wouldn't put running a weather station in the same class of disk activity as running Home Assistant. It is writing a fairly large amount of logs, plus statistics for every attribute/sensor for every device. The more devices you have, the more you will be writing.

There are regularly threads from people with "I restarted HA and now I get this weird boot error message", and it's because their SD card died.

You do you, but it's common enough of a problem that I think it's worth calling out as a "Don't do this".

I'm using OPNSense for the router, on their dedicated hardware - DEC750 iirc.

The switches are mostly Mikrotik, with some Unifi switches.

The wifi APs are all Unifi - they are all PoE and wired into the same network, no mesh. Even between buildings I ran fibre.

For the switching and routing, were I to do it again now I might go all Unifi. They recently implemented some much needed updates to make doing things like firewall rules and routing based on device much easier. I have a complicated set of rules in OPNsense to route IOT VLAN traffic out via a VPN connection, which require static IP assignments via DHCP, but under the new Unifi network I could do it with a few clicks and being able to use device attributes rather than a static IP.

I am also using an SLZB-MR1 for a ZigBee controller and Matter over Thread border router. I've got a bunch of IKEA and Mercator ZigBee light bulbs/fixtures that act as ZigBee routers. It's a strong enough mesh I rarely have issues with the ~180 devices on the net.