# 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/vk6rbra
@david Which is why I forked ๐ -- Actually building a self-hosted "Pages" type hosting is something on my list of things to build ๐
@david Which is why I forked ๐ -- Actually building a self-hosted "Pages" type hosting is something on my list of things to build ๐
@prologic that would be a good contribution to Gitea. Gogs is harder because the project owner is very pickyโand rather slowโaccepting PRs.
@david I wouldn't build it for Gitea -- I'd built it as a "standalone" thing you can stand up. Gitea would be "welcome" to integrate with it however ๐
-- Consider it like standing up an instance of _say_ pagesd that you can basically either point Git repos at or connect Web hooks to and it automatically takes care of everything for you, routing, TLS, building, etc, etc. All you have to do is run it and setup a domain/sub-domain and configure some Let's Encrypt stuff.
Yes you could do all this by hand, but that's because we know what we're doing ๐
@david I wouldn't build it for Gitea -- I'd built it as a "standalone" thing you can stand up. Gitea would be "welcome" to integrate with it however ๐
-- Consider it like standing up an instance of _say_ pagesd that you can basically either point Git repos at or connect Web hooks to and it automatically takes care of everything for you, routing, TLS, building, etc, etc. All you have to do is run it and setup a domain/sub-domain and configure some Let's Encrypt stuff.
Yes you could do all this by hand, but that's because we know what we're doing ๐
@prologic I am genuinely curious. Why a feature that has being requested for a long time on a software we use everyday wouldn't be a good thing to do, and contribute back to it? I think that feature will benefit Gitea, and people using it, a lot. Gitea has repos, and web hooks, and it is written in Golang. Anyways, just curiosity, that's all.
@prologic I am seriously curious. Why a feature that has being requested for a long time on a software we use everyday wouldn't be a good thing to do, and contribute back to it? I think that feature will benefit Gitea, and people using it, a lot. Gitea has repos, and web hooks, and it is written in Golang. Anyways, just curiosity, that's all.
@david I didn't necessarily say I wouldn't contribute said feature to Gitea, I said I would built it as a separate thing. Like WebSub I'm trying to build for yarnd, often in software development when building non-trivial things, it's often better to build them separately with a good design, think library, good interfaces , etc. Then integrate later.
@david I didn't necessarily say I wouldn't contribute said feature to Gitea, I said I would built it as a separate thing. Like WebSub I'm trying to build for yarnd, often in software development when building non-trivial things, it's often better to build them separately with a good design, think library, good interfaces , etc. Then integrate later.