# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 7
# self = https://watcher.sour.is/conv/4rx5iyq
@lyse I do agree "the rules of the web", are far too loose - at least the syntax ones. I do think backwards compatibility is necessary.
As for my website, it might be visually very similar, to how it looked since its creation, many years ago, but it is frequently improved. Features that originally used JavaScript, changed to HTML and CSS components, code simplified, optimised to withstand browser updates and new screen resolutions,... Even a good chunk of the errors on your list, were already addressed and I plan to address the rest soon.
Just find it a bit depressing, that my attempt to bring back some of the old Internet spirit, by making a hidden easteregg page page for this years April 1st, was met with people complaining about April fools day jokes and you insinuating my website sucks.
@thecanine for what is worth, I don't think @lyse intention was to insinuate your website sucked (though it may well do, but again, not his intent, I am sure). I see it more like a technical jest, and a good one at it. It was fun! Isn't that the intent of April Fools', after all?
@david oh, what a copout. Now you have to visit it yourself and form an opinion on it. :P
@thecanine I came by to see it. I liked it! I think it all matches quite well the pixel style you are well-known for.
@thecanine My apologies, mate! :-( As @david pointed out, this was definitely not my intent at all.
For the easter egg hunt, I first looked for a hidden image map link on the pixel dog in the right lower corner itself. Maybe one giant pixel just links to somewhere else, I figured. But I couldn't find any and then quickly moved on. Hence, I naturally viewed the HTML source. Because where else would be a good hiding place for easter eggs, right?
Next, I noticed the <font> tags. I thought I had read quite some time ago that they are not an HTML5 thing, but wasn't entirely sure about it. So, I asked the W3C HTML validator. Sure enough. I thought I let you know about the violations. If somebody had found a mistake on my site, I'd love to hear about it, so I could fix it. I'm sorry that my chosen form of report didn't resonate with you all that well. I reckoned you'll also find it a bit funny, but I was clearly very wrong on that.
I actually followed the dog cow link to the video, so I ended up on the easter egg. However, I didn't recognize it as such. ¯\_(ツ)_/¯ Oh well.
Regarding my message about the browser quirks: I read your answer that you were arguing against the HTML validator findings. Of course, everybody can do with their sites whatever they likes._
@lyse to be clear, I do appreciate criticism, of both my art and and my other projects. Since you pointed it out, I have already fixed all the errors (missing semicolons, overused and incorrectly placed "p" tags, bad CSS workarounds) - all that remains, is last five font tags (maybe even less, by the time you are reading this). 🫡
As someone who likes to experiment with slight text color adjustments, I was somewhat of a font tag fan and did not realise, they were actually deprecated - I thought not using them, is still just some suggestion/new best practice.