# 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 22
# self = https://watcher.sour.is/conv/hz6o34q
The fact that the official Python docs don’t *clearly* state what a function returns, grinds my gears. This has cost me so much time over the years. You always have to read through a huge block of text.



You could *at least* put a list of possible return values in there (always at the same location, please!), here’s a mockup:

The fact that the official Python docs don’t *clearly* state what a function returns, grinds my gears. This has cost me so much time over the years. You always have to read through a huge block of text.



You could *at least* put a list of possible return values in there (always at the same location, please!), here’s a mockup:

The fact that the official Python docs don’t *clearly* state what a function returns, grinds my gears. This has cost me so much time over the years. You always have to read through a huge block of text.



You could *at least* put a list of possible return values in there (always at the same location, please!), here’s a mockup:

The fact that the official Python docs don’t *clearly* state what a function returns, grinds my gears. This has cost me so much time over the years. You always have to read through a huge block of text.



You could *at least* put a list of possible return values in there (always at the same location, please!), here’s a mockup:

@movq this is why people like me can't code this is boring eyes glazing over kinda stuff lol
@movq this is why people like me can't code this is boring eyes glazing over kinda stuff lol
@kat Okay, horrible cookie popup aside, would you say this is easier to read? https://docs.oracle.com/javase/8/docs/api/java/util/List.html#method.summary 🤔
@kat Okay, horrible cookie popup aside, would you say this is easier to read? https://docs.oracle.com/javase/8/docs/api/java/util/List.html#method.summary 🤔
@kat Okay, horrible cookie popup aside, would you say this is easier to read? https://docs.oracle.com/javase/8/docs/api/java/util/List.html#method.summary 🤔
@kat Okay, horrible cookie popup aside, would you say this is easier to read? https://docs.oracle.com/javase/8/docs/api/java/util/List.html#method.summary 🤔
@movq woah it's like a cheatsheet with explanations! java is kind of arcane magic sorcery to me so i'm having trouble understanding it but i have that with most programming languages. this is like so much easier to actually look at and read instead of my eyes glazing over lol
@movq woah it's like a cheatsheet with explanations! java is kind of arcane magic sorcery to me so i'm having trouble understanding it but i have that with most programming languages. this is like so much easier to actually look at and read instead of my eyes glazing over lol
@kat Yeah, Java itself is somewhat “controversial”, I guess. 😅 But I’ve always found their documentation to be very pleasent to work with, at least that of the standard library.
@kat Yeah, Java itself is somewhat “controversial”, I guess. 😅 But I’ve always found their documentation to be very pleasent to work with, at least that of the standard library.
@kat Yeah, Java itself is somewhat “controversial”, I guess. 😅 But I’ve always found their documentation to be very pleasent to work with, at least that of the standard library.
@kat Yeah, Java itself is somewhat “controversial”, I guess. 😅 But I’ve always found their documentation to be very pleasent to work with, at least that of the standard library.
@movq Yeah, the Python docs are more like a book. They absolutely shine if you have no idea and read them from top to bottom. The tutorial is baked right in. But they don't work all that perfect as cheat sheets. I also remember looking for the return types way too long in the past.

I would have thought that this could be easily improved when type hints are in place. And it sure does: https://www.tornadoweb.org/en/stable/httpclient.html#tornado.httpclient.HTTPClient.fetch
@lyse Right, there is some hope left for Python docs because of the type hints. 😃 (I still don’t use them, because, ugh. 🤦)
@lyse Right, there is some hope left for Python docs because of the type hints. 😃 (I still don’t use them, because, ugh. 🤦)
@lyse Right, there is some hope left for Python docs because of the type hints. 😃 (I still don’t use them, because, ugh. 🤦)
@lyse Right, there is some hope left for Python docs because of the type hints. 😃 (I still don’t use them, because, ugh. 🤦)
@movq I don't use them either.