joshsharp

Good luck with your launch :)

What actually is it though? What do you do with it? I can't tell.

Still working on https://exist.io, a platform for quantifying and tracking data about your life. We've been around for about a decade now and seen many competitors come and go — this niche is definitely not at the peak of the hype cycle any more. On the other hand, Apple Watches have normalised tracking body stats like activity (and sleep to a degree), and yet we think there's still so much more that can be done with that data. We're still (always) working on improving our insights and correlations to find better ways to use the data to optimise your health, mood, productivity, and so on. But not with "AI" :)

And you're using https://changemap.co for your public roadmap, another incredible tool in its own right ;)

If you like this, you may enjoy this old blog of Street View images as art: https://9-eyes.com/

If you want to do something similar without hosting it yourself, you can try my thing https://exist.io. It has a full API in addition to a bunch of integrations.

Yep, there's an API and import/export.

It just goes read-only. You can still access and export bookmarks.

Now wouldn't it be great if it was viable to make the same decision about distributing your iOS app.

Gluon is also a language built on Rust: https://github.com/gluon-lang/gluon

Cool to see that this is written in Crystal.

We do not need to honour cookies when making requests to the API as we use token authentication. Even if we wanted to keep users logged in within the web view, which we don't because the web view is just for static help pages, we wouldn't want to send those to the API.

Sure, the cookies expire (in two weeks I think, in this case) but that doesn't invalidate the issue that the wkwebview silently shares cookies with nsurlsession, nor does it negate the confusing journey of tracking down the bug. Sheesh.

They shouldn't be logging in via the webview within the app anyway, so that's moot.

We are using cookies, as the post says, as a fallback authentication so devs can browse the API from a browser if they're logged in to the site.

Using the Authorization header.