# 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 4
# self = https://watcher.sour.is/conv/br5oska
@movq @falsifian @prologic _Maybe_ I don't know what I'm talking about and You've probably already read this: *Everything you need to know about the “Right to be forgotten”* _coming straight out of the EU's GDPR Website itself_. It outlines the specific circumstances under which the right to be forgotten applies as well as reasons that trump the one's right to erasure ...etc.

I'm no lawyer, but my uneducated guess would be that:

A) twts are already publicly available/public knowledge and such... just don't process children's personal data and _MAYBE_ you're good? Since there's this:
> ... an organization’s right to process someone’s data might override their right to be forgotten. Here are the reasons cited in the GDPR that trump the right to erasure:
> - The data is being used to exercise the right of freedom of expression and information.
> - The data is being used to perform a task that is being carried out in the public interest or when exercising an organization’s official authority.
> - The data represents important information that serves the public interest, scientific research, historical research, or statistical purposes and where erasure of the data would likely to impair or halt progress towards the achievement that was the goal of the processing.

B) What I love about the TWTXT sphere is it's Human/Humane element! No deceptive algorithms, no Corpo B.S ...etc. Just Humans. So maybe ... If we thought about it in this way, it wouldn't heart to be even nicer to others/offering strangers an even safer space.
I could already imagine a couple of extreme cases where, somewhere, in this _peaceful world_ one's exercise of freedom of speech could get them in *Real trouble* (if not danger) if found out, it wouldn't necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for... let's just say 'Their well being', would it heart if a pod just purged their content if *it's serving it publicly* (maybe relay the info to other pods) and call it a day? It doesn't have to be about some law/convention somewhere ... 🤷 I know! Too extreme, but I've seen news of people who'd gone to jail or got their lives ruined for as little as a silly joke. And it doesn't even have to be about any of this.

P.S: Maybe make X tool check out robots.txt? Or maybe make long-term archives Opt-in? Opt-out?
P.P.S: Already Way too many MAYBE's in a single twt! So I'll just shut up. 😅
@movq @falsifian @prologic _Maybe_ I don't know what I'm talking about and You've probably already read this: *Everything you need to know about the “Right to be forgotten”* _coming straight out of the EU's GDPR Website itself_. It outlines the specific circumstances under which the right to be forgotten applies as well as reasons that trump the one's right to erasure ...etc.

I'm no lawyer, but my uneducated guess would be that:

A) twts are already publicly available/public knowledge and such... just don't process children's personal data and _MAYBE_ you're good? Since there's this:
> ... an organization’s right to process someone’s data might override their right to be forgotten. Here are the reasons cited in the GDPR that trump the right to erasure:
> - The data is being used to exercise the right of freedom of expression and information.
> - The data is being used to perform a task that is being carried out in the public interest or when exercising an organization’s official authority.
> - The data represents important information that serves the public interest, scientific research, historical research, or statistical purposes and where erasure of the data would likely to impair or halt progress towards the achievement that was the goal of the processing.

B) What I love about the TWTXT sphere is it's Human/Humane element! No deceptive algorithms, no Corpo B.S ...etc. Just Humans. So maybe ... If we thought about it in this way, it wouldn't heart to be even nicer to others/offering strangers an even safer space.
I could already imagine a couple of extreme cases where, somewhere, in this _peaceful world_ one's exercise of freedom of speech could get them in *Real trouble* (if not danger) if found out, it wouldn't necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for... let's just say 'Their well being', would it heart if a pod just purged their content if *it's serving it publicly* (maybe relay the info to other pods) and call it a day? It doesn't have to be about some law/convention somewhere ... 🤷 I know! Too extreme, but I've seen news of people who'd gone to jail or got their lives ruined for as little as a silly joke. And it doesn't even have to be about any of this.

P.S: Maybe make X tool check out robots.txt? Or maybe make long-term archives Opt-in? Opt-out?
P.P.S: Already Way too many MAYBE's in a single twt! So I'll just shut up. 😅
@aelaraji This is one of the reasons why yarnd has a couple of settings with some sensible/sane defaults:

> I could already imagine a couple of extreme cases where, somewhere, in this peaceful world one’s exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldn’t necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for… let’s just say ‘Their well being’, would it heart if a pod just purged their content if it’s serving it publicly (maybe relay the info to other pods) and call it a day? It doesn’t have to be about some law/convention somewhere … 🤷 I know! Too extreme, but I’ve seen news of people who’d gone to jail or got their lives ruined for as little as a silly joke. And it doesn’t even have to be about any of this.

There are two settings:


$ ./yarnd --help 2>&1 | grep max-cache
      --max-cache-fetchers int        set maximum numnber of fetchers to use for feed cache updates (default 10)
  -I, --max-cache-items int           maximum cache items (per feed source) of cached twts in memory (default 150)
  -C, --max-cache-ttl duration        maximum cache ttl (time-to-live) of cached twts in memory (default 336h0m0s)


So yarnd pods by default are designed to only keep Twts around publicly visible on either the anonymous Frontpage or Discover View or your Timeline or the feed's Timeline for up to 2 weeks with a maximum of 150 items, whichever get exceeded first. Any Twts over this are considered "old" and drop off the active cache.

It's a feature that my old man @off_grid_living was very strongly in support of, as was I back in the day of yarnd's design (_nothing particularly to do with Twtxt per se_) that I've to this day stuck by -- Even though there are _some_ 😉 that have different views on this 🤣
@aelaraji This is one of the reasons why yarnd has a couple of settings with some sensible/sane defaults:

> I could already imagine a couple of extreme cases where, somewhere, in this peaceful world one’s exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldn’t necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for… let’s just say ‘Their well being’, would it heart if a pod just purged their content if it’s serving it publicly (maybe relay the info to other pods) and call it a day? It doesn’t have to be about some law/convention somewhere … 🤷 I know! Too extreme, but I’ve seen news of people who’d gone to jail or got their lives ruined for as little as a silly joke. And it doesn’t even have to be about any of this.

There are two settings:


$ ./yarnd --help 2>&1 | grep max-cache
      --max-cache-fetchers int        set maximum numnber of fetchers to use for feed cache updates (default 10)
  -I, --max-cache-items int           maximum cache items (per feed source) of cached twts in memory (default 150)
  -C, --max-cache-ttl duration        maximum cache ttl (time-to-live) of cached twts in memory (default 336h0m0s)


So yarnd pods by default are designed to only keep Twts around publicly visible on either the anonymous Frontpage or Discover View or your Timeline or the feed's Timeline for up to 2 weeks with a maximum of 150 items, whichever get exceeded first. Any Twts over this are considered "old" and drop off the active cache.

It's a feature that my old man @off_grid_living was very strongly in support of, as was I back in the day of yarnd's design (_nothing particularly to do with Twtxt per se_) that I've to this day stuck by -- Even though there are _some_ 😉 that have different views on this 🤣