# 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 19
# self = https://watcher.sour.is/conv/nik3c4a
@lyse Just opened the video, skipped to a random position and ended up on 18:30 where he starts talking about Ruby. YES. THIS IS WHY I HATE RUBY. 😂 (And a couple of things more.)
Gotta watch the whole talk, looks like a lot of fun. 😃
@lyse Just opened the video, skipped to a random position and ended up on 18:30 where he starts talking about Ruby. YES. THIS IS WHY I HATE RUBY. 😂 (And a couple of things more.)
Gotta watch the whole talk, looks like a lot of fun. 😃
@lyse Just opened the video, skipped to a random position and ended up on 18:30 where he starts talking about Ruby. YES. THIS IS WHY I HATE RUBY. 😂 (And a couple of things more.)
Gotta watch the whole talk, looks like a lot of fun. 😃
Super fun, @movq, yes! You won't regret it. :-)
@lyse this talk reminded me how much I like Forth/concatenative languages!
@movq it wouldn't be so bad if you could use any date instead of just their magical 2006 date. I loathe the way date formats work--I never remember them and always have to look them up in the docs, like every single time I deal with dates. What I really want is to say "ugh, just make the date look like this: EXAMPLE DATE" and have it just work.
@abucci Yeah, I get your point. 🤔 It *has to be* a magical date, though, to avoid ambiguities. “12:03” could mean “3rd of December” for some weird reason, or “12th of March”.
What I keep confusing is m vs. M, and s vs. S. Like, is that “month” or “minute”, “second” or “timestamp”? If it was YYYY-MM-DD hh:mm:ss and T for a timestamp, it would be easier. But no, it’s Y-m-d H:M:S (according to strftime()), a mixture of upper case and lower case. (The easiest way to remember it is probably: “The time H:M:S is upper case, date y-m-d is lower case – and then they noticed Y2K, so Y got added.”)
@abucci Yeah, I get your point. 🤔 It *has to be* a magical date, though, to avoid ambiguities. “12:03” could mean “3rd of December” for some weird reason, or “12th of March”.
What I keep confusing is m vs. M, and s vs. S. Like, is that “month” or “minute”, “second” or “timestamp”? If it was YYYY-MM-DD hh:mm:ss and T for a timestamp, it would be easier. But no, it’s Y-m-d H:M:S (according to strftime()), a mixture of upper case and lower case. (The easiest way to remember it is probably: “The time H:M:S is upper case, date y-m-d is lower case – and then they noticed Y2K, so Y got added.”)
@abucci Yeah, I get your point. 🤔 It *has to be* a magical date, though, to avoid ambiguities. “12:03” could mean “3rd of December” for some weird reason, or “12th of March”.
What I keep confusing is m vs. M, and s vs. S. Like, is that “month” or “minute”, “second” or “timestamp”? If it was YYYY-MM-DD hh:mm:ss and T for a timestamp, it would be easier. But no, it’s Y-m-d H:M:S (according to strftime()), a mixture of upper case and lower case. (The easiest way to remember it is probably: “The time H:M:S is upper case, date y-m-d is lower case – and then they noticed Y2K, so Y got added.”)
@movq @abucci Yes, formatting with a special date is incredibly silly. I couldn't believe it myself either the first time I ran across it. It still drives me nuts every single fucking time I have to deal with it. Not sure why the Go folks still don't consider it a failed experiment. Luckily, I can often just use the time.RFC3339 or time.RFC3339Nano constants and don't worry about it.
Maybe the positive effect is that you're forced to always go to the docs to look everything up when writing the special time pattern, because there's no chance of remembering anything at all (maybe except the year 2006). With the letter system you might think you know what you do and then skip that check in the docs and finally fail because it was the other way around again. If the Go maintainers wanted to prevent that, then they actually succeeded.
It really depends on the ecosystem you're in. The lower date and upper time rule e.g. doesn't work for Java: yyyy-MM-dd'T'HH:mm:ssSSSXXX (not sure on the exact number of Xs though).
@movq the only way I ever "remember" it is to keep a cheat sheet of the date formats associated with an actual date printed in that format, for all the different formats I commonly use. It's annoying. If I'm building a lookup table like that, the compiler could do it for me. That's what they're for!
@abucci That cheat sheet is in fact a great idea! I should compile one for all my commonly used languages, too.
@lyse I watched this last night, and although I didn't find it too funny, it was quite horrifying 😂 Good watch though! Watched it all the way through, got me hooked 😅
@lyse I watched this last night, and although I didn't find it too funny, it was quite horrifying 😂 Good watch though! Watched it all the way through, got me hooked 😅