New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | GPS Track Server for TrackMe, OruxMaps and others | You have to log in to add a translation. | Details |
Original untranslated |
|||
| ↑ | Trackserver | Trackserver | Details |
Original current |
|||
| NOTE: Trackserver v5.0 contains backwards-incompatible changes and changes to client configurations are needed. Please read the <a href="https://www.grendelman.net/wp/trackserver-v5-0-released/">release notes</a> for more information. | You have to log in to add a translation. | Details | |
Original untranslated
NOTE: Trackserver v5.0 contains backwards-incompatible changes and changes to client configurations are needed. Please read the <a href="https://www.grendelman.net/wp/trackserver-v5-0-released/">release notes</a> for more information.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| <a href="https://www.traccar.org/client/">Traccar client</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://www.traccar.org/client/">Traccar client</a>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| <a href="https://gpslogger.app/">GPSLogger</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://gpslogger.app/">GPSLogger</a>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| <a href="https://f-droid.org/en/packages/net.fabiszewski.ulogger/">µLogger</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://f-droid.org/en/packages/net.fabiszewski.ulogger/">µLogger</a>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| <strong>External tracks proxy</strong> | You have to log in to add a translation. | Details | |
Original untranslated
<strong>External tracks proxy</strong>
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <strong>Using Trackserver</strong> | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Using Trackserver</strong>
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| In Trackserver, Cloud Sharing behaves a little differently than in the official TrackMe server. The official server only remembers the latest location update for your device ID. It also has a notion of 'public' vs 'non-public' location sharing, where 'non-public' requires some permissions exchange over mobile text message. Trackserver does not do 'public' sharing. Also, location updates that arrive via the cloud sharing feature are treated the same as any other update: they are stored as a track. The only difference with normal tracking is, that the track name is generated by Trackserver. A new track is created when the date changes. The track name format is 'TrackMe Cloud yyyy-mm-dd'. This is not configurable at this time, but that may change in the furture. | You have to log in to add a translation. | Details | |
Original untranslated
In Trackserver, Cloud Sharing behaves a little differently than in the official TrackMe server. The official server only remembers the latest location update for your device ID. It also has a notion of 'public' vs 'non-public' location sharing, where 'non-public' requires some permissions exchange over mobile text message. Trackserver does not do 'public' sharing. Also, location updates that arrive via the cloud sharing feature are treated the same as any other update: they are stored as a track. The only difference with normal tracking is, that the track name is generated by Trackserver. A new track is created when the date changes. The track name format is 'TrackMe Cloud yyyy-mm-dd'. This is not configurable at this time, but that may change in the furture.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Please also read the FAQ above: 'What changed for TrackMe authentication 1.9'. The new URL scheme is slightly more insecure in some cases, since with the new scheme it is even more certain that your TrackMe password will end up in the server's access logs. Other than that, there is no difference. Remember to always use HTTPS, and change your TrackMe password often, since it will give full read/write access to your Trackserver tracks. | You have to log in to add a translation. | Details | |
Original untranslated
Please also read the FAQ above: 'What changed for TrackMe authentication 1.9'. The new URL scheme is slightly more insecure in some cases, since with the new scheme it is even more certain that your TrackMe password will end up in the server's access logs. Other than that, there is no difference. Remember to always use HTTPS, and change your TrackMe password often, since it will give full read/write access to your Trackserver tracks.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you have been using TrackMe with the old style Server URL, and you try to use the cloud sharing feature, you will see a message along the lines of 'For cloud sharing you need to update your server URL, see Trackserver FAQ.'. This means you have to update the settings in the TrackMe app to contain your username and TrackMe password in the server URL. The complete server URL can be found in your Trackserver profile as always, and the old style URL is now deprecated. Switching to the new style URL also means, that the username and password that you set in the app will no longer be used, and you can leave those settings empty. | You have to log in to add a translation. | Details | |
Original untranslated
If you have been using TrackMe with the old style Server URL, and you try to use the cloud sharing feature, you will see a message along the lines of 'For cloud sharing you need to update your server URL, see Trackserver FAQ.'. This means you have to update the settings in the TrackMe app to contain your username and TrackMe password in the server URL. The complete server URL can be found in your Trackserver profile as always, and the old style URL is now deprecated. Switching to the new style URL also means, that the username and password that you set in the app will no longer be used, and you can leave those settings empty.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| This way, it also works for cloud sharing requests, and we can get the username and password from the URL. | You have to log in to add a translation. | Details | |
Original untranslated
This way, it also works for cloud sharing requests, and we can get the username and password from the URL.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| https://example.com/trackme/myuser/mypass/requests.z?username=&password= | You have to log in to add a translation. | Details | |
Original untranslated
https://example.com/trackme/myuser/mypass/requests.z?username=&password=
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| we configure TrackMe to send requests like this: | You have to log in to add a translation. | Details | |
Original untranslated
we configure TrackMe to send requests like this:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| https://example.com/trackme/requests.z?username=myuser&password=mypass | You have to log in to add a translation. | Details | |
Original untranslated
https://example.com/trackme/requests.z?username=myuser&password=mypass
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.