Community

pls upgrade your npm if others are okey

@crazycells seems Tenor gif started sending back larger gifs which caused the camo proxy to fail (the default max size is 5mb. I upped it to 10mb now).

Stop linking to huge GIFs people 😆

Kramer Seinfeld GIF

@julian Thanks for the heads up.

@pramariena What would you like to know? What they've shared is what's in the blog post, but I am happy to answer questions.

@omega I missed your questions, but it's a quick one. The whole moz project took only a couple months, and most of that was building out their custom theme and some custom functionality. Getting their forum imported into NodeBB was straightforward when using nodebb-plugin-import. We worked with @bentael for that one.

One tricky bit was getting their URL redirections working. Their topic slugs were not easy to parse since they were at the root level (e.g. /community/q/this-is-the-topic-slug). This meant we had to create a redirect map for every one of their existing topics, and ensure they correctly routed to the new topic ID.

great job 🙂

What is this?

Version 2 of NodeBB using the Persona theme (and many child themes based off of Persona) used Bootstrap 3 as its front-end CSS framework.

As part of the upgrade to version 3, we are upgrading to Bootstrap 5, whose migration comes with a number of updates and changes, many of which are incompatible with previous versions of Bootstrap. […]

Click here to see the full blog post

@gotwf The themes are from Bootswatch, so I suspect you should contact them with suggestions 🙂

You might already be aware that we’re in the midst of the design phase of a new base theme for NodeBB. What you might not know is that we already have some interim design previews for you to look at! Check out Vlad’s work on our theme here We’ve been working closely with Vlad for […]

Click here to see the full blog post

@julian

All my theme with persona is just CSS.
if I update to V3, I recreate all my themes but it's a lot of work 😉

Ah, the dark art of release engineering...

Good to know. Rock on! 🎸

@julian said in Optimizing Benchpress:

Are you saying we should build RustBB?

Looks like lemmy developers are trying to do it based on their platform 🙄 🙄
https://github.com/Nutomic/lemmyBB

@julian

v3 (SASS, front-end framework decoupling)... @baris

💡 👍

So when's V3 coming round the mountain? 😉 😁

Sounds just dandy to me. Future's looking rosy for NodeBB. 👍

Rock on! 🐕

Imagine, you walk into library, you hardly have both feet in the door when all of a sudden twenty people run at you holding books aloft crying, “we thought you’d like to read this!”

Terrible bums rush and puts the book angel out of a job.

Caveat: Extroverts might enjoy the attention 🤠

Nice!

A few things:

I, too, have long favored Brother printers. Excellent bang for the buck. 💵 Suggest you never lay a flat screen flat on its back. Better to keep stresses in the vertical plane so stand on edge leaning up against a wall somewhere out of the way. Plus, you just know that somewhere there is someone wanting to trip over their shoe laces and.... I, too, favor quality over cheap. Nice Lenovo gear. 👍

Rock on NodeBB! 🎸 🐕

@gotwf In vino veritas

Pumping the collective psyche with the truth wrapped in tuneful gaiety... 👉 Precession Of The Ages 👈

♒

In advance of the release of v2, we are releasing this migration guide in order to give third-party developers a chance to bring their plugins and themes up-to-date. In the successive sections below, we will outline the breaking change or new best-practice, and the steps to migrate, along with a live example.

Click here to see the full blog post

I think @volanar loved the addition so much, so he upvoted 😄

if he downvotes, it should be -5

@julian One may hope not. Leastwise.... what is special about those dates? I know not. Mayhaps were you referencing the 2038 Unix Epochalypse? I think this has potential to be far more problematic. I have been aware of this since the great Y2K "crisis" but kind of forgot about it until this thread since 2038 was a "long ways off yet". I also thought this would be no big deal in future modern times due to the prevalence of 64 bit processors and os platforms. Alas, I seem to be in error:

There is no universal solution for the Year 2038 problem. For example, in the C language, any change to the definition of the time_t data type would result in code-compatibility problems in any application in which date and time representations are dependent on the nature of the signed 32-bit time_t integer. For example, changing time_t to an unsigned 32-bit integer, which would extend the range to 2106 (specifically, 06:28:15 UTC on Sunday, 7 February 2106), would adversely affect programs that store, retrieve, or manipulate dates prior to 1970, as such dates are represented by negative numbers. Increasing the size of the time_t type to 64 bits in an existing system would cause incompatible changes to the layout of structures and the binary interface of functions. [emphasis added]

Could be in for some interesting times, eh? 😜

Truth be told our latest release was published late last week in advance of “snowmageddon” burying much of the U.S. northeast and Canadian southeast. But everyone is well and we’ve mostly managed to dig our way out of our various home offices across the Greater Toronto Area. Hope you are keeping safe and warm, wherever […]

Click here to see the full blog post