# 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 13
# self = https://watcher.sour.is/conv/fml2g4a
Man, that Port70 feed... š
@prologic this is going on for multiple pages on your pod, viewing in guest/logged out mode, so someone is following that feed I guess. I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? š¤ As in totally duplicate yarns like that one.
@eldersnake Yeah I emailed the "administrator" / "maintainer" and this is the response I got:
š¤·āāļø I _honestly_ don't know how to help if the help is just flat out refused š¢ š
@eldersnake Yeah I emailed the "administrator" / "maintainer" and this is the response I got:
š¤·āāļø I _honestly_ don't know how to help if the help is just flat out refused š¢ š
@eldersnake Yeah I emailed the "administrator" / "maintainer" and this is the response I got:\n\n \n\nš¤·āāļø I _honestly_ don't know how to help if the help is just flat out refused š¢ š
It's at this point that I _believe_ it might be time to implement and add support for pod-level "blacklist"(s). Basically I'm not even sure how this feed hits my pod's cache, like at all. Noone on my pod seems to follow it? š¤
It's at this point that I _believe_ it might be time to implement and add support for pod-level "blacklist"(s). Basically I'm not even sure how this feed hits my pod's cache, like at all. Noone on my pod seems to follow it? š¤
Oh well good news, we're having a dialogue, so we'll see where this goes. The problem as I've stated is I have no idea where or how this is landing n my pod's cache at all š¢ It's a right royal #mystery š¤
Oh well good news, we're having a dialogue, so we'll see where this goes. The problem as I've stated is I have no idea where or how this is landing n my pod's cache at all š¢ It's a right royal #mystery š¤
@eldersnake
> I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? š¤ As in totally duplicate yarns like that one.
Well yes and no, the thing is; The Feed Cachee's MaxCacheTTL and MaxCacheItems already limit this kind of thing to a degree. The so-called "spam" will come and go as quickly as it came just be sheer fact of other activity.
@eldersnake \n\n> I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? š¤ As in totally duplicate yarns like that one.\n\nWell yes and no, the thing is; The Feed Cachee's MaxCacheTTL and MaxCacheItems already limit this kind of thing to a degree. The so-called "spam" will come and go as quickly as it came just be sheer fact of other activity.
@eldersnake
> I guess this leads into the question, do we need a way to automatically limit content that might be considered spam? š¤ As in totally duplicate yarns like that one.
Well yes and no, the thing is; The Feed Cachee's MaxCacheTTL and MaxCacheItems already limit this kind of thing to a degree. The so-called "spam" will come and go as quickly as it came just be sheer fact of other activity.
