# 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 11
# self = https://watcher.sour.is/conv/iwzloka
@tamer Hey, that's actually quite a nice idea with the mobile phone app pulling raw twtxt feeds rather than over a custom API. (Disclaimer: I never used it and most likely never will). But that sounds true twtxt. On the other hand, all the – let's call it yarnd improvements – are harder to integrate.
@lyse @tamer It's a "balance" honestly. Whilst it _might_ be a nice idea et all, it _might_ now work out on a practical level. What _would_ work however is adding better support to the Mobile App for "offline" use -- as-in it isn't always required to be "online" as such. Cache as much as possible, Post for later when back online and connected to your Pod.
The greater vision here one day is that your "Pod" will actually be part of your Home 😅 -- Okay meby @lyse will never run one, but that's because he has his own "Yarn"-compatible client 😅
@lyse @tamer It's a "balance" honestly. Whilst it _might_ be a nice idea et all, it _might_ now work out on a practical level. What _would_ work however is adding better support to the Mobile App for "offline" use -- as-in it isn't always required to be "online" as such. Cache as much as possible, Post for later when back online and connected to your Pod.
The greater vision here one day is that your "Pod" will actually be part of your Home 😅 -- Okay meby @lyse will never run one, but that's because he has his own "Yarn"-compatible client 😅
@lyse that is a horrible idea. A mobile device isn't a server. Having a mobile device pull raw twtxt feeds from everywhere on an ongoing bases, will be, at the very least, tolling on the device's battery. Just as you, or even further, I will never use such thing.
@lyse that is a horrible idea. A mobile device isn't a server. Having a mobile device pull raw twtxt feeds from everywhere on an ongoing bases, will be, at the very least, tolling on the device's battery. Just at you, or even further, I will never use such thing.
@fastidious Well to be fair you would probably not build it as a server with constant polling but as an app that fetched feeds like an RSS Reader. But the experience would suck really.
And where would you host your own feed?! On your 5G connection from your phone?! 🤣
@fastidious Well to be fair you would probably not build it as a server with constant polling but as an app that fetched feeds like an RSS Reader. But the experience would suck really.
And where would you host your own feed?! On your 5G connection from your phone?! 🤣
@prologic you wrote "*but as an app that fetched feeds like an RSS Reader*". RSS is one way only, and, yes, it has customisable---but relatively slow---pulling intervals (or just pulls when the app is open). It is not a dual channel of communication. For mobile, I would rather have a server do that job, so that my mobile only talks to it.
@tamer Scuttlebutt does something like this I believe? 🤔
@tamer Scuttlebutt does something like this I believe? 🤔
Perhaps you already had a long discussion about centralization vs federation vs decentralization, network effect, availability, single point of failure, replication, privacy-oriented services, self-sustainability and more.
All of them are pulling forces, modelling the shape of a product/service/system surrounding it with ideas, beliefs, ideology, philosophy, humans livings with machines, thousands of 'standards', and such...
XKCD - Standards
Aaaand, that's good!