# 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 15
# self = https://watcher.sour.is/conv/weto2nq
Got Yarn (yarnd) built and running on my Raspberry Pi. All goes well I might eventually migrate to my own Pod? :P Depending on how much I have to deal with rate limits via Pagekite, otherwise might have to shift it over to a VPS.
@eldersnake Oh exciting! πŸ₯³ Let me know if you run into any problems or issues I _shoudl_ resolve! πŸ€— In theory depending on the number of unique followers you have you'd only get _that_ many requests Unfortunately pods (_which only count for 1 HEAD per ~5mins + 1 GET if your feed has changed_) _may_ hit your PageKite rate limits? πŸ€” I'm not sure... Maybe... It's sometime to optimize, which I'm hoping to learn from the experience of the Yarns search engine crawler over time and re-integrate the same logic into Yarn pods. 🀞~
@eldersnake Oh exciting! πŸ₯³ Let me know if you run into any problems or issues I _shoudl_ resolve! πŸ€— In theory depending on the number of unique followers you have you'd only get _that_ many requests Unfortunately pods (_which only count for 1 HEAD per ~5mins + 1 GET if your feed has changed_) _may_ hit your PageKite rate limits? πŸ€” I'm not sure... Maybe... It's sometime to optimize, which I'm hoping to learn from the experience of the Yarns search engine crawler over time and re-integrate the same logic into Yarn pods. 🀞~
@prologic Will do! I _should_ probably let you know yarnd was ignoring the '-R' open registration flag, I had to edit the default value in options.go and compile it that way. Probably something to put in a bug report but I also can't yet discount me having done something silly on my end yet...
@prologic The main thing I can't work out for the life of me is where the raw user txtxt.txt file is πŸ€” I did a find everywhere, lol!
@eldersnake Hmmmm that's a little odd:


$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'
time="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"


Are you positive it was ignoring the flag? πŸ€” What was the symtpoms?
@eldersnake Hmmmm that's a little odd:\n\n
\n$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'\ntime="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"\n
\n\nAre you positive it was ignoring the flag? πŸ€” What was the symtpoms?
@eldersnake Hmmmm that's a little odd:


$ ./yarnd -D -R 2>&1 | grep 'Open Registrations'
time="2021-09-18T14:29:36+10:00" level=info msg="Open Registrations: true"


Are you positive it was ignoring the flag? πŸ€” What was the symtpoms?
@eldersnake

> The main thing I can’t work out for the life of me is where the raw user txtxt.txt file is πŸ€” I did a find everywhere, lol!

In the data directory, which is controlled by the -d/--data flag or DATA env var. πŸ™ƒ
@eldersnake \n\n> The main thing I can’t work out for the life of me is where the raw user txtxt.txt file is πŸ€” I did a find everywhere, lol!\n\nIn the data directory, which is controlled by the -d/--data flag or DATA env var. πŸ™ƒ
@eldersnake

> The main thing I can’t work out for the life of me is where the raw user txtxt.txt file is πŸ€” I did a find everywhere, lol!

In the data directory, which is controlled by the -d/--data flag or DATA env var. πŸ™ƒ
@prologic Yeah, regardless of using the '-R' flag or the long form, every time I would fire up yarnd it would report registrations as being closed and saying neither of the flags were supplied (they were). And sure enough it was showing as closed on the actual webpage. Changing the default in options.go let me register my account, and then turning off Open Registrations in Pod Settings worked to turn if off again.
@prologic Supplying open_registrations: true in settings.yaml also wouldn't work unless the default was compiled to true in options.go first, but it respects it being turned true|false afterwards. Hmm.
@eldersnake That's odd. I'll see if I can repro this.
@eldersnake That's odd. I'll see if I can repro this.