# 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 14
# self = https://watcher.sour.is/conv/zrg4luq
@quark So it really was the missing env var, huh. 🤔 That’s still not great, I’ll keep an eye on it.
@quark So it really was the missing env var, huh. 🤔 That’s still not great, I’ll keep an eye on it.
@quark So it really was the missing env var, huh. 🤔 That’s still not great, I’ll keep an eye on it.
@movq Yup. Added all the language ones, and bam, working like a charm!
@quark Gah, I finally understood what’s going on here. The point is that you were using a non-UTF-8 locale (one with latin1, apparently) – I kept trying to reproduce it with LANG unset or LANG=C, which is different. And that made Python decode strings using latin1, which of course results in garbage. This is clearly a bug, jenny shouldn’t break with non-UTF-8 locales.
@quark Gah, I finally understood what’s going on here. The point is that you were using a non-UTF-8 locale (one with latin1, apparently) – I kept trying to reproduce it with LANG unset or LANG=C, which is different. And that made Python decode strings using latin1, which of course results in garbage. This is clearly a bug, jenny shouldn’t break with non-UTF-8 locales.
@quark Gah, I finally understood what’s going on here. The point is that you were using a non-UTF-8 locale (one with latin1, apparently) – I kept trying to reproduce it with LANG unset or LANG=C, which is different. And that made Python decode strings using latin1, which of course results in garbage. This is clearly a bug, jenny shouldn’t break with non-UTF-8 locales.
The test suite breaks horribly with en_US.ISO-8859-1. Not only do the tests fail, but the test framework is broken as well. 🤣
The test suite breaks horribly with en_US.ISO-8859-1. Not only do the tests fail, but the test framework is broken as well. 🤣
The test suite breaks horribly with en_US.ISO-8859-1. Not only do the tests fail, but the test framework is broken as well. 🤣
… is it really a bug? I can force everything to be UTF-8, that’s not a problem. But that means that your entire software stack must be capable of handling UTF-8 (editor, terminal, …). And at that point why not just require the user to use an UTF-8 locale? 🤔
… hmmm. I can force everything to be UTF-8, that’s not a problem. But that means that your entire software stack must be capable of handling UTF-8 (editor, terminal, …). And at that point why not just require the user to use an UTF-8 locale? 🤔
… hmmm. I can force everything to be UTF-8, that’s not a problem. But that means that your entire software stack must be capable of handling UTF-8 (editor, terminal, …). And at that point why not just require the user to use an UTF-8 locale? 🤔
… hmmm. I can force everything to be UTF-8, that’s not a problem. But that means that your entire software stack must be capable of handling UTF-8 (editor, terminal, …). And at that point why not just require the user to use an UTF-8 locale? 🤔