# Remove mention of Molly-FOSS **URL:** https://discuss.privacyguides.net/t/remove-mention-of-molly-foss/35258 **Category:** Site Development **Tags:** completed **Created:** 2026-02-07T07:33:52Z **Posts:** 13 ## Post 1 by @xDVD — 2026-02-07T07:33:52Z The RTC guide currently recommends Molly ([The Best Private Instant Messengers - Privacy Guides](https://www.privacyguides.org/en/real-time-communication/#molly-android)). It mentions the two Molly versions, that being Molly and Molly-FOSS. However, with recent Molly release v7.68.5-1, Molly-FOSS is deprecated since both versions are now unified into a fully FOSS Molly app ([https://github.com/mollyim/mollyim-android/releases/tag/v7.68.5-1](https://github.com/mollyim/mollyim-android/releases/tag/v7.68.5-1)), with UnifiedPush support as well as FOSS Firebase/Google notification libraries. The description should be updated but still mention UnifiedPush. In fact, recommending Molly-FOSS may be inadvisable since it is no longer updated. The guide also mentions public MollySocket instances, but I found these very difficult to find, as there isn’t a public list. Should consider making one, with e.g. [https://molly.adminforge.de/](https://molly.adminforge.de/) and [https://molly.notify.dykes.ca/](https://molly.notify.dykes.ca/). --- ## Post 2 by @anonymous420 — 2026-02-07T08:01:02Z > This release unifies the previous Molly and Molly-FOSS apps into a single fully FOSS app. All proprietary dependencies (including the Play Services SDK) have been removed, while FCM push notifications continue to work via a fully open-source implementation. The dual build variants have been consolidated into one FOSS build. ![](https://forum-uploads.privacyguidesusercontent.com/original/3X/2/7/27bae7f4ec2cb53f5164be7cc36802122aedea74.gif "Borat Borat Very Nice GIF - BORAT Borat Very Nice VERYNICE - Discover &...") --- ## Post 3 by @xDVD — 2026-02-07T09:09:53Z The updated article should probably still mention Molly-FOSS to warn people from using it. --- ## Post 4 by @byesun — 2026-02-07T09:31:10Z Regarding the MollySocket servers, there’s also [https://mollysocket.yourdevice.ch/](https://mollysocket.yourdevice.ch/) and [https://molly.freeyourtech.org/](https://molly.freeyourtech.org/). --- ## Post 6 by @anon42475305 — 2026-02-07T11:08:06Z Yes, we should correct the page to simply list Molly rather than the variants which no longer exist. You are however misunderstanding what actually happened. Molly has always used only a single package name `im.molly.app` which could be seamlessly updated to and from either variant to the other. Now that there is only a single unified Molly release, that is what you will get when updating, regardless of which version you previously used. > [Release v7.68.5-1 · mollyim/mollyim-android · GitHub](https://github.com/mollyim/mollyim-android/releases/tag/v7.68.5-1) > Users with an existing installation of either Molly or Molly-FOSS can install this release as a normal update. No migration or user action is required. --- ## Post 7 by @va3890hd — 2026-02-07T14:23:46Z Just to confirm: I was using the FOSS repo and I don’t have to change my repo or do anything at all, correct? And the same would be true even if I were using the non-FOSS repo? --- ## Post 8 by @null — 2026-02-07T14:39:54Z Yeah, still working. “If you have either Molly or Molly-FOSS installed, just update like usual. **No migration needed.** ” > **[Molly (@mollyim@fosstodon.org)](https://fosstodon.org/@mollyim/115791864290732496)** > > Starting with v7.68.5-1, we've unified Molly and Molly-FOSS into a single fully FOSS app, with no proprietary dependencies. > > We replaced the proprietary Play Services SDK previously used by Molly with our own open-source implementation, so FCM push... --- ## Post 9 by @Archer — 2026-02-07T20:38:43Z > [@anon42475305](#): > > Yes, we should correct the page to simply list Molly rather than the variants which no longer exist. You are however misunderstanding what actually happened. Molly has always used only a single package name `im.molly.app` which could be seamlessly updated to and from either variant to the other. Now that there is only a single unified Molly release, that is what you will get when updating, regardless of which version you previously used. In this case, I think there is no need to warn anyone about Molly-FOSS because it will still get updates --- ## Post 10 by @anon64387538 — 2026-09-19T04:31:51Z @fria Do we have any updates on this? I think this update would be easy, and would vastly improve the recommendations. Currently anyone looking at the Real-Time Communication section is likely to be confused. We just need to remove reference to Molly-FOSS and consolidate the wording for the section to contain the relevant info about UP. (Though, for anyone with only a single app that relies on UP, it maybe should be clarified that UP won’t provide any / much benefit vs. relying on the WebSocket built into Molly.) --- ## Post 11 by @fria — 2026-09-19T16:13:42Z > > > List of changes proposed in this PR: > > - fixed broken link to the Signal harden…ing blog post > - removed references to Molly-FOSS as it's deprecated > - removed reference to updating every two weeks since the last release was two months ago > > relevant discussion: https://discuss.privacyguides.net/t/update-molly-entry-remove-discourage-molly-foss/35258 --- ## Post 12 by @anon64387538 — 2026-09-19T19:31:33Z Thanks so much! Y’all do amazing work. --- ## Post 13 by @dngray — 2026-09-22T04:22:39Z Done in [`d077e5b`](https://github.com/privacyguides/privacyguides.org/commit/d077e5b66bcc2494f35d8fa514bd34018e157f8d). --- ## Post 14 by @jonah — 2026-09-22T17:39:23Z