# 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 8
# self = https://watcher.sour.is/conv/apv7rza
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@prologic Funny how we failed to specify this in the metadata extension. As the whole file is encoded as UTF-8, it’s technically legal to use any UTF-8 string for nick, eh? 🥴

Might break stuff in jenny/mutt, but I haven’t tested it.
@movq what would the easiest way be to pass a different configuration file to *jenny*?
While on *jenny*, I got this after trying jenny -e for the first time:


quark@arrakis:~$ jenny -e
Traceback (most recent call last):
  File "/home/quark/.local/bin/jenny", line 710, in <module>
    edit_twt_file(app)
  File "/home/quark/.local/bin/jenny", line 149, in edit_twt_file
    refresh_and_publish(app)
  File "/home/quark/.local/bin/jenny", line 324, in refresh_and_publish
    rotate(app)
  File "/home/quark/.local/bin/jenny", line 545, in rotate
    if len(twt_lines) <= max_num:
TypeError: '<=' not supported between instances of 'int' and 'str'
quark@arrakis:~$
@fastidious Mhh, there’s no easy way. We would have to add a command line option for this. Changing XDG_CONFIG_HOME could work, but that will have lots of side effects.
@fastidious Mhh, there’s no easy way. We would have to add a command line option for this. Changing XDG_CONFIG_HOME could work, but that will have lots of side effects.
@fastidious Mhh, there’s no easy way. We would have to add a command line option for this. Changing XDG_CONFIG_HOME could work, but that will have lots of side effects.