reinacchi / nreader Goto Github PK

It seems that this is an issue from the API, nothing that I can do to fix this.

I've been thinking to create a custom framework built specifically mainly for Reader. The framework will include mostly the API (as for now) then followed by the remaining custom built-in classes found inside the Extensions. In other words, every extended class will be removed and moved to this new framework instead.

Some classes may remain inside the folder such as ButtonNavigator and Util.

A PR will be made related to this topic.

I'm a bit surprised that no one has ever mentioned this issue within the bot. Apparently, #126 doesn't work as intended and I may have missed several testing before merging which leads the bot into a major issue.

Any active interactionCreate events will respond to any interaction with a message saying that This button is not for you! and the console will log multiple errors.

As of now, the original bot had the update reverted in the meantime while this issue is being investigated.

I think it's best to not keep any commands error visibility to the user itself (interactions being ephemeral)

Another reason, is that interaction defer comes with no flag thus, having interaction being ephemeral is useless.

• This depends on #55

I'm leaving this to track things down

• Join the Discord Server for some references.

The official NReader Discord bot runs locally on my machine. Thus, this explains why most features are incomplete or potentially broken. As for now, the API still had a Cloudflare Ban enabled on their endpoints which is problematic to troubleshoot in a VPS. This will get a fix as soon as I could find a solution to this however, it might take a long time.

Another thing that's important on the other hand, is features implementation. I've had several changes in mind that I might put an effort into.

Bypassing Restricted Tags

Currently, using the /read or /search commands with restricted tags included in the search is prohibited for regular servers. This can be bypassed if your server is marked as whitelisted by a Server Nominators. This behaviour will change entirely at least by the end of the year.

As of 2023, I'll be launching a Premium system for users, a paid service for users to access more locked features. Features such as bypassing restricted tags will be included in this premium service and there'll be changes in whitelisting servers where it'll be eligible to specific servers instead.

Unlimited Bookmarks

The current maximum bookmarks can hold up to 25 items. The new premium service will allow more than 25.

• I may have to reconsider this due to API rate limits.

More

Probably more, too.

There seems to be an issue where at some point the API will return an HTTP error. This is due to no prevention code being implemented and might be a connection error.

TL;DR: No possible fixes at the moment

Slash commands are registered automatically by the bot per guild. However, this system might be broken due to API rate limits. I don't know why I haven't thought about using global slash commands.

Switching entirely to global slash commands might be difficult as I need to delete all slash commands in each guild which then requires extended maintenance. Another thing which makes me not a fan of global slash command because editing its body structure could take some time before all guilds are updated. There's also some negativity about using global slash commands but I rather keep it to myself.

• I'll reconsider about this

I'm aware that some languages (currently the Chinese language) have their date localised wrong or are still in English format. I won't be fixing this until localisations are being used around mostly and several users report.

Thanks to Cloudflare being added to the API, it's almost impossible to fetch data. Though in some cases, the bot will somehow attempt to fetch the data for a while before Cloudfare decided to do something quirky about it.

Unfortunately no possible fixes from our side. They'll have to manage this.