As a part of its privacy policy, NoBleme will protect your anonymity as much as possible. This means that you will never be sent any emails that could be used to link you to your identity on the website, or asking you to provide your password. On top of that, automated password recovery systems can be used in a few nefarious ways that we would rather not have to deal with. With this context in mind, NoBleme decided to not implement an automated account recovery process.
If you have lost access to your account (forgotten username, forgotten password, or otherwise), the only way to recover that access is to go on NoBleme's NoBleme's IRC chat server and ask for a website administrator to manually reset your account's password. No need to worry about identity usurpation, there is a strict process in place that will allow the administrator to verify your identity before doing the resetting.
A new major version of NoBleme has been released, focused on code quality improvements.
That's right, code quality.
For the technically inclined curious minds, this overhaul of the codebase involved:
It might seem like an underwhelming update since nothing new has been added to the website, but there are a few legitimate reasons to spend a whole month on code quality improvements.
NoBleme's source code is now a bit easier to read.
As stated behind the scenes, NoBleme's source code should be as readable and accessible as possible.
The real reason though is to make it quicker to find and fix any future bugs.
PHP has been making some progress towards having stronger typing (kinda) in its recent versions. NoBleme's source code now makes full use of it.
For those who aren't into coding, this means that less security issues have to be taken into account when developing the codebase and testing for weaknesses. The programming language used by NoBleme could sometimes fail to notice the difference between the number 1000 and the phrase "1000 bananas in a tree", now it can. This seems like a small detail, but it's actually a much bigger improvement than you'd think.
Since dropping NoBleme's latest major rework a year ago, I've had plenty of time to measure the performance of its various scripts and pages.
This code quality improvement session was an opportunity to fix the performance issues I noticed.
Code tends to become obsolete after a short while, usually between 2 to 4 years, for a variety of reasons including but not limited to becoming better at coding and evolutions in the programming languages used.
This leads to situations where maintaining a codebase over a very long period of time tends to mean rewriting the whole thing from scratch in cycles of 5 years or so (as older NoBleme users know way too well).
The only way to avoid this endless cycle of rewrites is to constantly improve the code's quality before it can feel obsolete. This is why this update happened, and why more similar updates might happen in the future.
There are future plans for more interesting updates to NoBleme, but some preliminary improvements to the codebase were required before I could start working on them.
The next major version might also feel like a letdown (fair warning), but after that we'll get into the better stuff.