General Discussion

You can increase the recent topic count in the ACP. Again this won't show all the topics going back to first one but you will see more. [image: 1727269191110-ecf9bc55-9712-41b6-9e1f-2b110de0dd7c-image.png]

@eeeee my mistake, only brand:favicon is used as the favicon. As you assumed, the touch icon is used for mobile devices. We expose it in the page meta tags as an optional icon for mobile devices to use in bookmarks and when added to the home page. The "maskable" icon is meant to be an image that is preferable to be edited computationally. An One example of a maskable icon used would be the icons in your phone's notification bar — they're shrunken down and flattened to black-and-white. Some sites would prefer a different icon (maybe one that is less busy, or fewer colours, etc). For example, on another site I admin, OpenBeta, the icon is white-on-orange. When automatically masked, the icon ends up white on white, which is undesirable, so this site uploaded a black-on-white "maskable icon" that shows up correctly when masked.

@julian Same experience on Edge as with Chrome.

Thank you! I'm super looking forward to figuring this all out!

Figured it out. All good. Thanks for the help. Much appreciated.

You would need to create new routes in your plugin like so helpers.setupPageRoute('/:groupslug/:userslug', middlewares, function (req, res, next) { // todo: get uid of user using req.params.userslug // todo: check if user is member of req.params.groupslug // todo: render account template with all data }); You can take a look at the core user routes on how to do most of this stuff.

Composer plugin doesn't have colors, maybe you had a plugin that added them?

@eeeee using the latest version of both activitypub branch and link-preview, the images seem to be showing up ok. I did find a bug where editing a post caused the pictures to disappear, oops! That's fixed in the latest link-preview plugin version, 2.0.11.

Thank you so much @baris .

It seems Anandtech is closing up shop after 27 years of coverage — simply astounding. One interesting thing they included in their farewell: The AnandTech Forums will also continue to be operated by Future’s community team and our dedicated troop of moderators. With forum threads going back to 1999 (and some active members just as long), the forums have a history almost as long and as storied as AnandTech itself (wounded monitor children, anyone?). So even when AnandTech is no longer publishing articles, we’ll still have a place for everyone to talk about the latest in technology – and have those discussions last longer than 48 hours. Emphasis mine. That single phrase is one of the reasons why we started NodeBB and continue with it today. The social media landscape is rife with hot takes and expressions of opinion that last a mere days before it is pushed aside to make way for new content. It's by design and a part of the reason why the web seems so much shallower now than it did even a decade ago. Admittedly, it's what a lot of people want, and the last thing I want to do is to say that you're "using the web wrong", but there are a significant number of people who want to use the web to have real, genuine, long-term discussions with other human beings, and the best way to do that is with a forum. With ActivityPub integration, we're hoping to extend that olive branch into a fediverse mostly inhabited by a microblogging software. Goodbye Anandtech, you will be missed!

@eeeee yes that makes sense

@eeeee The embedded link via <script> does not work all of the time as it is only set to trigger onLoad whereas the <iframe> solution will work every time because it needs to call the remote source. NodeBB loads all assets onLoad as an SPA (Single Page Application) and will not make any further calls to remote sites unless requested by an ajax request. This is why the <script> embed will always work when you press F5 as the entire site is being loaded, but not when the links are clicked as there is no ajax request.

@eeeee this isn't possible without altering the markdown settings - more specifically, HTML Sanitization. Automatic HTML sanitization is an important part of ensuring that your users do not run arbitrary javascript or alter parts of the page that were not meant to be altered. This used to be the sole line of defense from rogue HTML in user-generated content. However, NodeBB now comes with its own built-in HTML sanitizer so it is safe to disable this one if necessary Enabling this option will expose your forum to risk in the sense that arbitrary code can then be executed which isn't something I'd recommend. Widgets allow this functionality because they do not accept input from users whereas posts obviously do.

Seems like they are all from secondary dependencies. $ npm ls punycode [email protected] D:\github\NodeBB ├─┬ @apidevtools/[email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped ├─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped ├─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped ├─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped ├─┬ [email protected] -> .\..\nodebb-plugin-composer-default │ └─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] ├─┬ [email protected] -> .\..\nodebb-theme-harmony │ └─┬ [email protected] invalid: "^9.0.0" from ../nodebb-theme-harmony │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] ├─┬ [email protected] -> .\..\nodebb-theme-persona │ └─┬ [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] ├─┬ [email protected] invalid: "7.0.19" from the root project -> .\..\nodebb-widget-essentials │ └─┬ [email protected] invalid: "7.32.0" from ../nodebb-widget-essentials/node_modules/eslint-config-nodebb │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] ├─┬ [email protected] │ └── [email protected] └─┬ [email protected] └── [email protected] deduped

Discourse is very bloated, while NodeBB is lighter.

Thanks @baris that has fixed the issue

@josef yes, good point. the eventListener is testing for printscreen button, and the 16 + 91 +83 keycode events to prevent that. However if Sniping tool can be activated another way (without those keypresses) then it wouldnt stop it.

@eeeee the shortened links should work fine as well: https://community.nodebb.org/post/100751 You can enable the YouTube "special embed" from the link preview admin settings page. [image: 1724163719298-bdbc67a8-281d-4e7a-9e9c-93a423ff7069-image.png]

Update: Something showing in World now!

How can I find out who author is, to ask for clearance? Wouldnt it make sense for the default setting to accept it for future versions, otherwise when nodebb advances there will keep being the issue for new installs?