×

Lost account access

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.

NOBLEME
PAGES
SOCIAL
L
FR
 
 
 

Login

Devblog

Public API

Published Sunday, March 19th 2023 (351 days ago)
18th birthday

As NoBleme was initially launched on march 19th, 2005, today marks NoBleme's 18th birthday.

It's been a long journey, and I would like to thank everyone who's been a part of it. We might not be a big community or an important part of the Internet, but we are a place where friendships developed and users grew up together into better people, and that's actually pretty cool.

Here's to many more years.

Public API

As of version 4.5.x, NoBleme now has a public API.

For non technically inclined people, this is a tool which allows you to fetch most of the website's publicly available data without using a browser. It can be used to create third party applications which use data from NoBleme, for example an IRC bot used to fetch quotes on demand, or an external calendar for meetups.

For technically inclined people, the documentation is short but exhaustive, just give it a quick read. It's all standard REST stuff. As of right now, the API is public and readonly: no token or authentication is required to use the API, you can fetch public data, but can not fetch any data that requires logging into an account, and you can not interact with any existing data (no updating or deleting).

There are currently no plans to have a private API, but plans can always change in the future.

State of things

While we're here, let me share a few interesting (?) numbers with you.

After a year of low frequency but regular updates, the 21st century compendium's growth is accelerating. It has reached 50 000 visits and is now the top result for most search engine queries related to pipi in your pampers. Not by choice, mind you, but I'll take what I can get.

6.2% of guests who stay on the website for more than a couple pages switch to light mode. I do have plans to make NoBleme adapt to your system's or browser's preferences between light/dark mode, but I will first wait for better support for all components of the prefers-color-scheme CSS media feature.

16.7% of guests use the website in french, which is an interesting change since NoBleme used to have a majority of french visitors until more or less 2020. Whatever changed, we are now getting a large majority of non-french speaking guests. Seems like making NoBleme bilingual was a good move.

According to Google's insights, the mobile experience on NoBleme before/after last year's redesign went from 8.4% of pages giving a good mobile experience to 66.7% of pages giving a good mobile experience. I would certainly call this progress, although it shows there's still more work left to do.

A grand total of zero pages on NoBleme have loaded in more than 100ms since the start of the year. Thanks to server performance improvements and a lot of work on improving code quality last year, I've finally reached my goal of guaranteeing a good experience on the website even for users with slower Internet speeds. Most likely nobody will notice or care, but I'm quite happy about it.

What's next?

Preliminary improvements to the codebase were required before I could work on more interesting updates to NoBleme. The public API was the biggest hurdle, and it's now finished and published.

I still need to finish a few other technical tasks first (those are minor and thus won't be discussed in a devblog), but actual new content is in the works. It's been a while since NoBleme's had anything properly new, let's hope you'll enjoy my upcoming surprises.

Previous devblog:
Code quality improvements