I just wanted to take a moment to acknowledge how amazing all of you are in working with this system. While this little bug might be frustrating, I’m confident we can figure it out. I’m committed to finding a solution and contributing to making this one of the best systems out there! Thank you for all the incredible work you do. (Besides I like breaking things... Why is it only on a Monday though, Mondays are my busiest days HAHA)

Ok, I may be the weird one here, but I want to display Powered by NodeBB on the forums of my site. Although it is not there, I know I can put it in a widget and display it in the global footer. But I am surprised that it isn't there by default. Did I accidently turn it off? Is it not there by default on the Peace Theme? Thought I would ask first.

Try now, if it doesn't work. Then log out and log in, it should work then

OK! So I officially HATE programming for WebSockets!!! Also it finally freaking works now... [image: 1734265101425-95a2487f-053a-44d7-842e-ce34ee7e8d22-image.png] tl;dr Let me preface this by saying that I’m usually more on the backend and systems side of development, where things are a bit more predictable. I’m not constantly pushing or pulling data dynamically, so WebSockets haven’t been a major part of my daily grind. Most of my interactions with them have been limited to fixing something trivial like an nginx.conf issue (you know, the "why isn’t this reverse proxy working?!" moments) or tweaking configuration for an existing setup. But then I decided to dive into actually developing a WebSocket implementation in NodeJS. Oh boy, was that an adventure. And by "adventure," I mean the kind where you’re stranded in a forest with no map, no snacks, no tent, no friends, no legs, no arms, and it’s starting to rain. Let's take an adventure together, shall we? Here are the main pain points I’ve encountered so far: The State Management Rabbit Hole WebSockets are a beast (you know the real word I wanted to use) when it comes to managing states. You have to keep track of which clients are connected, what data they should receive, and when to clean up stale connections. It’s like maintaining a live orchestra while random musicians keep joining and leaving mid-performance. Error Handling is a Nightmare Oh, you thought HTTP error codes were frustrating? Wait until you try debugging a WebSocket connection that mysteriously drops, reconnects, or worse, stays open but doesn’t actually work. The lack of clear error feedback is maddening. Concurrency, But Make It Fun... Not! Handling multiple connections simultaneously in NodeJS isn’t terrible in theory. But in practice, juggling all these connections and ensuring they don’t block each other feels like spinning plates on fire. Forget one plate, and suddenly your server’s on the floor. Protocol Nuances WebSocket communication requires a careful dance of handshakes and messages. Forget one small step, and everything crumbles. I definitely spent more time than I’d like to admit chasing down handshake errors that turned out to be... drumroll... a header issue. Testing Is a Whole Other Can of Worms Writing tests for WebSocket functionality is challenging. Simulating client-server communication, ensuring reconnections work as intended, and validating edge cases is a slog. There’s no easy curl command for WebSockets. Port in Use We haven’t even started talking about port conflicts yet... Oh yeah, THAT was fun. Nothing like the good ol’ "Port 3001 in use". Wait, WHAT?! I run lsof -i :3001 to track down the culprit, and it returns... nothing. Absolutely nothing. Thanks, WebSocket! You’re really earning that love-hate badge today. I know WebSockets are powerful, especially for real-time communication like chat apps, live notifications, or... you know... dashboards. But wow, they don’t make it easy to appreciate their elegance during development. For now, I’ll begrudgingly admit that I’m learning a lot. But I’ll also happily admit that I’m counting down the days until this project is done.

Actually, figured it out! I would like to tell you what I did, but I really don't know. I broke my CSRF tokens, then in pure panic fixed it by messing around with the nginx config. But let me show you what is working: The nginx config above (I edited it with the new one) This code here for the Logout: updateUserNavForLoggedInUser(userData) { const navContainer = document.getElementById('elUserNav'); const userPicture = userData.picture ? `<a href="https://discussions.codenamejessica.com/user/${userData.username}" rel="nofollow" class="nodebbUserPhoto nodebbUserPhoto--fluid nodebbUserNav__link" title="Go to ${userData.username}'s profile"> <img src="${userData.picture}" alt="${userData.username}" class="nodebbUserNav__avatar"> </a>` : `<a href="https://discussions.codenamejessica.com/user/${userData.username}" rel="nofollow" data-nodebb-hook="userNoPhotoWithUrl" class="nodebbUserPhoto nodebbUserPhoto--fluid nodebbUserNav__link" title="Go to ${userData.username}'s profile"> <div class="nodeBBNavNoPhotoTile"> ${this.getInitial(userData.username)} </div> </a>`; navContainer.innerHTML = ` <li data-el="profile"> ${userPicture} </li> <li data-el="logout"> <button class="nodebbUserNav__link" id="logoutButton"> <i class="fa-solid fa-right-from-bracket" aria-hidden="true"></i> <span class="nodebbUserNav__text">Log Out</span> </button> </li> `; // Attach the logout functionality to the button document.getElementById('logoutButton').addEventListener('click', this.logoutUser); }, logoutUser() { axios.get('https://discussions.codenamejessica.com/api/config', { withCredentials: true, // Include cookies }) .then(response => { const csrfToken = response.data.csrf_token; // Extract CSRF token return axios.post('https://discussions.codenamejessica.com/logout', {}, { withCredentials: true, // Include cookies headers: { 'x-csrf-token': csrfToken, // Use retrieved CSRF token }, }); }) .then(() => { window.location.href = 'https://codenamejessica.com/'; }) .catch(error => { console.error('Error logging out:', error); alert('Failed to log out. Please try again.'); }); }, Ultimately It took getting the user's x-csrf token, which I acquired by adding the x-csrf items and adding the logout to the api section of the nginx config. Then I was able to acquire the x-csrf from the const csrfToken = response.data.csrf_token;. Sending that in with a post, and redirect back to the website. AGGHHH! That was hard! Don't judge me, I see your eyes giving me those looks.

As another week comes to a close, let's take a moment to celebrate our accomplishments and recharge for the exciting challenges ahead. Whether you're coding a new feature, troubleshooting a tricky bug, or strategizing your next business move, remember this: You are capable of amazing things. The world of development is a dynamic one, filled with constant learning, problem-solving, and innovation. It demands resilience, creativity, and a growth mindset. Embrace the challenges that come your way, for they are opportunities to learn and grow. Remember the passion that ignited your journey. Whether you're driven by the thrill of building something new, the desire to solve real-world problems, or the dream of creating a successful business, hold onto that fire. Let it fuel your perseverance and inspire you to push beyond your limits. The road to success is rarely linear. There will be setbacks, doubts, and moments of frustration. But even in the face of adversity, never lose sight of your goals. Trust in your abilities, learn from your mistakes, and keep moving forward. We are all part of a vibrant and supportive community. Reach out to your fellow developers, share your knowledge, and seek inspiration from others. Collaboration can spark new ideas, accelerate your progress, and remind you that you're not alone on this journey. As you head into the weekend, take time to relax, recharge, and reflect on your achievements. Celebrate the progress you've made, no matter how small. You deserve it. Here's to a weekend filled with joy, inspiration, and well-deserved rest. Have a fantastic Friday and an even better week ahead! Codename: Jessica Linux Enthusiast | Adventurer | Smart Ass My Site | Join the Forum [image: 9wqynsG.png] [image: endpoint?url=https%3A%2F%2Fquotes.codenamejessica.com%2Frandom-quote&cacheSeconds=10&style=for-the-badge]

Currently while looking in the Admin-Appearances-Themes, you will see the Themes that are available, but no version information. Is there a way we can apply the version information under or beside the name so we can determine if we are out of date? Plug-Ins have a nice list, although I have not been able to see anything for the Themes. Codename: Jessica Linux Enthusiast | Adventurer | Smart Ass My Site | Join the Forum [image: 9wqynsG.png] [image: endpoint?url=https%3A%2F%2Fquotes.codenamejessica.com%2Frandom-quote&cacheSeconds=10&style=for-the-badge]

@baris Yeah, I already put something in the issues (Signatures not showing), I also found the problem and posted a fix. It looks like someone took it and added it to the next release. So far, everything looks good. There are some fun things to this theme, and I am excited to pushing the limits. If you are one of the developers, great job on the design. Codename: Jessica Linux Enthusiast | Adventurer | Smart Ass My Site | Join the Forum [image: 9wqynsG.png] [image: json?url=https%3A%2F%2Fquotes.codenamejessica.com%2Frandom-quote&label=Quote&query=$.message&color=$.color&style=flat&cacheSeconds=10]