jacobajit

The article points out that land value is intensely concentrated downtown, while outlying single-family areas typically have low land values. While this naturally results from agglomeration effects, isn't it also a partially an artifact of the low-density zoning itself?

Ie. if we implemented an LVT but also loosened zoning restrictions, the net development (and net taxes) on the single-family areas may well see the highest growth. The interaction between these two reforms performed simultaneously seems unclear.

This is a big underutilized dataset for mapping features, eg. parking restrictions on a given street or building entrances. With something like Gemini Flash, it's cheap to systematically extract map features from that imagery. Surprised that even Google doesn't extract much useful street view information into their maps.

You really need both.

Channels are a great first level, and iOS absolutely needs to implement an Android-tier version of this.

But channels continue to be abused, even on Android. When all deterministic controls fail...

Secondly, channels are set by the developer (or platform). In an ideal world, I want to define whatever channels I care about, and turn them on/off at will.

iOS really needs LLM-based notification filtering. This would take care of promotional notification spam overnight. It would even enable fine-grained user filtering like "notify when - someone is messaging me about plans for today."

Not to be confused with Vancouver Island, British Columbia (which does not contain Vancouver, British Columbia).

I wish there were a way to “archive” cards and passes in the Wallet app. I’d be much more likely to pass-ify my life if that were the case.

The Wallet app is just too important and used frequently in time sensitive actions to clutter with cards/passes that I use once every few months. That is, when I’m about to tap to pay, I don’t want to infrequently used cards to clutter my payment experience. Likewise, when I’m about to board a flight, I don’t want random loyalty cards to clutter the interface.

At the same time, I would really like to keep these occasional cards and passes in Wallet, just not on the main screen. It definitely beats hanging onto these physically, especially because they are in fact infrequently used so I would never carry them around.

It should be a similar distinction to Apple’s Home Screen vs App Library for long-term archival.

I feel like street-view data is surprisingly underused for geospatial intelligence.

With current-gen multimodal LLMs, you could very easily query and plot things like "broken windows," "houses with front-yard fences," "double-parked cars," "faded lane markers," etc. that are difficult to generally derive from other sources.

For any reasonably-sized area, I'd guess the largest bottleneck is actually the Maps API cost vs the LLM inference. And ideally we'd have better GIS products for doing this sort of analysis smoothly.

To be clear, wordplay seems to be all the author's doing.

From the README:

> When you simply open thisaidoesnotexist.com, the model names you'll see are hand curated and pre-generated by me.

Moving to a subscription fee model is dangerous for a service that's reached saturation point. They can no longer project infinite growth in value extracted from eyeballs going into the future, and are stuck with whatever they choose to charge (along with some limited increases in fees. Building a better service cannot be fully leveraged into higher fees, since there's only so much YoY increase in costs users will stomach.)

On the other hand, subscription models are fine for new entrants, even with VC hyper-growth expectations - there are still billions of users to capture even if per-user revenue is fixed! Then the game becomes delivering as much value to these customers as possible to attract more paying users.

Perhaps this is another malincentive that comes about from monopolies.