# 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/kynys6q
RPi seems to be handling it like a champ. Mind you, I suppose it should. It's the connection itself that would be the bottleneck. But I guess everyone only needs to load the static page and two images once.
@eldersnake How many page views? Do you have access.log enabled?
@eldersnake How many page views? Do you have access.log enabled?
@adi About 14,000 🤣 and counting
Total requests a bit over 33,000, I'm assuming that's including the image requests as well as the page load. So I'm just counting the hits attributed to the URL request (I'm using GoAccess).
Interesting thing is Pagekite on the Raspberry Pi is using anywhere from 30-70% CPU on 1 core at the moment, which I've never seen before. Obviously the activity puts a load on the tunnel process. Maybe would have been more efficient if they wrote the pagekite library in C or Go instead of Python lol.
@eldersnake Yeah Python isn’t great for performance 🤣
@eldersnake Yeah Python isn’t great for performance 🤣