# 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 196300 # self = https://watcher.sour.is?offset=164856 # next = https://watcher.sour.is?offset=164956 # prev = https://watcher.sour.is?offset=164756
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
Referer. There is simply no way to be on the /post endpoint normally anyway.
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
Referer. There is simply no way to be on the /post endpoint normally anyway.
POST /post XHR (_that is being run by htmx_) should never, ever be Referer: .../post ๐คฆโโ๏ธ
POST /post XHR (_that is being run by htmx_) should never, ever be Referer: .../post ๐คฆโโ๏ธ
/post) on either the POST or the GET ๐ค
POST /post request itself. That's the Referer that's looked up and used as the redirect.
POST /post request itself. That's the Referer that's looked up and used as the redirect.
Referrer is /post and not / or /discover like it should be. Can we confirm/deny this if you inspect the POST /post requests? ๐คg
if htmx.IsHTMX(r) {
htmx.NewResponse().
Location(RedirectRefererURL(r, s.config, "/")).
Write(w)
} else {
http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}
Referrer is /post and not / or /discover like it should be. Can we confirm/deny this if you inspect the POST /post requests? ๐คg
\t\tif htmx.IsHTMX(r) {
\t\t\thtmx.NewResponse().
\t\t\t\tLocation(RedirectRefererURL(r, s.config, "/")).
\t\t\t\tWrite(w)
\t\t} else {
\t\t\thttp.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
\t\t}
Referrer is /post and not / or /discover like it should be. Can we confirm/deny this if you inspect the POST /post requests? ๐คg
if htmx.IsHTMX(r) {
htmx.NewResponse().
Location(RedirectRefererURL(r, s.config, "/")).
Write(w)
} else {
http.Redirect(w, r, RedirectRefererURL(r, s.config, "/"), http.StatusFound)
}
GET /, You are right that a POST /post does an internal XHR redirect to whatever view you're on to refresh it.
GET /, You are right that a POST /post does an internal XHR redirect to whatever view you're on to refresh it.
GET /post -- There is no handler/route for that, that *will* indeed 404, really strange you're still seeing this? And what's this login issue?
GET /post -- There is no handler/route for that, that *will* indeed 404, really strange you're still seeing this? And what's this login issue?
DEBU[0163] no subscriptions found for http://10.0.0.164:8000/user/admin/twtxt.txt
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "POST /post HTTP/1.1" 200 0 8.323709ms
DEBU[0163] reloading templates in debug mode...
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "GET / HTTP/1.1" 200 18120 87.933208ms
POST /post ... followed pretty quickly by a GET /
DEBU[0163] no subscriptions found for http://10.0.0.164:8000/user/admin/twtxt.txt
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "POST /post HTTP/1.1" 200 0 8.323709ms
DEBU[0163] reloading templates in debug mode...
[yarnd] 2024/06/19 23:13:23 (10.0.0.164:64888) "GET / HTTP/1.1" 200 18120 87.933208ms
POST /post ... followed pretty quickly by a GET /
go v1.22.2 here, but I'll upgrade now just to be sure...
go v1.22.2 here, but I'll upgrade now just to be sure...
go v1.22.2 here, but I'll upgrade now just to be sure...
* 8eef4d5d - (HEAD -> main, origin/main) Add DB restore capability and tools/backu-_db.sh script (19 seconds ago) <James Mills>
$ URL=http://10.0.0.164:8000 ./tools/backup_db.sh > db.json
mv db.json data/db.restore.json
yarnd ...
* 8eef4d5d - (HEAD -> main, origin/main) Add DB restore capability and tools/backu-_db.sh script (19 seconds ago) <James Mills>
$ URL=http://10.0.0.164:8000 ./tools/backup_db.sh > db.json
mv db.json data/db.restore.json
yarnd ...
make clean. Why I originally had them in the git directory is anyone's guess. Anyway it blew away those files including the database so that's that. So your good self and @bender etc - apologies but your profiles got nuked as well (as did my own but easily recreated).make clean in the first place. I noticed my pod was being built with Go 1.22.4. Could this be a problem @prologic? preflight.sh actually errors out about it...