on that note: what the fuck is this mess of json-ld that mastodon throws at it

proof-of-concept: works :neobot_thumbsup:​

ooookay the oldest post cannot be 1970-01-01T00:00:00Z (got a err="[POST /api/v1/statuses][406] statusCreateNotAcceptable" in response) but 1970-01-01T00:00:05Z is fine, huh

okay even 1970-01-01T00:00:01Z is fine, good to know :neobot_thumbsup:​

aaaaahhh of course

while backdating is a feature, it can't send posts into the future (say, making a post at 2038-01-19T03:14:07Z) with the same thing

@awoo is 2037 possible?

aaaaahhh of course

while backdating is a feature, it can't send posts into the future (say, making a post at 2038-01-19T03:14:07Z) with the same thing

it is so sorry for that reference

and of course it couldn't stop there, so it tested GoToSocial's sanitiser for a bit :3

and turns out that it does filter out onload tags/events from elements.

it also filters out links (<a> elements) that are going to javascript:, interestingly enough.

it also filters out links (<a> elements) that are going to javascript:, interestingly enough.

@awoo if you do find something dreadful please let us know before posting about it... unless it's dreadful but harmless in which case have fun!

@awoo this is going to result in another Mastodon post from 10000BC breaking everything, isn't it? :3

@that it very much could result in such a post ​

it also filters out links (<a> elements) that are going to javascript:, interestingly enough.

even completely HTML entity-ified strings like <a href="&#106;&#97;&#118;&#97;&#115;&#99;&#114;&#105;&#112;&#116;&#58;&#97;&#108;&#101;&#114;&#116;&#40;&#49;&#41;">hmmmmm :3</a> get thrown out

now it's actually curious how GoToSocial's (or slurp's, if it has one) sanitiser works