I imagine it honors the "expires" property of cookies, it just probably wasn't set. Also there's an "ephemeralSessionConfiguration" you can use if you don't want to store the cookies. I enjoyed the article, up until the author blamed the framework for their own ignorance.

SDKSender: switch to ephemeral NSURLSession and disable cookie storage

Switch to a private (ephemeral) session independent of the app and disables cookies. The SDK otherwise shares the cookie storage with the app, which is not desired. This was causing the SDK to send the $dayjob tracking cookie (and others) to $dayjob API endpoint.

But it gave me a really interesting idea: a service/network/community/forum/etc for people to gather and discuss Really Confusing Bugs™ that they're trying to figure out. Not necessarily (?) for contemporary end users (maybe highly technical end users).

This could actually be a really cool concept. Somewhere squarely between HackerOne and StackOverflow - not for exploits, and not for simple(r) stuff, but specifically for complicated and confusing bugs you've been staring at for days/weeks and nothing's making any sense.

I can see a subscription model working for this, even - subscriptions would work both to allow people to provide extended assistance, and also because a contract makes NDAs easier.

Hmm. Thinking about how the subscription model would work... you sign up, configure billing, that then allows you to request extended assistance.

- One way that could work is that people offer you help in return for thanks, which would work like a configurable upvote; higher quality answers attract more rewards. Maybe anyone can reward answers (via the credit in their account) after the fact?

- Another way would be setting a minimum or exact reward amount up front to attract more help.

Regardless of how it worked, the site would have all discussion be public and open by default; you'd have to check a box to make the discussion private, and even after that you'd have the ability to go through and selectively un-redact parts of the conversations so everyone could be helped.

And anyone could sign up and offer answers instantly, and the rewards credited to their account could be cashed out at any time. That would attract new users.

I realize I've just described a weird kind of paid StackOverflow. I am very curious why SE hasn't pursued such an idea. As in, I am 1000% confident they've had this conversation at least once, and I'd really love to hear what the opinions were.

If you aren't using cookies for API auth, is there not some way to configure your server framework to just ignore them if received?

[1] They still exist, and it apparently gets traffic/use, but never hear anyone talking about them, and it never comes up when searching to resolve or diagnose a problem.

Should be universally open to all - at least until someone screws up badly enough to get temporarily or permanently barred, needs to be open outside regular work hours, should be free (or super a inexpensive nominal charge) to enter, would need to monetise itself via other means, perhaps selling beverages.

We've just re-invented "the bar"... ;-)