# Liveness check: community.general.bearychat **URL:** \ **Category:** Project Discussions\ **Tags:** community-general, deprecation, is-it-alive\ **Created:** [July 28, 2025, 4:31am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144 "2025-07-28T04:31:33Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [July 28, 2025, 4:31am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/1 "2025-07-28T04:31:33Z")
Hi everyone, I was reviewing something else in the community.general collection and the module `bearychat` came up. Curious - I have no recollection of hearing about that chat before, even though I have probably seen the module some other occasion - I looked at the code. There is no hardcoded URL, but everything seems to point to [bearychat.com](http://bearychat.com). Every search I make about the chat seems to indicate something abandoned about 3-4 years ago: - [bearychat.com](http://bearychat.com) - [Beary Innovative · GitHub](https://github.com/bearyinnovative) - [Python API at PyPI](https://pypi.org/project/bearychat/) I could not find any indication that this is installed on-premises as well, so presumably it would be only the hosted service on the internet. A lot of the information out there is in Mandarin and the piece I used G Translate with did not help much. Can anyone confirm whether this is still working? Unless told otherwise, I am inclined to deprecate the module (long deprecation period) and if no one complains, remove it later on. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [July 28, 2025, 6:15am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/2 "2025-07-28T06:15:29Z")
Good spot. I think we can just remove it in the next major version of `ansible` ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [July 28, 2025, 6:28am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/3 "2025-07-28T06:28:52Z")
Err… this is not a collection, just a module in community.general. Unless we get a final confirmation that the service is not available (rendering the module utterly useless), it should take the regular deprecation route, meaning it will be another year until it goes away. Right? 😃 ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [July 28, 2025, 8:00am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/4 "2025-07-28T08:00:37Z")
`bearyinnovative.com` got domain squatted after July 2014 `https://hook.bearychat.com/` no longer resolves (from the examples) I found this post [saying BearyChat was discontinued](https://laravel-notification-channels.com/bearychat/) and [here](https://github.com/laravel-notification-channels/bearychat/issues/15) So I think we can just remove without notice. I don’t see any [specific changes to the Ansible module](https://github.com/ansible-collections/community.general/commits/main/plugins/modules/bearychat.py). ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [July 28, 2025, 8:48am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/5 "2025-07-28T08:48:05Z")
@gundalow thanks for doing the spelunking work 🙂 submitting a removal now. Cc: @felixfontein ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [July 28, 2025, 9:33am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/6 "2025-07-28T09:33:12Z")
PR created: > > > \##### SUMMARY > > The bearychat service seems to be unavailable for a number of y…ears now. > > See more at: > https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144 > > > > > > \##### ISSUE TYPE > > \- Bugfix Pull Request > \- Feature Pull Request > > \##### COMPONENT NAME > > bearychat ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [August 8, 2025, 5:13am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/7 "2025-08-08T05:13:38Z")
For the record: the deprecation has been merged, and removal is set to community.general 12.0.0 ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [August 9, 2025, 3:52am UTC](https://forum.ansible.com/t/liveness-check-community-general-bearychat/44144/8 "2025-08-09T03:52:48Z")
@russoz thanks again for spotting this and keeping our collections tidy.