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.
An API (Application Programming Interface) is a tool which allows developers to create their own third party software that interacts with an application. In NoBleme's case, it means that you can use its API to build custom applications which interact with the website.
If you did not already know what an API is, then this part of the website is most likely not for you. It will only be of interest for people who have programming skills and want to create third party tools for NoBleme.
Every route in NoBleme's API must be queried using an URL beginning with https://nobleme.com/api/
NoBleme's API provides access to a limited number of website features. The complete documentation of all existing routes and their behaviors can be found through the dropdown menu at the top of the page.
Currently, the API is read-only, meaning that you can use it to fetch data from NoBleme, but not to interact with the website. This could change in the future.
Using the API currently does not require authentication. There are no access restrictions and no rate limiting. This could change in the future.
The API is not versioned. This means if a breaking change happens, the previous way of interacting with the API will disappear, and you will need to update your applications accordingly. Although the API is designed so that breaking changes should ideally never need to happen, advance warnings will be given before any future API breaking changes on the devblog and/or IRC and/or Discord.