# 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 8
# self = https://watcher.sour.is/conv/omqipwa
eaplmx
twtxt.net
View Thread
@david I don't want to discourage any idea, indeed I think it's a good one. I've read the whole RFC 770, so I think I understand the result, but not the why. My concern comes from the overhead of having to:
- Manage a lot of keys (with the problems it creates of string private keys)
- Decrypt every message once it arrives
- Not having a way for the non-compatible browsers to hide this content.
prologic
twtxt.net
View Thread
@eaplmx

> I’ve read the whole RFC 770, so I think I understand the result, but not the why.

So basically the "Why" is quite simple; As a User of Yarn.social I would like to be able to carve out a logically separate subset of folks I interact with, but in a more "private" way. I still want the interactions to be "asynchronous" and I don't want to have to use another platform, they're already on Yarn.social 😅
prologic
twtxt.net
View Thread
@eaplmx

> I’ve read the whole RFC 770, so I think I understand the result, but not the why.

So basically the "Why" is quite simple; As a User of Yarn.social I would like to be able to carve out a logically separate subset of folks I interact with, but in a more "private" way. I still want the interactions to be "asynchronous" and I don't want to have to use another platform, they're already on Yarn.social 😅
prologic
twtxt.net
View Thread
The primary two use-cases that are driving this for me are:

- I want to introduce my daughter to "social media" soon (_this year_) and I want her to be safe and "supervised". No-one but her "guardian" and other "young Yarners" (_with the same parental/guardian supervision_) should be able to see the contents of her Twts.
- I want to occasionally share Twts (_with potentially media_) with my family and close friends using the same platform, and _hopefully_ / _ideally_ with the same User Experience we've developed so far here.
prologic
twtxt.net
View Thread
The primary two use-cases that are driving this for me are:

- I want to introduce my daughter to "social media" soon (_this year_) and I want her to be safe and "supervised". No-one but her "guardian" and other "young Yarners" (_with the same parental/guardian supervision_) should be able to see the contents of her Twts.
- I want to occasionally share Twts (_with potentially media_) with my family and close friends using the same platform, and _hopefully_ / _ideally_ with the same User Experience we've developed so far here.
eaplmx
twtxt.net
View Thread
@prologic Love the async part! Go for it!
prologic
twtxt.net
View Thread
@eaplmx I believe we'll he the first social media to support e2e encryption 😆
prologic
twtxt.net
View Thread
@eaplmx I believe we'll he the first social media to support e2e encryption 😆