she blinded me with science (science!)

Yearly blog post! Ft. NixOS because of course.

https://ersei.net/en/blog/lean-mean-solitaire-machine

favourite VM runtime

So I'm running into an issue with Finamp where it would send duplicate playback started and playback stopped events due to a race condition (possibly), which messed with ListenBrainz. I fixed it in the worst way possible: with Nginx fuckery

limit_req_zone $http_authorization zone=jfplaybackstopped:10m rate=10r/m;
limit_req_zone $http_authorization zone=jfplaybackstarted:10m rate=10r/m;

# ...

        location = /Sessions/Playing/Stopped {
                limit_req zone=jfplaybackstopped;
                limit_req_status 599;
                limit_conn_status 599;
                error_page 599 =204 'debounce';

                proxy_pass http://$jellyfin;
                include snippets.d/proxy.conf;

                add_header Cross-Origin-Resource-Policy cross-origin;
        }

        location = /Sessions/Playing {
                limit_req zone=jfplaybackstarted;
                limit_req_status 599;
                limit_conn_status 599;
                error_page 599 =204 'debounce';

                proxy_pass http://$jellyfin;
                include snippets.d/proxy.conf;

                add_header Cross-Origin-Resource-Policy cross-origin;
        }

we need error_page to be like this because limit_*_status only lets you return an error code from 400-599. It works perfectly to prevent the duplicated requests :) only issue I foresee is a song that's less than 6 seconds being played, but I don't think I listen to that, so I'll be fine.

Of course, I have to make sure that fail2ban doesn't see the rate limit trips and ban me...

send me some cool rss feeds to subscribe to

I wrote about Niri, the fancy scrollable-tiling window manager I switched to. ft: complaining about Sway!

https://ersei.net/en/blog/niri

criticise my website please I need to make it better

wrote a blog post from a plane. enjoy an overview of all the projects I have been working on but weren't blog post worthy

https://ersei.net/en/blog/updates-2024-12

I've made my own 88x31 button. It's running a turing-complete cellular automaton that I wrote since I didn't wanna animate the electrical bits by hand.

Source code: https://git.sr.ht/~fd/wire-button

so I put bad apple on rss

https://ersei.net/en/blog/bad-apple-rss

https://youtu.be/IJCxbql39qg

@frameworkcomputer can i have a free computer to review please i will put it on my website ersei.net (very popular)

if anyone is proficient with a screen reader, I wanna find out how accessible my website is

boosts welcome

New blog post: booting Linux off of Google Drive!

https://ersei.net/en/blog/fuse-root

httpd_execmem for php jit

give me book recommendations (boosts welcome)

help everything I know about cryptocurrency is from goosebumps 2

I wrote a thing about skateboarding and the meaning of life.

Mostly skateboarding tho

https://ersei.net/en/blog/sk8r

spending millions of dollars to convince @yassie_j to switch to my instance for marketing reasons

I keep finding bugs with federated apps and S3 integrations. Here's the latest:

Now that Synapse can accept redirects, it's got some strange behaviour. I have a Minio instance running that matrix-media-repo redirects Synapse to. However, Synapse sets the Authorization:X-Matrix... header, which causes Minio to return a 400 Invalid Request due to it expecting either no authorization or proper AWS4-HMAC-SHA256.

Currently, I have a fix in place by having Apache unset the Authorization header if it detects Synapse is requesting something from the S3 endpoint:

<If "%{HTTP:Authorization} =~ /X-Matrix/">
  RequestHeader unset "Authorization"
</If>

So my grand question is this: is this a Synapse bug (are headers meant to be kept when redirecting), a Minio bug (it should accept any authorization header if the bucket allows anonymous reads), or a matrix-media-repo bug?

Both Synapse and Minio are on the same subdomain, so it might be a connection reuse bug, which is the second time I've hit this issue in two days.

This is a direct consequence of MSC3860

f1r5t p0st!!1!