moderation

@eweiss99 This repo is not maintained and wont work at all against the new API endpoints. I suggest you look at the working forks at https://github.com/moderation/garmin-connect-export/ and / or https://github.com/pe-st/garmin-connect-export

@Markleonard1019 This repo is not maintained and wont work at all against the new API endpoints. I suggest you look at the working forks at https://github.com/moderation/garmin-connect-export/ and / or https://github.com/pe-st/garmin-connect-export

@dedwardn this repository is no longer maintained. Could you test with this [fork](https://github.com/moderation/garmin-connect-export) that is more up to date?

@joetimmerman cool to see some of my code in your fork. Considering the last commit to this repo was December 2015 and the code as is doesn't work it is...

I don't believe the endpoint is down. When in a browser and logged into Garmin Connect I can load https://connect.garmin.com/proxy/activity-search-service-1.2/json/activities?start=0&limit=1 successfully. I think they must have changed the required cookie...

@frechina That worked! Amazing. How did you work that out? My _heavily_ modified but working fork is at https://github.com/moderation/garmin-connect-export if anyone is interested.

@TobiasGirschick follow the comments thread on this issue for the fix - https://github.com/kjkjava/garmin-connect-export/issues/18#issuecomment-243811213. My fork which has the necessary GET calls and works is linked to from the comments.

`reqwest` support makes sense. The issue for HTTP/3 support in `hyper` is at https://github.com/hyperium/hyper/issues/1818

The docker images at https://hub.docker.com/r/jarredsumner/bun/tags haven't been updated for quite a while. You are pulling `0.0.82` which is pretty old considering the big changes with each release. I'm sure the...

> Are you planning to support http2? HTTP/3 is on https://github.com/oven-sh/bun/issues/159 so I would say HTTP/2 will likely be added before that