1,890 karma · joined May 18, 2012
Turned out the installer had failed to put in the high altitude kit which told it to expect a smaller pressure differential. Mostly it was fine, but on rainy days with low barometric pressure, the difference would drop below threshold. But I had to be home for enough rainy days to figure it out.
At one point we were sending prices to GHS, which I think were all-in. But it was a fraught relationship, which I think ended. Google was trying to take a huge cut of the fees, while offloading the hard work of managing travelers, owners, payments, complaints, etc to us. It didn't make sense to help them eat our lunch.
This is 100% true. Hosts figured this out pretty fast and leaned into it. The biggest reason is that showing a cheap price on the initial search result page was very effective at getting bookings. I suspect this is even more effective in this case vs some others because rentals are not easily comparable. ie, travelers invest non-trivial time into researching a place (looking at pictures, location, description, etc) to decide that it works for them before they notice the higher price - and then don't want to throw away that "sunk cost" of their time.
>I don't understand why Airbnb is still on the side of hosts with this.
Everything I said up there also works at the level of Google search results. If just one vendor (ABnB, Vrbo, etc) switches to up-front pricing, then all their competitors look _much_ cheaper at first glance. And once the traveler is on their site, it's unlikely that they'll back out and go to a different one. The whole industry is basically in a "Mexican standoff" situation. Or maybe Prisoner's Dilemma if you prefer.
Also, the platforms are perfectly capable of doing all-in-one pricing, because they legally have to everywhere other than the US. There's loooots of extra logic to handle doing it two different ways. At some level they'd love to get rid of that complexity, but just can't for reasons mentioned.
source: worked on pricing at Vrbo for eight years.
But for commercial buildings where they're trying to squeeze out every square foot of rentable space, and probably are not allowed to overhang their property lines, it's likely not an option.
I partially alleviated this by requiring myself to summarize the useful bits from any article I read into a note. The point being that if there's not enough value in the article to make that worthwhile, then there's no point even reading it and I'm just wasting time. And if there is value in it, then forcing myself to summarize that is going to make it more likely that I'll remember it.
I'm not 100% consistent on doing this, but it does help break me out of "information grazing".
But fair to ask why everyone on HN (including the two of us...) are reading and talking about it.
Might be used for aircraft, ocean shipping, and other places where batteries don't have the requisite energy density and the refueling infrastructure can be installed in a limited number of places (ie, not for passenger vehicles).
Might be used for seasonal energy storage. Although there are relatively few places (salt caverns) in which to store it. Interestingly the same study concluded that natural gas + carbon capture is the next most economically feasible option. https://environment-review.yale.edu/power-127-hours-economic...
Might be stored in an easier-to-handle form - eg make hydrogen, turn it into ammonia, and store that. Of course that lowers the round-trip efficiency even more.
Some utilities have talked about injecting 5-10% hydrogen into the existing natural gas infrastructure to partially de-carbonize domestic heating.
You may have meant an IFV, and in some cases those work. But that's like saying that a rifle and a machine gun both shoot bullets, so why would you want a machine gun?
Also, doesn't thermal storage have the same problem with long-term storage of energy not producing a lot of revenue? Perhaps the capital investment is lower, but the yearly income would be order-of-magnitude the same.
I was pretty much agreeing with you about thermal being the cheap option, but thanks for the breakout.
Do you know of any examples of 10 GWh thermal storage? Just curious, I haven't really poked into that area too much.
I'm very much pro-renewables and pro-storage, but that doesn't mean that all forms of storage are equal. This one has certain advantages (cheap, simple, tough), but the roundtrip efficiency kinda sucks compared to some other options.
And I'm guessing (without checking) that the 30% is for short-term storage (eg, overnight). In which it will drop over time, as the battery inevitably leaks heat into the environment. I'd guess that after 6 months (summer to winter, as you mentioned) it will lose a non-trivial amount of energy so the efficiency will be even lower.
[1] - Actual rates from deployed systems from the EIA: https://www.eia.gov/todayinenergy/detail.php?id=46756
[2] - https://www.energyvault.com/newsroom/energy-vault-announces-...
Nuclear can be ramped, but typically is not. I haven't dug into why, but I get the impression it's partially economic - the plants are very expensive to build and the marginal cost of a few hours of fuel is so low that they prefer to just run all the damn time. I think there may be some technical reasons as well. In general if you look at how utilities operate, they will ramp down literally everything else before the nuclear plants.
That probably applies less to the Small Modular Reactors people keep talking about, but those are still not really a factor.
>with currently available technology the process of converting heat back into electricity only has an efficiency rate of 30%
Yes they're recovering heat as well, which is great when it works. But in general 30% is not great. This probably only makes sense to use when you have huge amounts of nearly-free power. Like if you massively overbuilt solar/wind (which could be a plausible thing to do!) or nuclear.
Tangentially, thanks for bringing this up. I've personally been vaguely aware of all the "inflation is high!!!!!!" articles and hadn't dug in enough to see the reality prior to this post.
Ironically water prices are largely set by government bodies that created water projects (eg, Bureau of Reclamation which made most of the huge dams in the west, various California water boards). Much of it was knowingly, intentionally priced below the cost to deliver it for various political reasons. If you want to read an in-depth account of that, I suggest "Cadillac Desert".
>"capitalism isn't the issue"
In this case, it's _at most_ part of the problem. Government policies delivered artificially cheap water. Capitalism responded to that incentive. Of course people then fight to maintain those policies, so in that sense one could blame capitalism.
>This analysis is so shallow it's practically Libertarian.
Said the guy who has done no actual analysis, and instead just asked questions. I think we've reached a second peak of HN here.
What the OP describes is basically a version of a "bait and switch" fraud, which is pretty widely illegal and not considered OK by anyone. Although you can find examples where people ride that line pretty closely[1], but even then people think it's bad behavior.
A subtly different thing that's maybe closer to what you're talking about is hiring contractors and then blaming them for problems. A current major example being many of the Amazon-branded delivery trucks that only deliver for Amazon, but when they do something wrong "oh they're a subcontractor, not Amazon's fault!"
So, not sure I agree 100%, but I understand the anger.
[1] For example, this guy that found name-brand USB-C hubs had the same "guts" as cut-rate crap. https://overengineer.dev/blog/2021/04/25/usb-c-hub-madness.h...
Just curious what kind of "example" you'd expect someone to bring? Surely not code samples, since most people will not be legally allowed to show you code from their previous employer.
The way I've done this before is to have them talk you through what they did and why, with some questions probing at an appropriate level of detail. But that's not exactly "bring[ing] an example".
People in your company (including non-engineers) definitely care, because code quality bears on how easy it is to debug problems and how easy it is to implement new features or fixes (or sometimes if a feature is even practicable).
Ex: I was selling an item on Facebook Marketplace. The price of the item is in the item header, and in the item description. Multiple people started a chat with me - opening a chat window that has the price again in the chat header - to ask me what it costs. I don't know what you do about that other than have a bot spoon-feed them that information.
Bots would routinely try to scrape pricing for every combination of {property, arrival_date, departure_date, num_guests} in the next several years. The load to serve this would have been vastly higher than real customers, but our frontend was mostly pretty good at filtering them out.
We also served some legitimate partners that wanted basically the same thing via an API... and the load was in fact enormous. But at least then it was a real partner with some kind of business case that would ultimately benefit us, and we could make some attempt to be smart about what they asked for.
A few comments on your list:
2. People got suuuuuper confused about this. I agree several kB is too long, though I could see a case for allowing a (reasonable length) URL, as that's a natural ID in some environments.
3. Yeah, basically if there's a fast rate of publishing relative to feed length you have issues. Another way to handle this would be to say the feed must have the last X days of content, and interested readers have to check back at least that often. Not a problem for always-on aggregator sites, though it could be an issue for occasionally-connected clients (eg, smartphone standalone app)
4. To be fair that's a feature in a lot of cases. Some sites have to monetize content somehow or other.
5. Or share buttons...
6. IKR?! For all my complaints I still wish RSS was used more!
Newsgator used to handle that by deleting any posts not in your feed at every retrieval. So maybe Feedly would too.
If you think that guessing at the internal implementation of Feedly's code based on what a company that's been dead for years used to do sounds like a long shot, then bravo. But hey, it's worth a try, right?
It's been a minute, but I think the gist of it is adding
xmlns:cf="https://www.microsoft.com/schemas/rss/core/2005"
to your <rss> root element, and <cf:treatAs>list</cf:treatAs>
under the <channel>. But see the link for examples. Good luck!
[1] - https://docs.microsoft.com/en-us/previous-versions/windows/d...Yeah, this is definitely a problem. FWIW, Ars Technica solved that by giving you full-text fees only if you pay for a subscription, which seems like a nice approach that more places could hypothetically use.
1) It's not that inefficient, especially if you recalculate your feed only when it changes and use HTTP statuses (particularly 304 Not Modified) correctly.
2) Most people then and now would go through an aggregator. So they'd really be talking to that instead of the source feed.
3) There were push notification standards out well over a decade ago, including RSSCloud and PubSubHubBub.
Somebody puts an entry on the blockchain that says they own my house. OK so what? Nobody cares. They can't get that enforced. If you want to make the sale "real" to the authorities, you have to enter it into the land registry - but now you have a coordination problem. Do we put it into the blockchain first (and hence you pay first) and then the land registry? Or vice versa? Either one requires trust. Hm, maybe we better involve a trusted third party like an escrow company... oh wait we just reinvented the existing system.
All of this is not dissimilar to people selling NFTs of someone else's art. And you'll see the same problems if/when they try to violate copyright on that basis.
If you could convince the relevant authorities that the blockchain was the system-of-record then you'd have something useful. But with all the problems of losing ownership, hacking, inability to recover defrauded assets, etc, what are the odds of that happening?