Sam

Results 133 comments of Sam

latest federation testing with a Mastodon (v4.0.2) and another FitTrackee instances: | FitTrackee | Mastodon | |------------|----------| | ![FitTrackee](https://github.com/user-attachments/assets/1a9f8c57-3b88-43f4-8265-453e44d2c8ea) | ![Mastodon](https://github.com/user-attachments/assets/a0d9368c-0c4c-4db7-940f-3db241efe6b6) |

Hi, **FitTrackee** already supports segments (``) in gpx file. For instance, for this workout two segments are present in the gpx file: ![fittrackee_screenshot-02](https://github.com/SamR1/FitTrackee/assets/3525167/55970e03-ed0d-45e8-a518-19dc6404fb9c) Each segment can be displayed: ![fittrackee_screenshot-02_segment](https://github.com/SamR1/FitTrackee/assets/3525167/f71dba07-d03e-4424-a1eb-76fc30294229) Do...

Hi, Thanks for the clarifications. This feature may be of interest to others (like leaderboards on total distance). However, this requires the [first part](https://github.com/SamR1/FitTrackee/issues/16) of the social features to be...

Hi, The issue may be related to system encoding or locale. Is the locale a non-UTF-8 locale?

Hi, Thanks for the detailed answer. For the moment, I have not been able to reproduce the issue. I tried with a fresh install on Docker (without any changes, by...

Hi, Thanks for the feedback. Source and the max and average values for heart rate and cadence are stored in database on file upload. The workout uploaded before v0.10.0 are...

Hi, > Like you have your activity and an application (like mine o:) ) can resend old GPX to reprocess in fittrackee ? The same gpx file? or an updated...

Unfortunately, recalculating all sessions will not be possible via an endpoint due to the potential volume of data. For information, I'm currently working on [storing GPX file data in a...

Hi, > Source and the max and average values for heart rate and cadence are stored in database on file upload. The workout uploaded before v0.10.0 are not updated, so...

Hi, It's an interesting feature, complementing the federation. Technically, it shouldn't be too complex to implement; only the most recent public workouts would be returned, as is already the case...