1,625 karma · joined September 26, 2019
In both cases, Airbnb would only offer us a refund plus maybe like 10%. They would not make any effort to rebook us at an equivalent property.
My theory is that because Airbnb does not sufficiently penalize hosts for these sort of late cancellations, hosts are incentivized to cancel cheap bookings to get a more expensive booking on another platform if prices meaningfully increase.
Don’t confuse lack of accountability with lack of responsibility.
They got scrutiny over it, sure. But trouble? No, I would say that they did not get into trouble.
Anyone is allowed to sue the lawnmower company. Did they win?
It’s not true. You can go find something worthwhile to do instead.
I’m not usually a conspiracy theorist, but if I was a product engineer looking for a way to make my well-engineered product fail just after the warranty period was up, that trigger failure looked like a pretty good candidate. There was a specific piece of the plastic that looked like it was ostensibly there as a structural reinforcement, but it was clearly too short, and the trigger had cracked just past it.
ifixit guide for the curious: https://www.ifixit.com/Guide/Dyson+V11+Trigger+Replacement/1...
Tomatoes prove your point better, but I still would never eat any of the tomatoes in an NYC supermarket in the winter, as they don't taste much better than soggy cardboard.
Another reason is that credit card companies sell your purchase data to aggregators and advertisers, and cash affords more privacy.
I’ve had a couple times now where Google Maps has taken me into absolutely terrible traffic jams on back roads in areas where there is limited cell service. What seems to be happening is that there is a slowdown on the main road and a blind spot on the back route with no service, so Google assumes there are no cars there and no traffic, so it just funnels everyone that way until the whole route clogs up. Utterly infuriating.
Stacking PRs is useful, but I haven't encountered issues with the ergonomics of just using normal git operations to do it. My stacking workflow is roughly:
- Open the first PR from `branch-1` against `main`
- While waiting for a review on that first PR, if I need to build on subsequent work in `branch-1`, I'll `git checkout -b branch-2`, and open a draft PR against `branch-1`
- If the open review requires me to make changes to make changes to `branch-1`, I'll `git merge branch-1` on `branch-2` to pull them up the stack
- After `branch-1` is merged, my draft PR for `branch-2` will automatically update to being opened against `main`
- Repeat as necessary depending on how much stacking is requires and how far ahead I get against my reviewers
I don't find any of this all that difficult or cumbersome. Is there something that this feature offers, that I'm missing out on?
As far as I'm aware, the YIMBY "movement", or whatever you want to call it, is pretty squarely about housing development. It's not about saying yes to building anything and everything, but saying yes to new housing in particular.
For example, https://newyorkyimby.com/ is pretty much exclusively about housing.
I can maybe understand finding value in a machine-written novel if others also read it and enjoyed it, but having an LLM spit out a novel and reading it in isolation, that would be a complete waste of time to me.