Hi DoneAgain,
There are really two separate issues here, and you may be running into both at once.
First, If you’re still on 5.2.x, upgrading to 5.3.0 is worth it anyway: that branch includes several RSS/Atom improvements, including feed auto-discovery and better category feed URLs. 5.4.x goes further with feed date formatting and slug-based category URLs. Neither release fixes the authentication issue you’re describing, but it’s easier to debug feed behavior on a current version.
On the actual problem: start with the easy check. Special characters in the password can break URL parsing. A plain @ in the password can be interpreted as the separator between credentials and hostname, which silently truncates the rest. Percent-encode them in the URL: @ becomes %40, # becomes %23, : becomes %3A, and % becomes %25. For example, p@ss#word should become p%40ss%23word.
If it still doesn’t work after encoding, you’ve probably hit the real limitation: Flatboard uses session cookies, not HTTP Basic Auth. The user:pass@url trick sends an Authorization: Basic ... header, which Flatboard ignores; it doesn’t recognize that as a login, so you’ll still appear as a guest.
What can actually work is using an RSS reader that can keep an authenticated session cookie. FreshRSS and Miniflux both support feeds behind a login, and Thunderbird may also keep a session cookie if you log into the forum first through its built-in browser. The idea is to authenticate normally first and let the reader reuse the cookie, with no credentials embedded in the feed URL.