@Sampo2910 you can preview the actual site here
And this from NodeBB themselves
Bringing Back Better Bootswatch! - nodebb
A change in NodeBB's integration of Bootswatch themes is outlined. This change is scheduled to land in v3 of NodeBB.
As I mentioned above, it’s a replica of bootswatch, and not a new selection of swatches.
@Sampo2910 you should also have a look at the new ones I added today - Twitter, and Anthracite. I’m currently using the latter and love it.
@Sampo2910 have you seen the article they recently released about supporting bootstrap 5 in v3 of NodeBB? This means that they will actively add functional support for bootswatch themes.
Whilst this is a welcome advance, several of these themes look quite ghoulish in my view, and lack creativity - essentially, they are simply recycling existing effort, and not bringing anything new to the table. I understand the approach in the sense that these are ready made and work very well, and why reinvent the wheel, but what would add much more value in my view is a fully skinnable interface where you could keep various iterations of color schemes that you liked.
It’s why I created the swatch engine in the first place.
Those of you who keep up with tech news will no doubt already be aware of the decision to standardise charging devices using USB-C.
Sky News published the article below
Phone chargers to be standardised across Europe from 2024 - forcing Apple to change to USB-C
Apple has previously opposed the move, saying it would stifle innovation and create waste.
One of the huge benefits in my view is the enormous dent this will place into the Apple ecosystem in the sense that they will be forced to comply with this new standard. My experience of Apple has been that each time a new iPhone is released, a new charger type is required meaning you cannot simply reuse the charger you had previously.
Not only does this force the owner to purchase new hardware, but also contributes heavily to landfill thanks largely to unwanted power adapters that no longer have a purpose. Moving towards a centralised standard creates a wider scope of innovation in my view as charging techniques have dramatically improved over time.
It also puts a stop to Apple cornering their user base every time a new model is released. In my view, that alone is a huge positive.
Hi All,
As you know, we now have 10 swatches featuring various colour schematics. I thought it would be useful to run a poll to garner some stats around who is using what.
In addition, I’m interested to gain some insights into why you are using this particular Swatch.
Many thanks for your input.
*** NEW *** Anthracite theme added
For those who like a bit of darkness in their lives, but not too much of it 
*** NEW *** Twitter (Dim) theme added
For those who like the Twitteresque dim theme.
@DownPW just circling back to this, as I did eventually find the class. Seems you can disable the outline using the below CSS
textarea {
outline: none;
}
On this site, I’ve added an animation (essentially, a link underline) that meant I needed to modify the Fancybox function. The new animation I mentioned above has an annoying artefact where it also applies on images where the fancybox class exists.
This is not surprising, as the fancybox attribute adds a a href to all img tags. Based on this, it is necessary to add a noanimate class so that the link animation is not being applied. However, this isn’t such a simple affair. Due to the Lazy Load feature that NodeBB leverages, the images aren’t in the DOM until that specific chunk of data is loaded as the user scrolls through the post. To allow for this, we need to fire an event that selects each target image extension and then appends the existing classes with noanimate as desired. For this to work, we have to create a duplicate each function that uses the preexisting hook of action: posts.loaded.
In usual cases of an entire page load, this could be quite greedy and have a significant impact on CPU cycles. Thankfully, the cost is in fact negated by the limited amount of data being pulled in each Ajax request using the post loaded feature.
Below is the code I developed for that
if (top.location.pathname !== '/login') {
$(window).on('action:posts.loaded', function(data) {
console.log("Loaded");
$(document).ready(function() {
$('a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() {
$('a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"]').addClass("noanimate");
});
});
});
}
if (top.location.pathname !== '/login') {
$(document).ready(function() {
$(window).on('action:ajaxify.end', function(data) {
this.$('a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() {
$('a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"]').addClass("noanimate");
data.preventDefault()
// Strip out the images contained inside blockquotes as this looks nasty :)
$('blockquote img').remove();
});
Fancybox.bind(
'a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"]', {
groupAll: true,
}
);
});
});
}
The specific CSS that defines the animated underline (which you can see for example by hovering over the usernames in each thread) is shown below - note how we exempt noanimate using the :not() class. Basically, apply this css to all a href except those that carry the appended class noanimate.
It’s a bit of a bulldozer to break an egg, but it’s still efficient nonetheless.
.content p a {
position:relative;
}
.content p a:not(.noanimate):after {
background: none repeat scroll 0 0 transparent;
bottom: 0;
content: "";
display: block;
height: 1px;
left: 0%;
position: absolute;
background: var(--link);
transition: width 0.3s ease 0s, left 0.3s ease 0s;
width: 0;
}
.content p a:hover:after {
width: 100%;
left: 0;
}
You’ve probably heard in the news that Twitter is evidently trialing a “feature” that enables you to edit tweets. See below
Twitter rolling out edit feature to some users in Canada, Australia and New Zealand
The roll-out of the edit feature is currently limited to people who pay monthly for the premium Twitter Blue service.
For me at least, this has been met with a degree of trepidation - ok, even sarcasm if I’m honest. If you read the article, you’ll notice that this is being targeted at those who actually pay for Twitter’s services - their Premium Blue Services to be precise.
Even Facebook, with it’s multitude of well documented privacy issues over the years offers you this for free - and also the ability to delete a post you’ve created. Whilst Facebook is far from perfect, they’ve at least given you this functionality for free, yet Twitter have the audacity to charge for even the most basic of features. Whilst I fully understand that some services, particularly those that extend the platform’s existing functions with a set of features that enhance the overall capability need to be offered as a paid service to provide the firm with a revenue stream, that (in my view) doesn’t extend to a feature that should be part of the core product suite, and should be free.
As an analogy, can you imagine buying a car only to find out that the wipers are a “premium” addition? If you’re like me, and produce plenty of typos in text you type - and let’s be honest - with a significant portion of devices connected to the internet being mobile, this is an ongoing trend that shows no sign of showing down, yet alone stopping altogether.
In this instance, you have to delete an entire tweet just to rectify poor grammar or spelling mistakes which by today’s standards is almost prehistoric. Admittedly, every platform, including this one, will retain the original post along with the edits you made. The difference here is that you have access to the edits, and can remove them completely if you so desire.
Seeing as it took Twitter years to go from 140 to 280 characters per message (and for the purists out there, I’m well aware of Twitter’s origins and it’s emergence as a micro blogging platform), I’m not expecting Twitter to make this edit “feature” mainstream meaning that every year can benefit from it as part of the core functionality.
My personal view is that it’s not right or acceptable to make users pay for basic functionality - and the ability to edit a post is paramount in my view. Let’s say that you’ve worded something in a way that could be misinterpreted, or misconstrued. After reading your post, you have a chance to rectify that and this is a feature I see being used on a daily basis here.
It’s no wonder that various tweets on Twitter often cause a backlash, and a wave of negative comments. The only saving grace is the ability to delete a tweet, but in terms of damage control it may be too late already.
I guess there’s always the argument that you should think before you post, but sadly, that doesn’t seem to be adhered to in several cases I’ve seen.
I’m interested in your views around this topic. Self moderation should be encouraged at all times, and it’s not something I’d expect to have to pay for either.