# 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 12
# self = https://watcher.sour.is/conv/jtwsmaa
@abucci This is quite hard to do really. Because the "web app" is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I'm also working in parallel on a way to "embed" Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im -- If we can pull that off, it'll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌
@abucci This is quite hard to do really. Because the "web app" is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I'm also working in parallel on a way to "embed" Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im -- If we can pull that off, it'll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌
@abucci This is quite hard to do really. Because the "web app" is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I'm also working in parallel on a way to "embed" Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im -- If we can pull that off, it'll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌
@abucci This is quite hard to do really. Because the "web app" is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I'm also working in parallel on a way to "embed" Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im -- If we can pull that off, it'll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌
@abucci Yeah like I said it's being worked on slowly 🤞
@abucci Yeah like I said it's being worked on slowly 🤞
@abucci Yeah like I said it's being worked on slowly 🤞
@abucci Yeah like I said it's being worked on slowly 🤞