social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

#molly

2 posts2 participants0 posts today

You know you aren't suffering real problems if you choose to station stewards by a statue to prevent visitors from touching it. #dublin #molly

Also points to the silliness of our culture: both that the statue was shaped that way, and that visitors can't seem to keep their hands to themselves.

Dear @Mer__edith and the the amazing @signalapp team,

After the last update, the Signal "desktop app" is requiring us to launch the mobile app - however, many of us do not have the Android or any other "mobile" version of the Signal app any more.

We are a large (by our standards) group of #Linux phone users, and **your "desktop" app is our "mobile" app** : )

Our previous phones on which #SignalApp was initially activated was an Android or Apple device and we have since then completely migrated to #Linuxphones. Some of us may have registered Signal on #signalcli, Flare, #Molly, Signal Android in #WayDroid, etc.

The #mobileLinux community is growing - we have members spanning a good number of projects and devices, e.g.
- @purism #Librem5 and #LibertyPhone running #Debian-based #PureOS #GnuLinux, #Alpine-based #PostmarketOS or #Mobian,
- @PINE64 #Pinephone and PP Pro running #ManjaroARM, #SailfishOS, etc.
- @furilabs #FLX1 running #Droidian-based #FuriOS,
- a wide variety of Android phones (including OnePlus 6, Google Pixel 3, #Fairphone 4 & 5) running #Alpine-based @postmarketOS ,
- @volla , #Fxtec and #Brax3 devices running #UbuntuTouch by @ubports,
- devices running @mobian which is part of #Debian project, etc.

[Apologies to any project I may have failed to include - you are all appreciated]

(1/n)

My second #OpenBSD #port that got merged into the #ports tree: MollySocket [1]
Mollysocket is for every #Signal user that wants to ditch Google-dependent notifications.
Together with #Molly [2] you can be sure that notifications will only be routed over systems that you choose, using #UnifiedPush.

This OpenBSD port in particular comes with a useful README that should help you to get started quickly. Let's hope that it makes it into 7.7-release :)

See: https://cvsweb.openbsd.org/ports/net/mollysocket/

[1] https://github.com/mollyim/mollysocket
[2] https://molly.im/
cvsweb.openbsd.orgports/net/mollysocket/OpenBSD source via CVSweb
Replied to :ablobpride1: mnmlist :antifa:

@mnmlist
Also, wenn ich das richtig verstanden habe, funktioniert #UnifiedPush mit #Molly und #Nextpush nur, wenn du einen Molly-Socket irgendwo laufen hast: github.com/mollyim/mollysocket
Das heißt vermutlich wird Molly bei dir aktuell immernoch über den Websocket die Benachrichtigungen empfangen.
Ich habe ein #degoogled Android mit #grapheneos und ohne Play Services. Darauf konnte ich mit UP und Mollysocket (Airgapped) den Akkuverbrauch von Molly auf einen Bruchteil (< 1%) verringern.

GitHubGitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.MollySocket allows getting Signal notifications via UnifiedPush. - GitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.

Habe vorgestern mal mit via auf meinem Smartphone eingerichtet .. funzt auch .. die Akkulaufzeit scheint subjektiv verkürzt im Gegensatz zum original Signal was ich vorher nutzte .. irgenwie war damit zu rechnen, immerhin ist 'ne zusätzlich App im Spiel .. aber wie sind so Ehre Erfahrungswerte? .. kann man das irgendwie optimieren? 🤔

Replied in thread

@scy They're all pretty bad. Threema has some major issues with their encryption protocol: infosec.exchange/@Fiona@blahaj

Delta Chat outright lacks forward secrecy, and also doesn't use post-quantum cryptography.

XMPP and IRC are a mess, and essentially unusable for less technical users.
When considering or recommending a messenger, always ask yourself: Would your grandma be able to use it? If she encountered some issue, would she be able to find someone, other than you, who could fix it? That unfortunately rules out a bunch of messengers.

I think best option is to use the @mollyim client for Signal. The second best choice would be @simplex

infosec.exchangeInfosec Exchange
Replied in thread

@ploum @nitot

Est-ce que cela ne dépend pas de ce qui est couvert par « quitter la France » ?

Si c'est enlever l'application des boutiques d'applications pour les utilisateurs français, OK, je vois (mais de toute façon j'utilise personnellement #Molly depuis #fdroid ).

Si ça coupe l'accès aux serveurs depuis une adresse IP française (par exemple), se dépêcher d'installer ne changera rien, n'est-ce pas ?

Replied in thread

@chewie By using Signal-FOSS or Molly-FOSS you just force the Signal app to use its WebSockets-based notification fallback mechanism. But if you have Play services installed and have granted them network permissions, you might as well just use FCM for notifications. It saves battery life compared to each app maintaining its own background network connection.

If you're using @mollyim you also have a third option for receiving notifications: @unifiedpush

But since Signal doesn't support it natively, you need a mollysocket server that receives the Signal notifications and translates them into UnifiedPush format. The mollysocket server is connected to your Signal account as a linked device, but it does not have your decryption keys. There are public instances of mollysocket like mollysocket.adminforge.de

The easiest and best way to get started with UnifiedPush (IMO) is the recently released Sunup distributor app.

GitHubGitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.MollySocket allows getting Signal notifications via UnifiedPush. - GitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.