clatd
Signal-Desktop
| clatd | Signal-Desktop | |
|---|---|---|
| 8 | 322 | |
| 199 | 14,008 | |
| - | 0.4% | |
| 4.7 | 9.9 | |
| 6 months ago | 5 days ago | |
| Perl | TypeScript | |
| MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clatd
-
Signal Desktop messaging app having trouble with IPv6
For Linux if you have the need for 464XLAT you can use clatd
-
Best practices for home network?
I'd say no. This will break anything that uses literal IPv4 addresses, like games. Unless you also run clatd or something. Just run dual stack, then your IPv4 stuff will continue to work (as well as it ever has, through layers of NAT).
-
are we IPv6 ready?
If you're not running IPv4 at all, you need clients to run something like clatd to do NAT46 locally.
-
IPv6 Only Cloud Server
You can run this on linux to get ipv4 on all types of connections: https://github.com/toreanderson/clatd
Most other OSes like Windows also have a built in CLAT implementation that works similarly.
-
IPv6 is coming.
On the two machines that have this (and whatever appliance devices, which I guess would include our phones), it means I have a full 464XLAT system, so applications running aren't necessarily aware that I don't have a full dual-stack network. On the flip side, I don't have clatd or anything similar running on my laptop, so any software that tries explicitly to create an IPv4 connection is going to fail.
-
TMO Home Internet - First Impressions
There's nothing specific about t-mobiles 464xlat, you just need a clatd to do it. This one should work just fine
-
Connecting to an ipv4 system without DNS entry on an ipv6 only network
This is generally why 464XLAT was invented - at the OS level there's a CLAT daemon that presents itself as an IPv4 networking stack to applications, it translates the requested IPv4 address to a synthetic IPv6 address, sends that to a NAT64 upstream, gets the response over IPv6, and gives the responses to the application over IPv4 again.
-
NAT64 explained (ungleich tech talk number 3)
Typically paired with 464xlat in an IPv6-only environment, for programs that are hard-coded for IPv4.
An excellent `just-works` example is https://github.com/toreanderson/clatd
Signal-Desktop
-
Privacy is Priceless, but Signal is Expensive
2: https://github.com/signalapp/Signal-Desktop/issues/1862
-
Interview on Signal app?
For more Information on how to proceed kindly connect with the HR on Signal app. Download (Signal ) on your mobile device https://signal.org/download/ and connect now with the HR ON +13093936282
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].
[0] https://github.com/electron/electron/pull/39824
[1] https://github.com/signalapp/Signal-Desktop/issues/5195
[2] https://github.com/signalapp/Signal-Desktop/pull/4381
- No longer showing link previews?
-
super choppy video streams
There was a issue opened on GitHub a while back apparently but that was closed due to inactivity. What you might want to do is either open a new issue directly in GitHub (provide as much information as possible and include debug logs) or just send them a support ticket via the support form (and include debug logs).
- Signal Desktop for Windows takes 30+ min to send messages. Phone app still works.
-
Signal Android BETA has text formatting now
Desktop will have it https://github.com/signalapp/Signal-Desktop/commit/9bfbee464bc307a9133ccf43042987343722afe9
-
Signal Desktop messaging app having trouble with IPv6
Issues have been ongoing for the past couple weeks. It's not clear if this is the client or backend. Dual stack works again with v6.20.2, but IPv6-only with NAT64 still doesn't. Actively being worked on, and hopefully some good learnings. Issue link thread: https://github.com/signalapp/Signal-Desktop/issues/6439
-
IPv6 connectivity again with 6.20.1 Update
Alive again with 6.20.2 on Windows dual stack. Directly downloaded from https://signal.org/download/
-
Desktop Client takes minutes to send messages
Fix1, Fix2, Fix3, Fix4
What are some alternatives?
tnat64 - IPv4 to IPv6 interceptor
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
axolotl - A Signal compatible cross plattform client written in Go, Rust and Vuejs
session-desktop - Session Desktop - Onion routing based messenger
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
webclient - Angular webclient (with Linux, macOS and Windows desktop clients) for CTemplar's encrypted email service.
telegram-bot-api - Telegram Bot API server
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
nodegui - A library for building cross-platform native desktop applications with Node.js and CSS 🚀. React NodeGui : https://react.nodegui.org and Vue NodeGui: https://vue.nodegui.org
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
Signal-Android - Patches to Signal for Android removing dependencies on closed-source Google Mobile Services and Firebase libraries. In branches whose names include "-FOSS". Uses new "foss" or "gms" flavor dimension: build with "./gradlew assemblePlayFossProdRelease".
Unigram - Telegram for Windows