# 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 9
# self = https://watcher.sour.is/conv/tspjera
How I build web frontends in Go - Philipp Tanlak -- Hmmm 🤔 Thinking about how I've been strutting my Go Web Applications, the Templates, the Backend handler(s) and so on... This guy's approach is _quite intriguing..._ -- as it _might_ help cleanup this massive "God object" of a Context that has grown over time in yarnd's codebase... What do y'all think of this approach @lyse / @xuu ? 🤔
How I build web frontends in Go - Philipp Tanlak -- Hmmm 🤔 Thinking about how I've been strutting my Go Web Applications, the Templates, the Backend handler(s) and so on... This guy's approach is _quite intriguing..._ -- as it _might_ help cleanup this massive "God object" of a Context that has grown over time in yarnd's codebase... What do y'all think of this approach @lyse / @xuu ? 🤔
How I build web frontends in Go - Philipp Tanlak -- Hmmm 🤔 Thinking about how I've been strutting my Go Web Applications, the Templates, the Backend handler(s) and so on... This guy's approach is _quite intriguing..._ -- as it _might_ help cleanup this massive "God object" of a Context that has grown over time in yarnd's codebase... What do y'all think of this approach @lyse / @xuu ? 🤔
How I build web frontends in Go - Philipp Tanlak -- Hmmm 🤔 Thinking about how I've been strutting my Go Web Applications, the Templates, the Backend handler(s) and so on... This guy's approach is _quite intriguing..._ -- as it _might_ help cleanup this massive "God object" of a Context that has grown over time in yarnd's codebase... What do y'all think of this approach @lyse / @xuu ? 🤔
@prologic It's not all that different from yarns/yarnd what this dude does. Just the gigantic Context is broken up into multiple smaller ones and also having some unnecessary helper functions for them in my opinion. But I'm all for multiple contexts. This helps to properly cut things. Please don't do it before my yarns MR is merged, though, or I have to rework that one. :-D
What's much more important in my opinion is to find an elegant way to support multiple content types. I've never seen something, that handles this nicely and kind of automatically. Especially with errors. There are probably lots of libraries out there that bolt that on, but I bet they bring in a gazillion of dependencies, so I do not consider them valid solutions.
@lyse Thanks for your thougjts 👌 I have some ideas on this I'd like to try but probably not on the yarnd codebase yet 😆
@lyse Thanks for your thougjts 👌 I have some ideas on this I'd like to try but probably not on the yarnd codebase yet 😆
@lyse Thanks for your thougjts 👌 I have some ideas on this I'd like to try but probably not on the yarnd codebase yet 😆
@lyse Thanks for your thougjts 👌 I have some ideas on this I'd like to try but probably not on the yarnd codebase yet 😆