# 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 6
# self = https://watcher.sour.is/conv/qw62i6q
@prologic woohoo! š„³š The hard part is done. Maintaining it now is ease pease.
Slightly off topic, but still on it. I have thought about the timeline, and I think it will greatly be improved with an ever fetching, ānever endingā approach.
How difficult would that be to implement?
youāre actually talking about an infinite scroll timeline which is actually something that the mobile app implements.
unfortunately it is absolutely impossible to do this server-side of course with the current default theme so a completely new theme i.e a SPA would have to be developed and it would be quite JavaScript heavy and I donāt think this is something that you could easily do graceful fallback on š¤
youāre actually talking about an infinite scroll timeline which is actually something that the mobile app implements.
unfortunately it is absolutely impossible to do this server-side of course with the current default theme so a completely new theme i.e a SPA would have to be developed and it would be quite JavaScript heavy and I donāt think this is something that you could easily do graceful fallback on š¤
@prologic ah, I see! Eventually things will have to happen though. I mean, imagine if city governments required that everyone use horse drawn carriages. Or if we were to still sail across the oceans using wind as propulsion. Things change, and the old, well, is left behind.
Anyway, not an easy feat. The new timeline approach on issues looks more doable. š
@fastidious It will happen eventually for sure, but it _may_ just be "another theme" if that makes sense. With a decent amount of backend code + template refactoring and cleanup, it _could_ be done in such a way to support both server-side and SPA (_driven by an API_) without duplicating ocde across API endpoints and Server-side Handlers.
@fastidious It will happen eventually for sure, but it _may_ just be "another theme" if that makes sense. With a decent amount of backend code + template refactoring and cleanup, it _could_ be done in such a way to support both server-side and SPA (_driven by an API_) without duplicating ocde across API endpoints and Server-side Handlers.