@mckinley@twtxt.net I must admit I was tempted to use EndeavourOS for an install on a HTPC (N97 mini PC) when it arrives to quickly get up and running, but then again I haven’t done a fresh install of Arch in quite a while so it sounds like things have simplified even more since then. Hmm…

I love Arch but they could probably do to have some of these warnings come down pacman itself

There is JavaScript, but not everything is implemented (properly). They’re writing everything including the JavaScript engine from scratch.

A huge effort 😲

@prologic@twtxt.net Very nice 👌

Very cool! Interestingly using your web app, the result was a higher bitrate than when I downloaded the best audio only option in yt-dlp (258 kbit/s vs 140 kbit/s).

Don’t quite understand that but nice work 😅

The whole gift card thing is crazy. You get scammers calling up people pretending to be from the IRS (just one example) and getting people paying with gift cards 😳

@prologic@twtxt.net Perfect 👌

@movq@www.uninformativ.de Golly, you are right 😅

Oh no, don’t tempt me. I’ve been on KDE for a while to not tinker and make it possible for my Windows using partner to use my laptop now and then, I’m trying to avoid the dwm/l addiction 🤣

@prologic@twtxt.net phew 😁

@prologic@twtxt.net yep pretty much!

Could you perhaps just have a check box to do the opposite, like “Don’t remember me”? I’ve seen that a couple of places I think. Sort of an opt in short lived login, if you’re at a public library or something etc.

@prologic@twtxt.net hey mate, all working well here so far. The login issue isn’t really an issue as far as actually logging in goes, rather if I get my password wrong it gives the response error code in console, the response of which contains the HTML for the wrong password page if you inspect it, but on the frontend itself nothing actually happens which is the confusion. Just stays on the login page as if it was never submitted. Am I alone in having this issue as well?

@prologic@twtxt.net Yes very very strange! I truly don’t know where to start on that one 🤣 Must be one of those really weird edge cases. Thanks for your help on this, I can at least post normally now.👌

I’ll check logging in etc tomorrow, time for bed lol 😴

Test

EDIT: Okay, convo works properly now at least

@prologic@twtxt.net It’s weird though cos I could reproduce it on any of my browsers on either my laptop or phone 🤔

@prologic@twtxt.net Firefox 126.0.1 is my primary

@prologic@twtxt.net Fix works!

Test

@prologic@twtxt.net Woops my blockquote got mangled but you get the gist haha

@prologic@twtxt.net I was wondering if my reverse proxy could cause something but it’s pretty standard…

server {

    listen 80;
    server_name we.loveprivacy.club;

    location / {
            return 301 https://$host$request_uri;
            <a href="https://yarn.girlonthemoon.xyz/search?q=%23proxy_pass">#proxy_pass</a> http://127.0.0.1:8000;
    }

}
server {

    listen 443 ssl http2;
    server_name we.loveprivacy.club;

    ssl_certificate /etc/letsencrypt/live/we.loveprivacy.club/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/we.loveprivacy.club/privkey.pem;

    client_max_body_size 8M;

    location / {
            proxy_pass http://127.0.0.1:8000;
    }

}

Test

@prologic@twtxt.net Firefox but it happens on Brave and Chromium on my laptop, or any browser (Brave, Chromium, Vanadium) I try on my Android phone.

@prologic@twtxt.net Sorry, my messages don’t get included in the current convo unless I tag you. Guess something gets lossed in translation with this weird posting issue. ANYWAY, it is rather perplexing. Clearly only an issue on my Pod, but what could the source of it be 🤔

Yeah sorry just realised, but just checked again and the referrer is the same (/post) on either the POST or the GET 🤔

Testing

Indeed /post is referrer…

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

@prologic@twtxt.net Okay lemme see

@prologic@twtxt.net Yeah realised I hit the character limit lol

Hmm…

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

@prologic@twtxt.net The login issue I cant yet narrow down as to when it happens as sometimes I login fine. But it gives off a 401 forbidden error. Anyway I’ve been focusing on the posting error as I figured it must be related. Registering and logging in as a new user works every time, which is weird.

@bender@we.loveprivacy.club hmm you may be right…

Unfortunately not on that front. Still the same 404 posting errors and oddly occasional login errors.

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.

Haha, yeah sorry about that, I wasn’t even trying to nuke the database either but it worked out that way 😩

I guess it got rid of all the dead spam bot accounts at least 🤣

@prologic@twtxt.net Correct… epic fail 🤣 Been a long day and I just wasn’t thinking, nor backing up properly. Oops indeed. My usual errors still exist though.

@prologic@twtxt.net Righteo, so rookie error - I obviously had some untracked, rather important files for starting my pod and I ran a 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@twtxt.net 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…