encoding formats

Hi, here are some encoding formats you can use with my uploader:
You cannot upload encoded images through the UI, this is for use with ShareX only.
On your ShareX custom uploder's settings, add the following to your headers:
'encodeversion' (no quotes)
and as the value, add one of the following numbers:

Then your uploads will have encoded json!
Finally, to use this encoded JSON you need to change your returned URL!
basically for the img id json you wanna use $json:files[0].encodeString$
You can see all the available JSON by hitting the Test button and pressing "Show last response"

You can also include any prefix/suffix as well as text inside the encoded strings, so long as the encoding format doesn't use those keys to decode.
For example, if you use format 10, which is numbers-only, you could add any characters that aren't numbers to your encoded string!
so you could have your URL be this:
http://i0.tf/owo$json:files[0].encodeString$whats_this
the "owo" and "whats_this" dont interfere with the encoding since they're not numbers, it will still parse the embed correctly.
Remember not to use spaces on the URLs though, since that would break the URL.
You can also add text directly inside the encoded string, just not with ShareX, however.
But if you upload with format 10, with the URL above, you would get something like
http://i0.tf/owo5185295902352580414184014234234whats_this
you could add text in the middle of the numbers, like so:
http://i0.tf/owo5a1b8c5d2e9f5g9h0h2hhhh3robdab52yeet5my80spag41lol41840XDDDD142LOL34234whats_this
And this would embed correctly as long as the numbers are the same, and in the same order.
This applies to all encoding formats, not just format 10.

There is no UI for viewing encoded things anywhere, and an upload can only have a single encoding format.


1 = Bunch of special chars
2 = all commas and dot sepperators
3 = small chars, looks like zalgo
-- Not reliable on discord
4 = small chars but with invis sepperators [Uses Zero-Width]
5 = special chars but sepperator is the word 'gay' [Uses Zero-Width]
6 = all characters are invis but 1 character [Uses Zero-Width]
7 = all characters are zero-width or invisible [Not 100% reliable on Discord] [Uses Zero-Width]
8 = all characters are zero-width, sepperators is word 'gay' [Not 100% reliable on Discord] [Uses Zero-Width]
--
9 = Upgraded e7, all chars are zero-width. [Needs testing] [Uses Zero-Width]
10 = All numbers, Seperator = 0
11 = Entirely emojis [Triggers bot antispam]
12 = arabic big letter [Uses Zero-Width] [Triggers bot antispam]
13 = kanji mixup
14 = Entirely ok_hand [Uses Zero-Width] [Triggers bot antispam]
15 = Entirely :eyes: [Uses Zero-Width] [Triggers bot antispam]
16 = ¯\_(ツ)_/¯‍ [Uses Zero-Width] [Triggers bot antispam]
17 = d1nzy's copypasta ‍[Uses Zero-Width] [Triggers bot antispam]
18 = Entirely red heart emojis [Uses Zero-Width] [Triggers bot antispam]
19 = Random heart emojis [Triggers bot antispam]
20 = "Steam is better" meme [Uses Zero-Width]
21 = "bc it fucking sucks" meme [Uses Zero-Width]
22 = same as v9 but had a prefix of a space-length invis char, which makes links on discord not include some invis chars (so if you use this the clickable part of your URL on discord will actually point to the URL it should) [Uses Zero-Width]
23 = ayaya pasta [Uses Zero-Width]
24 = hiragana A spam [Uses Zero-Width]
25 = fat ayaya meme LOL [Uses Zero-Width]
26 = underage okhand meme [Uses Zero-Width]
27 = d1nzy's oWo meme [Uses Zero-Width]
28 = Spaghet [Uses Zero-Width]
29 = new invis encoding template for discord [Uses Zero-Width]


99 = testing version - will change often (dont use)

Note: Formats that use Zero-Width or invis chars will not work in many places.