johnefrancis@cosocial.ca eh, keep the floppy disk as far as I'm concerned. The replacement (the hard drive with a down arrow) is even stupider. 'sides... we still use the telephone handset to represent calling people. I guess I'm old, Gen Z doesn't call people either

squinky@teh.entar.net of course, please keep me in the loop. It sounds like something that could be controversial but have interesting implications for Trust and Safety (cc thisismissem@hachyderm.io)

reiver@mastodon.social what a good lookin' group of people!

lepertti@mastodon.gamedev.place yes! That's what I did with NodeBB. The main things you need for that are the content discovery pieces, otherwise you're broadcasting only.

rimu@piefed.social I love it! box464@mastodon.social

jupiter_rowland@hub.netzgemeinde.eu Mastodon shows the title, summary, and adds a link. It's as good as it'll get and quite a ways from where it used to be.

ariadne@social.treehouse.systems where's the forum option

Hi julian, thank you for your previous reply, and sorry for the late response. I was able to resolve the CORS issue using Nginx. Now, I’m working on integrating the NodeBB Write API with my React.js frontend. For authentication, I’m using Keycloak for login and registration. I have a question regarding the express.sid cookie: After login, the express.sid is generated and stored in the cookies. I tried using this session ID to fetch the CSRF token by calling /api/config, but it doesn’t seem to work for me. My goal is: Successfully retrieve a valid CSRF token. Use it to create topics or posts via the Write API. Ensure that once I have this token and session, I can access all the required NodeBB APIs. Could you please clarify the correct approach to: Retrieve and use the CSRF token with the express.sid? Authenticate API requests (like creating topics or posts) when using Keycloak for login instead of NodeBB’s built-in login? Any guidance or best practices for this integration would be greatly appreciated. Thanks in advance!