Competitors use it as their serverless JS runtime, likely as simple as that.

Isn't that underselling the opportunity?

I'm sure they'll have a migration path to the cloudflare platform in 12 month.

> There are many events you can't get into now without a smartphone.

Yeah, it's pretty bad.

At least Apple's Wallet app works offline. There is nothing worse than having to use a dogshit proprietary app, waiting for it to handshake with four thousand data collection services before you can reach your My Tickets page, in a location where cell service is shit because thousands of other people are trying to do the same thing.

At least you can still almost always get a normal old PDF that you can print or open on your phone. Somehow these methods even work without sending gigabytes of data to 300 random services, requiring access to every sensor and going through the most botched workflows and UX choices you can imagine. A technological miracle if you ask me.

I'm enjoying the time before it gets really bad, because so far it's usually just the extremely large and centralized companies who let themselves engage this kind of abuse. Small venues, movie theaters, rewards programs or hotel reservations still find complex digital tickets to be too weird, and let us do things the boring old way.

I don't go to many events, but the last one I went to was a concert, and the tickets required the app and could not be screenshotted or PDFed because there was some motion thing on the QR code to ensure that it wasn't a screenshot. It really pissed me off, but there's not much I can do about it other than boycott the show.

Someday, I'd like to try capturing an animated gif or short MP4 or something of the motion, and see if that works, but the pragmatic part of me overwhelmed the hacker side of me. I would hate to lose my money on the ticket and not be able to see the show because I tried to hack the process

I'm wondering what the motion thing is even meant to address. Either a ticket is valid and used / not used or it's not a valid ticket. What about that requires a real-time motion thing?

The code is rolling so you can't use a screenshot to enter the show. This is to stop ticket transfers outside the system.

The ticket stub is animated so you can't use a simple screenshot to move to a better location once inside the show.

Human beings are checking those tickets, and movement is proof of liveness (and not a screenshot you and 25 friends are sharing). Many ticket checking systems are not connected to the internet and cannot/will not check if it's already been used. Many of the motion enabled codes are also basically working in the same way as 2FA codes: your ticket is given with a public key, usually unique to your device, and rotates every minute. Allows them to ensure that the ticket is up to date, not forged and signed properly.

I wonder if they want to prevent reselling or at least require that it goes through their app? (I think this is a bad thing for them to do, just trying to think of the motivation).

My guess is, you're right, it's to force your use of their app. for data harvesting reasons?

Could be that too.

The ones I've seen pretty clearly had some of the motion/change defined by the time. We're so fucked.

You do understand it there because people have been trying to pass of screenshots as the app right? This happened during Covid as well. The Danish Covid passport initially just had QR code, then people started selling screenshots on Facebook. Same with the drivers license, people tried to pass off screenshots as the actual drivers license app.

It's not hard to imagine that people would sell screenshots of QR code ticket online. So rather than accepting that we've created a system that is fundamentally flawed, companies try to pave over it with more and more features, instead of just providing physical tickets.

> [...] there was some motion thing on the QR code

Yep, same happened to me with some baseball game tickets. So incredibly dumb.

Even worse, we split into two groups and I had to ask the other group to download the app... create an account... and finally be able to "transfer" the tickets to them. It took like ten minutes, and thank god we weren't at the park yet trying to do all that. Ugh.

Haha. I bought tickets to an event at the ticket window. They required sending it to my phone and wouldn’t print me a ticket! (They used ticket master). I have heard if you complain enough, they’ll have a security person escort you, but they will not just print you tickets!

These small operators are increasing their usage of the Technical Abomination Solutions, the simple QR code ticket is on the way out

It’s bad. I used to have a 6s which doesn’t have some nfc thing so most of the ticketmaster readers didn’t work and i had to go lookup how to get a barcode to appear..

On one hand, I am incredibly tired of seeing the absolute train wreck of waste that is suave founders taking millions and blowing it on hundreds of personnel who do practically nothing— especially having seen what a single person can do with these tools.

On the other hand, death of a livelihood in a social structure that doesn’t care about you.

We’ve always had pump-and-dump trash. The terrible stuff loses and the good stuff wins. I don’t see why that would change.

The companies that ditch the management structures of yore and successfully build better software faster with the new tools will come out on top. I don’t think these companies will replace ALL saas subscriptions with in-house solutions, because one huge benefit of paying someone else to hold that bag is liability and regulatory overhead.

look at the accounting firms, you'll just have four or five companies that switch off between who holds the bag

I’m sure it depends on the type of work, but for mine, Codex is much more helpful. Honestly, it mostly comes down to it being significantly faster, probably because as many have said, it seems tuned to not spit out word vomit, both in its chat interactions, and its code (Claude is obsessed with massive comment blocks that are basically guaranteed to become dead context noise if you ever use it to iterate on code).

I mostly do very obsessive, tightly scoped, carefully thought out small changes on a fairly boring stack, one interaction at a time, verifying functionality and code. I know what I am doing, but I also know what I don’t like doing (the same exact set of things I’ve already done a dozen times in my career)

If every commit has full ai conversation baggage, and you feed that history back to an ai… aren’t you wildly inflating context with stuff that may or may not matter? How does this even work with thousands of “commits?”

There is a universe where prompting with large context will be near instantaneous and pretty much free. In that universe, there would be no reason not to have even more robust and verbose logging like this. For thousands of commits, a chunking mechanism and a running summary of the chunks would roughly get you there.

I have always wanted a web browser with tmux/iterm2 style tabs/panes, as well as the ability to save the window configuration and tab contents to a file that can be checked in to projects and loaded.

Load all of your project's documentation links, local development browser tools (database viewers, etc.) into a set of views that can be source controlled with the project. Don't force people to use their daily driver browsers for this, or hack side-by-side views together with their OS window managers. Zen and friends have split panes, but it's not the robust tab/panel system that I wanted.

There is a simple tab widget system, which so far has:

- Viewport manager: basically 1:1 with what is in Chrome devtools

- Session manager: create and manage browser sessions as a first-class entity, and attach/detach tabs to these sessions. Includes a simple "incognito" toggle as well.

- System light/dark override: stop flipping this on/off for your whole OS to test "system" light/dark mode (tedious)

- Reload trigger: pick a target tab. if that tab reloads, so does this one.

- Log file viewer: if the tab source is a local file, change the tab's view to a structured log file parser with search/filter, play/pause, etc.

- Screenshot/Video capture: not built yet. pretty self explanatory.

Great keyboard controls are a hard requirement for me. It's a little tricky since content in web views can capture this too, so I have a global "nav mode toggle" you enter to move around between panes and the tabs within them. Actively figuring out the correct UX, but I am liking what I have so far.

Toying with the idea of a "tab link" which allows you to store a set of "source" tabs in a view, but create "links" in other views, where the navigation is synced across all instances. Useful if you want to have, say, the Tailwind docs open to a specific page, but have that page shared across different views. For example, if you want to have one view specifically for mobile view work and another for desktop view work, and not have to manually navigate to the same Tailwind docs page in both views.

I'm honestly just using it as I work on another real project, and adding features as I think "hey wouldn't this be nice?" Which is a pretty fun and satisfying process. I don't have it published yet, because I'm not entirely sure if it's worth sharing at the moment, but I feel like I'll discover that along the way here and go from there. Maybe someone here will chime in :P