Error fetching threads: Only bots can use this endpoint about discord.js-selfbot-v13 HOT 7 CLOSED

Is that a yes 😆 I don't want to submit a PR if you're already working on something.

I'm working on interactions at the moment, so you can submit a PR .-.

from discord.js-selfbot-v13.

Update: It's actually more complex for guilds! For guilds users receive the threads via the GUILD_CREATE event you receive upon startup, probably because users always cache channels and guilds unlike bots which can be picky about what they cache. I'll probably create a new object on the guild class which gets populated on startup and also is modified through events such as thread create/thread delete etc.

For channels it's really simple, there's an API call for it.

Not a massive problem but it does add more complexity when keeping the project up-to-date with the discord.js branch, especially when you still want to maintain support for bots where you need to add extra checks.

from discord.js-selfbot-v13.

Issue description

It seems that ThreadManager.fetchActive is a bot-only endpoint. The Discord client uses the search API endpoint for the threads dropdown. This may also apply to fetchArchived.

      throw new DiscordAPIError(data, res.status, request);
            ^

DiscordAPIError: Only bots can use this endpoint
    at RequestHandler.execute ([redacted]/node_modules/discord.js-selfbot-v13/src/rest/RequestHandler.js:350:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async RequestHandler.push ([redacted]/node_modules/discord.js-selfbot-v13/src/rest/RequestHandler.js:51:14)
    at async ThreadManager.fetchActive ([redacted]/node_modules/discord.js-selfbot-v13/src/managers/ThreadManager.js:234:17) {
  method: 'get',
  path: '/guilds/[redacted]/threads/active',
  code: 20002,
  httpStatus: 403,
  requestData: { json: undefined, files: [] }
}

Code sample

// Fails with "DiscordAPIError: Only bots can use this endpoint"
const activeThreads = await channel.threads.fetchActive();

Package version

2.0.4

Node.js version

18

Operating system

No response

Priority this issue should have

Medium (should be fixed soon)

Checklist

• I have searched the open issues for duplicates.
• I have shared the entire traceback.
• I am using a user token (and it isn't visible in the code).

Additional Information

No response

I will block this endpoint, thank you for informing me
I will find another endpoint with similar functionality

from discord.js-selfbot-v13.

It appears users use a special endpoint for this: https://discord.com/api/v9/channels/*************/threads/search?archived=true&sort_by=last_message_time&sort_order=desc&limit=25&offset=0 (grabbed this from network logs) so you can probably set the archived to false to get active threads. I can submit a PR if @aiko-chan-ai is happy for me to do so.

from discord.js-selfbot-v13.

It appears users use a special endpoint for this: https://discord.com/api/v9/channels/*************/threads/search?archived=true&sort_by=last_message_time&sort_order=desc&limit=25&offset=0 (grabbed this from network logs) so you can probably set the archived to false to get active threads. I can submit a PR if @aiko-chan-ai is happy for me to do so.

ty <3

from discord.js-selfbot-v13.

It appears users use a special endpoint for this: https://discord.com/api/v9/channels/*************/threads/search?archived=true&sort_by=last_message_time&sort_order=desc&limit=25&offset=0 (grabbed this from network logs) so you can probably set the archived to false to get active threads. I can submit a PR if @aiko-chan-ai is happy for me to do so.

ty <3

Is that a yes 😆 I don't want to submit a PR if you're already working on something.

from discord.js-selfbot-v13.

Update: It's actually more complex for guilds! For guilds users receive the threads via the GUILD_CREATE event you receive upon startup, probably because users always cache channels and guilds unlike bots which can be picky about what they cache. I'll probably create a new object on the guild class which gets populated on startup and also is modified through events such as thread create/thread delete etc.

For channels it's really simple, there's an API call for it.

Not a massive problem but it does add more complexity when keeping the project up-to-date with the discord.js branch, especially when you still want to maintain support for bots where you need to add extra checks.

(I have no idea where I got guilds from when the issue stems from fetching channel threads but this could be a future thing!)

from discord.js-selfbot-v13.