Somewhere like Shanghai, you'll see ~70% of traffic in "bike" lanes are what appear to be electric mopeds.

But if you look closer, all of these mopeds technically have tiny attachment points for pedals. Government regulations allowed e-bikes to be driven unlicensed (but with a special green license plate, unlike the US!) and wherever bicycles are allowed. At the same time, the delivery industry and commuters wanted something stable, capable of carrying cargo/passengers. So the form factor adopted was that of mopeds, while vestigial pedal attachments were provided in order to pass as "e-bikes" under the regulatory criteria. Example. [0]

In practice, using pedals on these made for a clunky experience so they were not usually attached at all. The other main regulatory criterion was that these have to be limited to <= 25 km/h, unlike true mopeds/motorcycles. In practice, these speed limiters were also removed, setting up a cat-and-mouse game between police and riders.

The rule requiring the vestigial pedals was finally removed a few months ago, meaning that the ontology of "e-bikes" is pretty different in China now. [1] (Pedal-assist traditional bike frames also exist, but they share space with the larger mopeds in bike lanes and bike parking. True electric mopeds and motorcycles also exist, but they are effectively regulated out of existence in big cities.)

At the end of the day, top speeds are more determinant of whether different modes of transportation can coexist than pedals or form factor.

[0] https://www.youtube.com/shorts/r4HAUJDQT1w [1] https://chinamotorworld.com/chinese-e-bike-new-standard/

"in Cowork we’ve added an initial set of skills that improve Claude’s ability to create documents, presentations, and other files" https://claude.com/blog/cowork-research-preview

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.

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.

From the README:

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

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.

While the 1913 hot spell was certainly significant, all recorded weather information at the time from surrounding locations, in combination with the dynamics of local microclimates, imply that the 134 degree reading was "essentially not possible from a meteorological perspective." [1]

Observer error stands to be the most plausible explanation, implying that the the recent 130 degree reading in Death Valley may actually become the location's, and the world's, hottest verified temperature.[2]

[1] https://www.wunderground.com/blog/weatherhistorian/an-invest... [2] https://www.washingtonpost.com/weather/2021/07/09/death-vall...

[1] https://www.michellelim.org/writing/stop-using-frontend-back...

This is all great to experience as web apps increasingly take over the functions of native apps. It does help them feel more like first-class citizens, rather than plain documents pulled up through a program.

But it easily brings up new potential abuses by phishing sites, spammy notifications, and other bad actors. The new design seems to start breaking down the browser UI's Line of Death [1], at least in perception.

[0] https://www.apple.com/v/macos/monterey-preview/a/images/over... [1] https://textslashplain.com/2017/01/14/the-line-of-death/

Preemptively opening the link as the sender will send a request to TikTok, but they're not really gaining any useful data there since you just watched the video, hit share (this is what they know so far), and now you opened the link that you had generated. So their database only learned that you shared a video with yourself, which you immediately opened.

The more valuable data is when various intended recipients open the link, allowing TikTok to associate you with them to serve more targeted videos based on implicit social graph, etc.

Moreover, opening the link yourself to get the "canonical url" protects yourself if you're sharing the link broadly since others can't obtain your name [and potentially more?] from the shortlink.

Now, if you're the recipient, there's not much you can do to avoid the tracking link, besides opening it up in as much of an anonymous environment as possible. But interestingly enough, I find the privacy threat greater to the sender. The sender has a TikTok account to aggregate data quite straightforwardly, unlike the recipient. The sender is also being associated with a number of recipients, vs. the recipient with only one sender, and again only through cookies, IP, or something of that sort.

If you share a link from the TikTok app, it gives you a vm.tiktok.com/[xyz] link to send/post elsewhere. It gives you no indication that this isn't a generic link to the post, nor does it give you an option to expose the generic link to the post.

Instead, when you share that link and someone clicks on it and does not have the app, it opens with a header saying "[First Last] is on TikTok." On the other hand, once you do click on that link (if and only if you don't have the app installed), you get redirected to the static link to the video and finally obtain it.

This is an anti-pattern that enables further tracking and potentially unknowingly exposes user data when links are shared publicly. And there's no indication to the user that this is happening, since the link is structured as if it does not contain any tracking. Ie a tool like this wouldn't be able to "strip out" the tracking since it isn't tacked on in any way, but embedded as the generated link itself.

See also: Seaport in Boston, Navy Yard in DC, Mission Bay in San Francisco

Comments URL: https://news.ycombinator.com/item?id=26019443

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=26011099

Points: 4

# Comments: 2