On this forum there is open discussion about Taking ownership of Signal Flatpak, but in my humble opinion, we need to have some measurements, before we can be taken more seriously by Signal desktop team. Can you please answer to bellow questions. Thank you. Which Signal on phone are you using: p...
There are big wishes for Signal to adopt the perfectly working Flatpak.
This will make Signal show up in the verified subsection of Flathub, it will improve trust, allow a central place for bug reports and support and ease maintenance.
Flatpak works on pretty much all Distros, including the ones covered by their current "Linux = Ubuntu" .deb repo.
To make a good decision, we need to have some statistics about who uses which package.
Signal wants to provide updates themselfs to make sure they are fast in case of big security bug. F-Droid can lag behind to provide new version of app.
F-droid is only a few days behind at most. They are arguing against F-droid with evidence that's out of date. I think it has more to do with laziness than anything.
The worst part about signing up somewhere is the amount of email spam that will land in you inbox. I don't know about their specific configuration, but by default Discourse (the forum software they use) sends weekly "digest emails" if you haven't visited the site for a week. So make sure to turn them off.
Use SimpleLogin and Bitwarden for everything. I never use the same email or password anywhere and can turn off receiving emails from the source for each account.
That's the biggest pain point with Signal and WhatsApp in my opinion. Telegram does it, but then of course it's much easier for them to support. Sharing content from my tablet is such a hassle.
Same. I just didn't have any use for signal after SMS removal. Yes I know SMS is insecure but I was stuck. Either you use a separate secure app and magically convince everyone else to use it whilst falling back onto a separate SMS app anyway (for those who don't use the encrypted app). Or alternatively you just have to use a mainstream app like Google Messenger with SMS plus RCS.
At least when signal supported it I could migrate family to signal and then our communication would be encrypted and they could still message everyone else over SMS. It meant a large portion of my messages were encrypted. After SMS removal everyone I had on signal just quit so there was no one to communicate with. Trying to get people to use multiple apps was like herding cats.
My parents are approaching 60. I told them that the signal text message app would work a lot like iMessage if we both used it. And it did. It was great. For the other people that used signal, the experience was generally better. For other people that didn't, SMS was fine because that's how I was going to talk to them anyway.
The thing is, My parents are not going to go to more than one app to communicate with other people. Since it no longer sends and receives text messages, it doesn't work with 99% of the other people in their lives.
They own and run a pretty large business. There's no way that they're staying on more than one messaging platform. You can talk all day about what they "should" do, but at the end of the day just getting them to switch to another app was a huge lift for me. Not only did they switch back to regular SMS, I burned a lot of credibility with them on tech related stuff through no fault of my own.
Repeat this story for the 90 or so people I had converted. There was no critical mass, so adoption evaporated overnight because my social graph is not enough to provide any sort of critical mass and adoption.
You do realise that mobile data is non-existent or limited in some counties right? Even here in New Zealand mobile data is still limited or expensive and the main communication, especially between people who don't know each other, is SMS. Some encryption is still better than nothing.
First being able to use the service first-class on the desktop without registering with phone app first.
Second is using native desktop technologies for the app, as Signal currently uses Electron so it is basically a website running in separate Chromium web browser without tabs.
Hahaha, any comment here makes no sense. This is just to help that guy have an actually somewhat useful survey, because Signal devs have very strange priorities
There is Flare. I haven't used it myself because it's not official and I don't know what it will do to e.g. my backups, but just sharing in case you're interested.
I prefer the deb that works. I get a signal.update almost every other day. I don't remember to update my flatpaks anywhere near that often. I also appreciate that it doesn't force me to include dependencies that are already met.
Automatic updates are a thing and should be everywhere.
Absolutely not...most especially prior to production deployment. How else would someone see the change logs before hand or see/test if it would hurt their environment?
I'd love this but also temp sub users, I have it linked to my phone but I'd like to keep my real username and phone number private if using the app outside of my circle.
I'm thinking about abandoning Signal given the fact that they use AWS servers, still insist on requiring a phone number to use the APP and haven't yet implemented nicknames like Telegram
If you want absolute control over your communications, the only way is to self-host an XMPP server
Your data is always encrypted before it reaches the AWS servers though, so it's not like Amazon has access to them. The phone number/nicknames is still in progress, but it's hard to do that securely, and given that their user base is really big now, they also need to make sure it works well for everybody.
Element, the Matrix reference client, is too complicated IMO. If everyone were to only use FluffyChat, it would be great but then FluffyChat afaik doesn't implement every protocol feature and and you could end up in compatibility issues with Element users.
Purely as a client I find Telegram the most convenient. I think more should copy their homework from there, heck perhaps post the client to Matrix.
Personally I install it with pacman and generally avoid Flatpaks due to annoying problems I've had with it limiting filesystem access in the past. My biggest problem is that it seems to "forget" that I'm logged in if I don't use it regularly, meaning I have to regularly re-auth it on my desktop since I use it infrequently there.
Flatpaks are generally made way to loosely. Always "not breaking" > "being secure".
So this should not really be the case, drag&drop doesnt work yet, maybe copy-pasting files doesnt if the app cannot access that directory statically (you need to add an attachment from within the app, your file picker will open which is a "portal" which links that file into the apps container and thus allows the app to see it.)
Last time I installed slack through flatpack I couldn't send any files. Not through drag-and-drop, neither through the filepicker. The latter was just empty.
Downloading files from slack also had awfully weird side-effects.
Slack doesn't have an apt repo, so I download debs and updat manually. Maybe once half-a-year.
If that's the experience I'd get on my signal through flatpack, I'd also rather be downloading manually. And I'd even compile from source rather than deal with that flatpack stuff.
That's an understandable goal, but as a user, breaking the user experience when I go to send a file to someone only to find that I can't even see it in some apps is a deal breaker. If the app can't be trusted to do that, I won't use it.
This is just so bad. I can't use anything snap/flatpack cuz it simply won't let me send a file. As it runs on it's on file subsystem and doesn't have access to anything else.
On the other hand, an app that has access to my entire hard-drive is awfully insecure, right? So, what's the solution?
in the meantime they could include an option "I allow this app to acess my whole $HOME, thanks, I need it cuz I am a user not a security researcher". Until then I'm not touching flatpack
The post here is a link to an online survey being done by the Signal Community. Users need to follow the link to answer the survey if they wish (but it means creating yet another new account which I'm getting pretty tired of as I'm now passing over 900 different logins all with unique passwords etc ;-)
The appeal of signal is it is a good option (may have flaws but it is better than say discord) and it's pretty easy to get normies using it, all the other alternatives you mentioned are obscure and convincing normies such as friends and family to use them is much harder, and while signal isn't perfect, it's certainly better than whatsapp or other proprietary solutions
So... not using Signal because it's based off a conspiracy theory that it's secretly funded by CIA?
Well, let's stop using RSA and encryption because the most used secure crypto algorithms today were created by none other than the NSA!
EDIT: None of the alternatives provided are good alternatives for Signal. Matrix is an extremely complicated protocol that lacks some features compared to normal IM apps (I use Matrix and the experience is quite close to a standard messaging app). XMPP is dead and has a very niche userbase. The others are not suitable for being a daily messaging app.
Signal is a good alternative and while I do agree with some points, they are not bad enough to prevent you from using it (e.g. not having usernames).
I tend not to use flatpack. I lost a few nights trying to get OBS plugins to work in flat pack. It would probably be fine for something as simple and straightforward as signal. But it's more or less nothing but disadvantage to end users. That said I'm sure it's a great savings for you guys.
Luckily for me, I'm on an Ubuntu derivative. So apt upgrade just does it. Sorry, OP, works for me in my preferred way, I don't need any flatpacks. Let's hope once they do one they keep building .debs nonetheless.
Flatpaks work just as well. It is an electron app, that causes all the bloat. Signal is modern and everything apart drag&drop and maybe a tray icon (havent tried that) works.