# 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 10
# self = https://watcher.sour.is/conv/xd6wama
Alright! Finally got everything set up to start working on the #pwa! 💪💪💪
I'll be working only on the #pwa repo and I've set a local proxy on a throwaway docker instance of yarnd as a local backend.
First will be to get all the API mapped and then I'll try to get everything to work with less graphics elements as i can at first. 🙃
For the rest I'll write down a quick list of the next steps to do as soon as I can.
Meanwhile feel free to give any suggestions/proposal/alternative on the UI or any questions/request for the project. 😜
@justamoment
> First will be to get all the API mapped and then I’ll try to get everything to work with less graphics elements as i can at first. 🙃
if you need new API endpoints written, LMK! I'm happy to accommodate those as quickly as you need them 👌 If you are on Signal we can also collaborate along with @ullarah a bit more in real-time if you like...
@justamoment
> First will be to get all the API mapped and then I’ll try to get everything to work with less graphics elements as i can at first. 🙃
if you need new API endpoints written, LMK! I'm happy to accommodate those as quickly as you need them 👌 If you are on Signal we can also collaborate along with @ullarah a bit more in real-time if you like...
@prologic Yes, thanks you.
For now I'll try to use what we have already, the API in dev.twtxt.net seems to cover most actions, the only APIs that are missing are one for reporting and the actions on twts (mute, bookmark, etc.) and one with the metadata of the pod too, (version, branch, references, etc.).
I'm not real time by nature 🥴 so I think working with issues and yarn should be enough for now.
@justamoment
The endpoints for /report and /support are open-ended endpoints, so there's no need for any "API" for these. They already exists. If you _feel_ that there _should_ be /api/v1 matching endpoints, that's fine, we can do that too 👌
Yes I _believe_ we are missing endpoints for /api/v1/mute, /api/v1/unmute and /api/v1/bookmarks. I can add all these pretty quickly.
> I’m not real time by nature 🥴 so I think working with issues and yarn should be enough for now.
No problems! I prefer Yarn too 👌 (async ftw 😂)
@justamoment
The endpoints for /report and /support are open-ended endpoints, so there's no need for any "API" for these. They already exists. If you _feel_ that there _should_ be /api/v1 matching endpoints, that's fine, we can do that too 👌
Yes I _believe_ we are missing endpoints for /api/v1/mute, /api/v1/unmute and /api/v1/bookmarks. I can add all these pretty quickly.
> I’m not real time by nature 🥴 so I think working with issues and yarn should be enough for now.
No problems! I prefer Yarn too 👌 (async ftw 😂)
@prologic Having everything under one endpoint is better for other integration too I think.
I'm missing endpoints because I didn't see them under the spec page, I should check the repo then, I'm also missing the response structure, but I can directly look it up later when working on the API.
@justamoment I will work on this fore you over the next coming days and tidy this up and fix the documentation. I already have a backlog issue for me to do this.
@justamoment I will work on this fore you over the next coming days and tidy this up and fix the documentation. I already have a backlog issue for me to do this.
@prologic Sure, I'll be working on the project plan and data layer in the meantime. 💪