Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Handler\GuzzleV6\GuzzleHandler::__construct(): Implicitly marking parameter $client as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Handler/GuzzleV6/GuzzleHandler.php on line 23

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\S3Client::getHeadObjectMiddleware():466}:467}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/S3Client.php on line 467

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\S3Client::getDisableExpressSessionAuthMiddleware():541}:542}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/S3Client.php on line 542

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\HandlerList::__construct(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/HandlerList.php on line 53

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\HandlerList::interpose(): Implicitly marking parameter $fn as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/HandlerList.php on line 249

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ApiProvider::__construct(): Implicitly marking parameter $manifest as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ApiProvider.php on line 186

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\Service::createErrorParser(): Implicitly marking parameter $api as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/Service.php on line 81

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\Parser\RestXmlParser::__construct(): Implicitly marking parameter $parser as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/Parser/RestXmlParser.php on line 19

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ErrorParser\XmlErrorParser::__construct(): Implicitly marking parameter $api as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ErrorParser/XmlErrorParser.php on line 18

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ErrorParser\XmlErrorParser::__construct(): Implicitly marking parameter $parser as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ErrorParser/XmlErrorParser.php on line 18

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ErrorParser\XmlErrorParser::__invoke(): Implicitly marking parameter $command as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ErrorParser/XmlErrorParser.php on line 23

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ErrorParser\AbstractErrorParser::__construct(): Implicitly marking parameter $api as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ErrorParser/AbstractErrorParser.php on line 22

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\ErrorParser\AbstractErrorParser::populateShape(): Implicitly marking parameter $command as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/ErrorParser/AbstractErrorParser.php on line 37

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\Parser\ValidateResponseChecksumResultMutator::__invoke(): Implicitly marking parameter $command as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/Parser/ValidateResponseChecksumResultMutator.php on line 35

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\Parser\ValidateResponseChecksumResultMutator::__invoke(): Implicitly marking parameter $response as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/Parser/ValidateResponseChecksumResultMutator.php on line 35

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\AstRuntime::__construct(): Implicitly marking parameter $parser as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/AstRuntime.php on line 14

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\AstRuntime::__construct(): Implicitly marking parameter $fnDispatcher as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/AstRuntime.php on line 14

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\TreeInterpreter::__construct(): Implicitly marking parameter $fnDispatcher as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/TreeInterpreter.php on line 17

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::__construct(): Implicitly marking parameter $lexer as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/Parser.php on line 38

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::parseWildcardObject(): Implicitly marking parameter $left as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/Parser.php on line 258

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::parseWildcardArray(): Implicitly marking parameter $left as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/Parser.php on line 263

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::next(): Implicitly marking parameter $match as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/JmesPath/Parser.php on line 322

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\Serializer\RestXmlSerializer::__construct(): Implicitly marking parameter $xmlBody as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/Serializer/RestXmlSerializer.php on line 19

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::sourceFile():31}:32}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 32

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::validation(): Implicitly marking parameter $validator as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 50

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::validation():53}:54}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 54

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::tap():128}:129}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 129

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::retry(): Implicitly marking parameter $decider as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 152

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::retry(): Implicitly marking parameter $delay as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 152

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::contentType():189}:190}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 190

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::history():239}:240}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 240

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::mapRequest():263}:264}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 264

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::mapCommand():280}:281}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 281

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::mapResult():296}:297}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 297

Deprecated: {closure:{closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\Middleware::timer():304}:305}(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Middleware.php on line 305

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Auth\AuthSchemeResolver::__construct(): Implicitly marking parameter $tokenProvider as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Auth/AuthSchemeResolver.php on line 28

Deprecated: {closure:DeliciousBrains\WP_Offload_Media\Aws3\Aws\RetryMiddleware::createDefaultDecider():69}(): Implicitly marking parameter $result as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/RetryMiddleware.php on line 69

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\RetryMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/RetryMiddleware.php on line 154

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Api\Validator::__construct(): Implicitly marking parameter $constraints as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/Api/Validator.php on line 21

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\IdempotencyTokenMiddleware::wrap(): Implicitly marking parameter $bytesGenerator as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/IdempotencyTokenMiddleware.php on line 37

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\IdempotencyTokenMiddleware::__construct(): Implicitly marking parameter $bytesGenerator as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/IdempotencyTokenMiddleware.php on line 43

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\IdempotencyTokenMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/IdempotencyTokenMiddleware.php on line 49

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\EndpointV2\EndpointV2Middleware::__construct(): Implicitly marking parameter $credentialProvider as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/EndpointV2/EndpointV2Middleware.php on line 56

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\SSECMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/SSECMiddleware.php on line 33

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\ExpiresParsingMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/ExpiresParsingMiddleware.php on line 36

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\PutObjectUrlMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/PutObjectUrlMiddleware.php on line 35

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\PermanentRedirectMiddleware::__invoke(): Implicitly marking parameter $request as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/PermanentRedirectMiddleware.php on line 37

Deprecated: DeliciousBrains\WP_Offload_Media\Providers\Storage\Streams\AWS_S3_Stream_Wrapper::register(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/classes/providers/storage/streams/aws-s3-stream-wrapper.php on line 21

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\StreamWrapper::register(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /app/wp-content/plugins/amazon-s3-and-cloudfront/vendor/Aws3/Aws/S3/StreamWrapper.php on line 97

What Are Facebook Broadcast Channels and Why Should You Care?

Meta CEO Mark Zuckerberg has revealed a Broadcast Channels feature is coming to Facebook, but should you actually care?

Mark Zuckerberg has revealed via Facebook that the world’s most popular social media platform will be getting a broadcast channel feature similar to the one rolled out earlier in the year for two of Meta’s other apps, WhatsApp and Instagram.

The tech giant launched a public one-to-many messaging feature as WhatsApp Channels earlier this year, alongside something similar for Instagram. Now it’s coming to Facebook and is being described by the company as a tool for creators and public figures to more deeply engage with their followers.

Anyone on Facebook will be able to join these broadcast channels as a way of keeping up-to-date with the content from their favorite Pages and dive deeper into the topics that matter most to them. Facebook’s partner messaging app, now simply called Messenger, will also be getting the feature.

How Will Facebook Broadcast Channels Work?

Meta reveals more in a Facebook blog post announcing the new feature. Going forward, anyone with admin access to an official Facebook Page belonging to a brand or celebrity will be able to start a broadcast channel directly from the Page they manage.

Admins can invite users to join the broadcast channel, creating what has been described as a “giant group chat” where they are able to publish content to this channel for all of those who choose to see it and engage with.

Channel members receive notifications whenever the creator drops new content. They cannot post in the channel themselves, but can react to posts published by the admin.

 

About Tech.co Video Thumbnail Showing Lead Writer Conor Cawley Smiling Next to Tech.co LogoThis just in! View
the top business tech deals for 2025 👨‍💻
See the list button

Facebook Businesses Most Obviously Benefit

Listing its core benefits, Meta describes the tool as a “direct communication line with your biggest fans and a lightweight way to keep followers in the know.” Zuckerberg’s post adds that pages will be able to share voice notes, text, photos/videos, and GIFs with anyone who joins their channels.

Polls will also be an important feature for brands to utilize in order to get instant feedback from their community. As well as following in the footsteps of WhatsApp and Instagram channels, the new Facebook broadcast feature most obviously has echoes of Telegram, as the privacy-focused and encrypted messaging app was among the first platforms to introduce such functionality.

New features to the broadcast channel tool are being tested and are expected to be rolled out in due course. This include collaborators, which enable creators to invite other creators (or fans) to participate in their broadcast channel.

Is It Overkill for Meta’s Social Media Family?

Whilst the news has been welcomed with open arms by brands and creators which have had success engaging more deeply with their followers on Instagram and WhatsApp, some are skeptical it was necessary to roll out the same feature across all of Meta’s platforms. In short, the feature isn’t exactly new – it’s just new for Facebook.

One Facebook user gained 227 Likes (at the time of writing) by simply commenting on Zuckerberg’s post: “I miss how each app used to be unique.”

The additional notifications are a potential cause for concern, and might limit the number of channels one user can actually manage to keep up with. It’s not known why Meta didn’t introduce broadcast channels as a cross-platform feature to begin with, to avoid users doubling up on the same content across multiple apps and accounts.

Fed up of Facebook? Check out our guide and learn all the ways you can delete Facebook today, either for good or temporarily.

Did you find this article helpful? Click on one of the following buttons
We're so happy you liked! Get more delivered to your inbox just like it.

We're sorry this article didn't help you today – we welcome feedback, so if there's any way you feel we could improve our content, please email us at contact@tech.co

Written by:
Abby Ward is a contributor at Tech.co and freelance search engine marketing (SEM) specialist. Since graduating from Kingston University London in 2015 with Bachelor's degree in Journalism with French, she has worked in many areas of digital marketing including website management, SEO, and paid media. Her specialist topics span her professional and personal interests in search social media, ad-tech, education, food & beverage, hospitality, and business.
Explore More See all news
Back to top
close Building a Website? We've tested and rated Wix as the best website builder you can choose – try it yourself for free Try Wix today