# 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 20
# self = https://watcher.sour.is/conv/dadrusa
I'm assuming 12~ sec latencies is pretty insane LOL but this is my RPi we're talking about.~
@eldersnake The thing is that tool is designed to hammer and attack a web endpoint 🀣
@eldersnake The thing is that tool is designed to hammer and attack a web endpoint 🀣
Given how underpowered a Raspberry Pi really is; I’m not surprised to see these kinds of numbers under β€œattack” πŸ˜‚
Given how underpowered a Raspberry Pi really is; I’m not surprised to see these kinds of numbers under β€œattack” πŸ˜‚
@prologic Haha I know, but I was curious to see the difference, especially on the different hardware. It didn't crash and burn so that's something 🀣
@eldersnake Try to hit your twtxt.txt URI which is what the rest of the Yarn.social network sees πŸ‘Œ
@eldersnake Try to hit your twtxt.txt URI which is what the rest of the Yarn.social network sees πŸ‘Œ
@eldersnake Yeah nice to see 100% success rate there at least πŸ‘Œ
@eldersnake Yeah nice to see 100% success rate there at least πŸ‘Œ
@prologic \n> Try to hit your twtxt.txt URI which is what the rest of the Yarn.social network sees πŸ‘Œ\n\n\nNot such a 100% result there, however that exact error is one that often comes up in my output log for yarnd for various feeds, for no apparent reason. I blame not the RPi for that, but my internet connection. It is after all a 4G connection in a zone the carrier doesn't even recognise as being fully covered (on a standard device, granted I have Yagis hooked up), occasionally I can forgive flakiness.
@eldersnake Hang on... What was the URI you were hitting with vegeta? πŸ€” What where is vegeta bring run from? πŸ€”
@eldersnake Hang on... What was the URI you were hitting with vegeta? πŸ€” What where is vegeta bring run from? πŸ€”
@prologic http://localhost:8000/user/eldersnake/twtxt.txt , so on the RPi itself. Which is a fair point actually... that error shouldn't happen on a local network connection πŸ€”
@eldersnake No it really shouldn’t hmmm πŸ€”
@eldersnake No it really shouldn’t hmmm πŸ€”
@prologic Pretty sure I'm the only one who gets that error though so I dunno, naturally always thought it was my internet. Can't explain the localhost getting the error though.
@eldersnake Did you notice the hash of this Yarn? 😁
@eldersnake Did you notice the hash of this Yarn? 😁
@prologic haha yes! I live for the day a hash happens to have _fuck_ in it 🀣 (I know, real mature).