Hi tubugato223,
The first login dialog is triggered by the extension itself. The second one, however, is not.
The second dialog is displayed by the browser when the extension initiates a feed request, and the browser determines that an authentication is required. To minimize interruptions, the browser may eventually stop showing this dialog.
If the user still wants to access the feed manually, they can do so by selecting the “Sign in…” option from the feed’s context menu.
I hope this is clear.