# 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/6j2mb4q
Granted I wish Nextcloud itself wasn't a PHP driven behemoth, but that's another story 😆 But it has made a lot of that transition off typical cloud services easy.
@prologic some day I would genuinely like to look at lightweight alternatives to Nextcloud as I think we have mentioned before, possibly have to build one, but replacing WebDAV etc is a problem 😥
@eldersnake \n\n> some day I would genuinely like to look at lightweight alternatives to Nextcloud as I think we have mentioned before, possibly have to build one, but replacing WebDAV etc is a problem 😥\n\nIt's next on my roadmap after _perfecting_ Yarn.social -- Part of what I plan to do with Self Hosted Pty Ltd 👌
@eldersnake
> some day I would genuinely like to look at lightweight alternatives to Nextcloud as I think we have mentioned before, possibly have to build one, but replacing WebDAV etc is a problem 😥
It's next on my roadmap after _perfecting_ Yarn.social -- Part of what I plan to do with Self Hosted Pty Ltd 👌
@eldersnake
> some day I would genuinely like to look at lightweight alternatives to Nextcloud as I think we have mentioned before, possibly have to build one, but replacing WebDAV etc is a problem 😥
It's next on my roadmap after _perfecting_ Yarn.social -- Part of what I plan to do with Self Hosted Pty Ltd 👌
notes.mills.io and files.mills.io are my early attempts at solving both Document and File sharing. Needs much more work though. Calendaring/Eventing however I _feel_ needs to be solved another way, CalDav/CardDav is just an insane over-engineered and over-compliated spec 😢
notes.mills.io and files.mills.io are my early attempts at solving both Document and File sharing. Needs much more work though. Calendaring/Eventing however I _feel_ needs to be solved another way, CalDav/CardDav is just an insane over-engineered and over-compliated spec 😢
For now I just run an instance of Baïkal for CardDav/CalDAV; which I haven't gotten my wife (@kt84) onto just yet...
> Baïkal
> Lightweight CalDAV+CardDAV server
For now I just run an instance of Baïkal for CardDav/CalDAV; which I haven't gotten my wife (@kt84) onto just yet...\n\n> Baïkal\n> Lightweight CalDAV+CardDAV server
For now I just run an instance of Baïkal for CardDav/CalDAV; which I haven't gotten my wife (@kt84) onto just yet...
> Baïkal
> Lightweight CalDAV+CardDAV server
@prologic oh nice, I didn't know about Baikal. But yes, why does *Dav have to be so over complicated 😔*
@eldersnake
> But yes, why does *Dav have to be so over complicated 😔
Because the IETF folk behind the standards were _trying_ to make *DAV do too much.
Something we have to be careful with when spec'ing out the standards and specifications for Yarn.social based on and around the Twtxt spec. At some point we'll write up a whole new v2 spec that documents everything.
@eldersnake \n\n> But yes, why does *Dav have to be so over complicated 😔\n\nBecause the IETF folk behind the standards were _trying_ to make *DAV do too much.\n\nSomething we have to be careful with when spec'ing out the standards and specifications for Yarn.social based on and around the Twtxt spec. At some point we'll write up a whole new v2 spec that documents everything.
@eldersnake
> But yes, why does *Dav have to be so over complicated 😔
Because the IETF folk behind the standards were _trying_ to make *DAV do too much.
Something we have to be careful with when spec'ing out the standards and specifications for Yarn.social based on and around the Twtxt spec. At some point we'll write up a whole new v2 spec that documents everything.
@prologic Ooo, I see. 👀 Yeah, I've been having problems with Nextcloud, and wasn't totally happy with it even before that.