# 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/dzmkf4a
Anyone interesting in distributed file systems? Specifically interested in contributing ideas, code, testing of something I'm working on? πŸ€”
Anyone interesting in distributed file systems? Specifically interested in contributing ideas, code, testing of something I'm working on? πŸ€”
@prologic maybe. is it something for twtxt/yarn, that can be used for hosting people's twtxt.txt? I had a look at cabal.chat yesterday that seem to have something like this going for it, but it was still very buggy.
Yeah, what'd you have in mind?
Yeah, what'd you have in mind?
@darch It’s nothing to do with twtxt/yarn sorry 😁
@darch It’s nothing to do with twtxt/yarn sorry 😁
@anth So far I've basically put together some of the building blocks. A blobserver, some basic metadata thing (_not quite a server yet_) and some basic CRUD operations on files (_create/read_). I'm using Reed Solomon Erasure Encoding for data durability and redundancy. I _could_ use some guidance, help, code contributions, battle testers, etc. I'm at a point where now where I need to think about how to structure the "clustering" and "metdata" -- ideally masterless. Then I'll work on integrating a FUSE layer on top. Still interested? πŸ€”_
@anth So far I've basically put together some of the building blocks. A blobserver, some basic metadata thing (_not quite a server yet_) and some basic CRUD operations on files (_create/read_). I'm using Reed Solomon Erasure Encoding for data durability and redundancy. I _could_ use some guidance, help, code contributions, battle testers, etc. I'm at a point where now where I need to think about how to structure the "clustering" and "metdata" -- ideally masterless. Then I'll work on integrating a FUSE layer on top. Still interested? πŸ€”_
Potentially. What environment/language(s) are you working in? I'd dump fuse for 9p, personally :-)
Potentially. What environment/language(s) are you working in? I'd dump fuse for 9p, personally :-)
@anth I'm using Go to implement this. Developing on macOS, plan to support BSD and Linux. 9p sounds great, but I have zero experience or access to such :D
@anth I'm using Go to implement this. Developing on macOS, plan to support BSD and Linux. 9p sounds great, but I have zero experience or access to such :D