Testing encrypted images
bie1:QklFMQL2+oo80GaWVEc6HC9i7qIsRWra3xkzpMemx8yRXIVlyeNmKeQgULV25SxeLDsdCASKpQL7dbx/uqxxFNEaa6/UbDMJNr6DSFnN9fYYTxQMjS76ih8pNqk/nxkbusvq91LHqaHb9J2cOXbi0PD6uHX4J9MKCZN7+wdF7maUceFKxZghCptB8cViplhoibWGydJeuWp7hDC31bm3s8atrXdoNCLPxEXxSWD8VYJowY0wuHx28BRezPgFTDb0MXkhzvpuWTCSCxDZ0GC677pFvFp0XmZdWZ3+k4a4EPnR8MaKglWbnZsWewcMuloGWSJgX7SJdl/1CktA0P7Z6Jyoitr9kUzL5DjvLaJirORxPF8bbzonJtOGGBJ1RzASpygyqGtpS9hlDNfONOwzdgtHvuyKJsfgB2Zb2GguXuQYSNPqOg==
It works, but there is something weird that happens when it loads and it may refresh and lose its place on the timeline.
That’s one major thing you guys should look further into is callbacks and fluid anchored positioning for the user’s experience during scroll.
It can be discombobulating to have the entire screen dislodge from the instance where I was interacting.
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
18JwoWxk5fqKXjKdmjusJ27ggh3PXgof4w UnverifiedI think thats related to pushing updates but will look into it
Ok thanks