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.
>GET /post HTTP/2
Host: we.loveprivacy.club
[...]
HX-Request: true
HX-Target: content
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post
>
Referrer is /post and not / or /discover like it should be. Can we confirm/deny this if you inspect the POST /post requests? ๐คSee this code
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? ๐คSee this code
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? ๐คSee this code
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.
>Jun 19 23:31:38 yarn_init.sh[61567]: [yarnd] 2024/06/19 23:31:38 (127.0.0.1:40254) "POST /post HTTP/
1.0" 200 0 3.402208ms
[...]
>
> Jun 19 23:31:39 yarn_init.sh[61567]: [yarnd] 2024/06/19 23:31:39 (127.0.0.1:40262) "GET /post HTTP/1.0" 404 729 123.474001ms
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
for every post there should be a
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
for every post there should be a
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>
Oh well ๐ It works wonderfully!
In the event of a database corruption or loss:
$ 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>
Oh well ๐ It works wonderfully!
In the event of a database corruption or loss:
$ URL=http://10.0.0.164:8000 ./tools/backup_db.sh > db.json
mv db.json data/db.restore.json
yarnd ...
That's why I was wondering if using Go 1.22.4 could be an issue. I don't know how exactly. Only way to test is to rebuild it with an older version I guess, which is why I did the make clean in the first place. Old habits die hard lol.
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).Another thing I noticed which was the reason I ran
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...
In the long run, Iโm going to effectively fork dwl. Iโm very glad that this project exists, saves me a lot of work. I think this is the only way forward for me โ any other compositor out there requires making too many sacrifices.
The big question is: How stable is wlroots (the underlying Wayland library)? There appear to be _a lot_ of breaking changes in each release, these are the last two releases:
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.17.0
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.16.0
Will I have the resources to keep up with that? Maybe itโs _still_ too early to begin this journey. ๐ค
In the long run, Iโm going to effectively fork dwl. Iโm very glad that this project exists, saves me a lot of work. I think this is the only way forward for me โ any other compositor out there requires making too many sacrifices.
The big question is: How stable is wlroots (the underlying Wayland library)? There appear to be _a lot_ of breaking changes in each release, these are the last two releases:
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.17.0
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.16.0
Will I have the resources to keep up with that? Maybe itโs _still_ too early to begin this journey. ๐ค
In the long run, Iโm going to effectively fork dwl. Iโm very glad that this project exists, saves me a lot of work. I think this is the only way forward for me โ any other compositor out there requires making too many sacrifices.
The big question is: How stable is wlroots (the underlying Wayland library)? There appear to be _a lot_ of breaking changes in each release, these are the last two releases:
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.17.0
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.16.0
Will I have the resources to keep up with that? Maybe itโs _still_ too early to begin this journey. ๐ค
In the long run, Iโm going to effectively fork dwl. Iโm very glad that this project exists, saves me a lot of work. I think this is the only way forward for me โ any other compositor out there requires making too many sacrifices.
The big question is: How stable is wlroots (the underlying Wayland library)? There appear to be _a lot_ of breaking changes in each release, these are the last two releases:
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.17.0
- https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.16.0
Will I have the resources to keep up with that? Maybe itโs _still_ too early to begin this journey. ๐ค
yarnd and there's enough interest, it _could_ become a user preference.
yarnd and there's enough interest, it _could_ become a user preference.
-
^n (Ctrl+n) -- Compose new Twt-
Esc (Escape) -- Close the composer-
^t (Ctrl+t) -- Refresh or navigate to Timeline-
^m (Ctrl+m) -- Refresh or navigate to Mentions-
^d (Ctrl+d) -- Refresh or navigate to DiscoverThere are shortcuts for Feeds, Settings and Profile too (_similiarly_))
-
^n (Ctrl+n) -- Compose new Twt-
Esc (Escape) -- Close the composer-
^t (Ctrl+t) -- Refresh or navigate to Timeline-
^m (Ctrl+m) -- Refresh or navigate to Mentions-
^d (Ctrl+d) -- Refresh or navigate to DiscoverThere are shortcuts for Feeds, Settings and Profile too (_similiarly_))
^n, then @ and then bender<TAB> and the rest of this twt, finally ^ENTER_)
^n, then @ and then bender<TAB> and the rest of this twt, finally ^ENTER_)