# 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 59
# self = https://watcher.sour.is/conv/yzul4yq
Ah! I just use the web client for both!
@adi Can't you just pack the current web frontend in a chromium on mobile too?
@adi Can't you just pack the current web frontend in a chromium on mobile too?
@adi Can't you just pack the current web frontend in a chromium on mobile too?
@adi That's how good it is IMO.
@adi That's how good it is IMO.
@adi That's how good it is IMO.
> Can’t you just pack the current web frontend in a chromium on mobile too?
No because it's actually all a server-side rendered web app. It _actually_ works mostly just fine without Javascript enabled at all 😀 (_except media uploads_).
> Can’t you just pack the current web frontend in a chromium on mobile too?\n\nNo because it's actually all a server-side rendered web app. It _actually_ works mostly just fine without Javascript enabled at all 😀 (_except media uploads_).
> Can’t you just pack the current web frontend in a chromium on mobile too?\n\nNo because it's actually all a server-side rendered web app. It _actually_ works mostly just fine without Javascript enabled at all 😀 (_except media uploads_).
> Can’t you just pack the current web frontend in a chromium on mobile too?
No because it's actually all a server-side rendered web app. It _actually_ works mostly just fine without Javascript enabled at all 😀 (_except media uploads_).
> That’s how good it is IMO.
I'm glad you like it 🤗
> That’s how good it is IMO.
I'm glad you like it 🤗
> That’s how good it is IMO.\n\nI'm glad you like it 🤗
> That’s how good it is IMO.\n\nI'm glad you like it 🤗
@prologic That's the idea, keep it like it is and distribute in the Play Store wrapped in a Chromium instance. I'm sure there's a way.
@prologic That's the idea, keep it like it is and distribute in the Play Store wrapped in a Chromium instance. I'm sure there's a way.
@prologic That's the idea, keep it like it is and distribute in the Play Store wrapped in a Chromium instance. I'm sure there's a way.
@adi That doesn't really work. If you go install Goryon on a mobile device now you'll see why. It prompts you for a "Pod URL" on startup to either login to or register to. -- "Decentralised". 😀
@adi That doesn't really work. If you go install Goryon on a mobile device now you'll see why. It prompts you for a "Pod URL" on startup to either login to or register to. -- "Decentralised". 😀
@adi That doesn't really work. If you go install Goryon on a mobile device now you'll see why. It prompts you for a "Pod URL" on startup to either login to or register to. -- "Decentralised". 😀
@prologic Not that hard to solve, don't think it requires a new client IMO.
@prologic Not that hard to solve, don't think it requires a new client IMO.
@prologic Not that hard to solve, don't think it requires a new client IMO.
@adi Packaging it all up with a Chrome instance ala Electron isn't really viable IHMO. OTOH I'm also _thinking_ that this isn't a problem to be solved per se. Or rather, I'm not best suited to creating/maintaining a PWA client in the first place. I _should_ probably just focus on what I _am_ good at and continue improving the backend, API and continue my plans for the CLi client (_which would also improve the backend API for other clients_). I'm sort of realizing that having _many_ clients each with their own feature(s) isn't such a bad thing...
@adi Packaging it all up with a Chrome instance ala Electron isn't really viable IHMO. OTOH I'm also _thinking_ that this isn't a problem to be solved per se. Or rather, I'm not best suited to creating/maintaining a PWA client in the first place. I _should_ probably just focus on what I _am_ good at and continue improving the backend, API and continue my plans for the CLi client (_which would also improve the backend API for other clients_). I'm sort of realizing that having _many_ clients each with their own feature(s) isn't such a bad thing...
@adi Packaging it all up with a Chrome instance ala Electron isn't really viable IHMO. OTOH I'm also _thinking_ that this isn't a problem to be solved per se. Or rather, I'm not best suited to creating/maintaining a PWA client in the first place. I _should_ probably just focus on what I _am_ good at and continue improving the backend, API and continue my plans for the CLi client (_which would also improve the backend API for other clients_). I'm sort of realizing that having _many_ clients each with their own feature(s) isn't such a bad thing...
In order words, focus on what makes Twtxt the spec/format and Twtxt the backend great. Keep working on cross-pod functionality, discovery, etc...
In order words, focus on what makes Twtxt the spec/format and Twtxt the backend great. Keep working on cross-pod functionality, discovery, etc...
In order words, focus on what makes Twtxt the spec/format and Twtxt the backend great. Keep working on cross-pod functionality, discovery, etc...
@prologic I guess each client is responsible for keeping up with new features? The web client being the reference implementation?
@prologic I guess each client is responsible for keeping up with new features? The web client being the reference implementation?
@prologic I guess each client is responsible for keeping up with new features? The web client being the reference implementation?
That's what it has been since we started this journey back in Aug. Yes.
That's what it has been since we started this journey back in Aug. Yes.
That's what it has been since we started this journey back in Aug. Yes.
@adi To be honest... At this point in the project it is becoming more and more important to have a single client that works across Desktop, Mobile and Web. I'm not sure what's happening with @dooven who is the author of the Goryon mobile app for iOS/Android, but if I don't come up with something viable that is easy to maintain and develop for me (_because contributors do come and go_) the project risks running out "stream" so to speak.
@adi To be honest... At this point in the project it is becoming more and more important to have a single client that works across Desktop, Mobile and Web. I'm not sure what's happening with @dooven who is the author of the Goryon mobile app for iOS/Android, but if I don't come up with something viable that is easy to maintain and develop for me (_because contributors do come and go_) the project risks running out "stream" so to speak.
@adi To be honest... At this point in the project it is becoming more and more important to have a single client that works across Desktop, Mobile and Web. I'm not sure what's happening with @dooven who is the author of the Goryon mobile app for iOS/Android, but if I don't come up with something viable that is easy to maintain and develop for me (_because contributors do come and go_) the project risks running out "stream" so to speak.
@prologic @dooven Ah, I thought you yourself were settled on developing a single client (the web one) for the reasons mentioned here: https://twtxt.net/twt/mk3zkcq. I guess you would like to have somebody else rather than you develop a single client that you could develop and maintain. So again, what would happen with this client in that case?
@prologic @dooven Ah, I thought you yourself were settled on developing a single client (the web one) for the reasons mentioned here: https://twtxt.net/twt/mk3zkcq. I guess you would like to have somebody else rather than you develop a single client that you could develop and maintain. So again, what would happen with this client in that case?
@prologic @dooven Ah, I thought you yourself were settled on developing a single client (the web one) for the reasons mentioned here: https://twtxt.net/twt/mk3zkcq. I guess you would like to have somebody else rather than you develop a single client that you could develop and maintain. So again, what would happen with this client in that case?
@dooven @adi Not sure to be honest. nothin concrete at this stage just ideas floating around
@dooven @adi Not sure to be honest. nothin concrete at this stage just ideas floating around
@dooven @adi Not sure to be honest. nothin concrete at this stage just ideas floating around
@prologic @adi no matter what you're doing, Electron is NEVER the answer. just say no.
@prologic @adi no matter what you're doing, Electron is NEVER the answer. just say no.
@adi @deadguy Don’t worry we’re not touching Electeon with a 100ft pole 🤣
@adi @deadguy Don’t worry we’re not touching Electeon with a 100ft pole 🤣
@adi @deadguy Don’t worry we’re not touching Electeon with a 100ft pole 🤣