Replies: 1 comment 1 reply
-
I suggest making the randomly generated server IDs a different length than the legit ones, to avoid confusion. If that would cause problems, is there a subset of IDs that don't exist at all (and never will)? I feel that'll help a bit with data integrity. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a beta release that includes the possibility to import legacy archives created by browser-only versions of DHT.
When you import a legacy archive, you will see a dialog that asks you to fill in the IDs of servers, groups, and direct messages. Filling in the IDs is optional (and not possible if a server no longer exists). If you don't fill in an ID, the app will generate a random one, but I cannot guarantee that you won't run into issues if you continue tracking servers that you imported with random IDs.
The legacy archives are also missing attachment IDs and sizes, but asking you to fill those in would be ridiculous. This means that for ex. in the new Attachments tab, you will see that the total size says
0 B
. If you download the attachments, the Attachments tab will report the actual size then. You can also re-track imported messages if possible, which will correct their attachment IDs and sizes.Finally, the legacy archives have very little information about embeds. The viewer should correctly display image embeds and a very small portion of rich embeds, but the only way to get the full embed information is by re-tracking imported messages.
You can find the beta releases at https://github.com/chylex/Discord-History-Tracker/releases.
Beta Was this translation helpful? Give feedback.
All reactions