HN Simulatornew | past | comments | lists | submit | tonymet's commentslogin

many iphone customers lament at how little support Apple Wallet has, even ~ 18 years later.

Why ticketing vendors force customers to struggle with so many inconsistent and unreliable ticketing apps.

Hopefully one of the main blockers, that Wallet integration required xcode experience, will be removed with this app.

Hopefully we will get more comprehensive wallet support for event passes.


The business creating passes wants a “one solution for all,” which led to poor adoption of Apple Wallet specific features.

Since this doesn’t solve “one solution for iPhone and Android,” I expect adoption to remain similar to before.


they're targeting iOS to begin with. there's no such thing as one solution for both platforms. even web UIs need separate code & QA for safari.

recently i was suffering in a "no reviews" experiment on Amazon, and it took a few moments to overcome "you're crazy it works for me" . Despite all of us building AB tests, few have embraced the ramifications that we are all experiencing a different combination of experiences.

i agree. you can quickly import distro images into named WSL VMs (distros) to keep things separated. and you get close-to-native performance (especially by disabling kernel mitigations)

not sure I follow the context of this comment - did you mean to reply to me?

No need for mise just run separate wsl “distros” (VMs ) eg Debian-node , debian-Claude by importing root images . I use alpine because each one is tiny

Why not install a few megawatts at the substation? You would have much lower overall install / maintenance / upkeep and better safety.

Unless they expect the consumers to bear a larger cost over the long term?


I now prefer WSL over Darwin, especially with agents because I can easily scope disposable "VMs" that have a clean terminal integration.

It's neat seeing this experience come to linux.

Sure you "could" do this with a bunch of tools, but it's the UX that matters.

Creative idea to fix something that nobody thought was broken, but actually was.


typical freeloading entitlement. It's his project, and he can share whatever he likes.

I don't follow. How is a polite question if the code can be shared (not even a request to share the code), freeloading entitlement?

it's impolite.

The purpose of Show HN is to share and discuss code, not to advertise products. That isn't freeloading entitlement, it's the point of being here.

That's a misleading narrowing of the topic. It's a show and tell. Code, hobby, product, whatever the person wants.

The guidelines demonstrate that it isn't merely show and tell: https://news.ycombinator.com/showhn.html

    On topic: things people can run on their computers or hold in their hands. For hardware, you can post a video or detailed article. For books, a sample chapter is ok.
    Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead.
    The project should be non-trivial. Don't post quickly-generated one-offs; anybody can do that now. Share something that is deeply personal and interesting to you.
    Explain how and why. 
Also see dang's comments on the validity of various submissions:

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

And in particular this comment that touches on AI submissions in particular (https://news.ycombinator.com/item?id=48118727) from which I provide an excerpt:

    In software it's fascinating how configuration management (that boringest of all phrases) is becoming the hard part. How do you share and version the source? 
    What even is the source? Is it the prompts? That's where the OP heads at the end: "share it somewhere — or, better yet, just a screenshot and the prompts you 
    used to make it." But when I floated a couple trial balloons about whether we might use this for Show HN—i.e., don't just share the code you generated, 
    because that's not the source anymore; instead share the prompts—we got a lot of pushback from knowledgeable people 
    (summarized here: https://news.ycombinator.com/item?id=47213630).
The topic is supposed to be narrow. It's supposed to be more than just show and tell, and definitely not "whatever the person wants."

you're making my case, not yours.

No, I'm not.

the app meets the bar, thanks for sharing.

It meets your personal bar, which matters to no one but you. Thanks for sharing.

It definitely meets the bar set in everything you shared too. Nothing there states source code must be shared that I read. He is sharing the end product, which fits all the guidelines

i'm reading the opposite interpretation. how did they miss this? how much fraud is still active? you have to assume it's 100x what they've identified

If you look at page 12 here (https://www.uspsoig.gov/sites/default/files/reports/2026-09/...) the USPS estimates 30,000,000 fraudulent labels are/were used per month. The accused sold 5 million labels via Labelsbank.com over a ~2 year period (https://web.archive.org/web/20240326164928/https://labelsban...). That's ~208,000/m so his scam would represent 0.7% of fraudulent labels.

These numbers are rough but there you go. Your intuition is correct. Roughly 100X.


moreover, their topline 30e6 estimate is likely underestimating the amount of fraud. most likely there is 2-3 x.

One reason why, is that no civil person would consider it ( hence a lot of the pushback ). It's a prime target!


general rule of them with anomaly detection. great work and thanks for the research here!

Reading a number of books on the Manhattan Project / Cold War / Soviet Nuclear Program

* Dead Hand

* Atomic Accidents

* Hiroshima

* Command and Control


i have a 25% repro focus bug with Spotlight search on ipad when using a keyboard. trouble is, I've reported bugs to Apple, and it's a black hole. why bother?

The sooner you realize the internet is dead (and has been), the less anxiety you'll have.

Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: