docs: clarify migration instructions

[returnDanilo]

Description

I added some details to the migration page to save people the time I took to learn the nuances about using different types of tokens and scopes.

Checklist

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
  • I have updated the changelog with a quick recap of my changes.
• This PR fixes an issue.
• This PR adds something new (e.g. new method or parameters).
• This PR is a breaking change (e.g. methods or parameters removed/renamed)
• This PR is not a code change (e.g. documentation, README, ...)
• I have read and agree to the Developer Certificate of Origin for this contribution

[tribes2]

edit: This change appeared important to me, but it seems I'm mistaken. You can ignore this post.

_This change is really important and clarifies the significant change in basic behaviour, far better than 'initial_channels removed'.

I've found the migration process confusing because my bot is using outdated token behaviour for a single user scenario (i.e. streamer operates the bot for only two channels). This clarifies how much work is left and means I'll be pinning to the last 2.x release until I have time to upgrade._

[EvieePy]

@tribes2 I'm not sure I understand what you mean. Could please clarify, because whilst migrating docs are still a work in progress there are multiple sections of the page and other parts of the documentation including the FAQ that indicate and explain that IRC functionality was removed and that EventSub is now the standard.

[tribes2]

Yeah. It states that IRC is removed and EventSub is the standard. That doesn't mean anything to me because I'm not paying much attention to Twitch APIs, but this pull request explains the change in methodology in enough detail that I know what to do next. I think it's a good improvement and would aid others in migrating to 3.x.

[chillymosh]

This PR has outdated information, as well as some incorrect details about connectivity and rate limits.

[tribes2]

Alright. Guess it's not worth merging. Sorry for the noise, have a nice day.

[EvieePy]

It's not going to merged no as the information is incorrect and does not explain how to migrate from IRC to EventSub in any greater detail than what is shown via the examples and existing migrating guide.

However I do understand the importance of a section detailing the steps involved with this and appreciate the feedback so I will put this on the board to do.

Unfortunately migrating guide has taken much longer than initially expected to complete as there's only 1 person writing it (myself).

[returnDanilo]

It's not going to merged no

no worries.

would @EvieePy and @chillymosh please clarify what is wrong with the claims in the PR? thank you!

[EvieePy]

Hey @returnDanilo the migrating guide will require a whole section dedicated to explaining how to migrate from IRC to EventSub.

Also this PR includes information on how to bypass the core libraries design to send messages to chat. While I appreciate that it may be an option for some people to explore the advice doesn't belong in the library as the library itself does not support this mode of operation. The reason we shifted towards these choices was to avoid staying on outdated APIs that Twitch themselves encourage people move away from.

All that being said there's nothing stopping anyone from exploring old/restricted APIs or even implementing IRC on TwitchIO 3 as an extension, it's just not available in the library as core functionality.