Should be /usr/src/app

You can simply use the custom CSS tab in the acp and use a different css. [component="brand/logo"] { max-height: 64px; width: auto; } Don't forget to enable custom css switch if you haven't already on the same page.

Hi! I don't have time to look into this at least for the next three days.

@jwildeboer@social.wildeboer.net Right, there's a possible social engineering vector at play here, which I think makes this a little concerning. I certainly don't like my time wasted either cc @thisismissem@hachyderm.io @mariusor@metalhead.club

@osma@mas.to the default assumption is that announces are delivered back to the origin server in order to close the loop. However it is not a requirement. For example I am considering not doing so for group announces.

@julian src/slugify.js requires public/src/modules/slugify, so I changes the slugify function in that file to return function slugify(str, preserveCase) { if (!str) { return ''; } str = String(str).replace(trimRegex, ''); if (isLatin.test(str)) { str = str.replace(invalidLatinChars, '_'); } else { str = XRegExp.replace(str, invalidUnicodeChars, '_'); } str = !preserveCase ? str.toLocaleLowerCase() : str; str = str.replace(collapseWhitespace, '_'); str = str.replace(collapseDash, '_'); str = str.replace(trimTrailingDash, ''); str = str.replace(trimLeadingDash, ''); return str; }; , basically replaced the dashes with underscore. I then stopped my current instance, upgraded it and then started it. However, now I registered a user using the google-sso plugin and again it has a dash in username instead of underscore. I guess we need to log the username somewhere in the plugin/core nodebb to find the problem. Which would be the best place for doing so?

@Kichae thanks! Looks like an issue to look into. https://github.com/NodeBB/NodeBB/issues/13201

@kirk@social.coop just wanted to drop a note that your two issues have not been forgotten