Discord (And Soon™ Fluxer) supports recieving 'feeds' from other servers, via 'subscribing' to an announcement channel, posting published messages to that channel in whatever channel(s) users choose when subscribing. These are really just fancy webhooks.
Currently, Bifröst doesn't bridge these webhooked messages when they are posted. (For example, PCMR's discord has an announcement channel that they publish whenever the major PC marketplaces offer a game for free, many users subscribe to this channel, and have a 'free games' channel in their discord which recieves these posts - Bifröst doesn't actually relay these messages if you link the channel where those subscribed messages are sent, to a channel in fluxer)
These webhooked responses are different than normal messages, and we also have to ensure we don't trigger some sort of loop with the bot's messages (also webhooks, of course) aren't endlessly looped.
Discord (And Soon™ Fluxer) supports recieving 'feeds' from other servers, via 'subscribing' to an announcement channel, posting published messages to that channel in whatever channel(s) users choose when subscribing. These are really just fancy webhooks.
Currently, Bifröst doesn't bridge these webhooked messages when they are posted. (For example, PCMR's discord has an announcement channel that they publish whenever the major PC marketplaces offer a game for free, many users subscribe to this channel, and have a 'free games' channel in their discord which recieves these posts - Bifröst doesn't actually relay these messages if you link the channel where those subscribed messages are sent, to a channel in fluxer)
These webhooked responses are different than normal messages, and we also have to ensure we don't trigger some sort of loop with the bot's messages (also webhooks, of course) aren't endlessly looped.