More "security" software that blindly accepts effectively unaudible binary updates from a third party.
Standalone Signal Desktop
91–100 of 320 posts
Re: Standalone Signal Desktop
#92Earlier quoted context omitted.
eul is a light (4 MB) native desktop client for all popular messengers: https://eul.im Signal support is coming later this year. Right now it supports Slack, Skype, Facebook, and Gmail.
native in that it's not a web-app, sure, but it sure doesn't feel like a native citizen on the mac. window can't be resized, standard menus are missing, standard keyboard shortcuts for text fields don't work, conversion text can't be selected, no way to cut or copy text (tho paste does seem to work). is it implementing its own ui toolkit? qt maybe?
These are valid observations.
Right now the focus is on features and performance, but the app is going to be polished before the 1.0 release to have a more native feel: native notifications, shortcuts, textfields, etc.
Re: Standalone Signal Desktop
#93Earlier quoted context omitted.
eul is a light (4 MB) native desktop client for all popular messengers: https://eul.im Signal support is coming later this year. Right now it supports Slack, Skype, Facebook, and Gmail.
does it support relevant slack features...gifs, slackmojis, tags, etc?
Not yet. Right now only mentions and threaded conversations are supported. But most of these features will be implemented in the future.
Re: Standalone Signal Desktop
#94Why no web app? Moxie closed https://github.com/WhisperSystems/Signal-Desktop/issues/723 without giving any reasoning. Can someone link me to a blog post that explains why Signal is refusing to release a web version? I cannot run another Electron app on my computer, I simply do not have the RAM left. Signal as a web-app would allow me to put it inside of Franz or Rambox, where all my other chat services live. Right n…
They are a small non-profit dev group, and resource wise it's probably not worth it for them. You could indirectly solve this problem by making some sort of electron multiplexer that could take multiple electron apps and make them share the same electron host browser, achieving the same thing you have now. I personally just use a bluetooth keyboard and my phone. I get a native app, keyboard typing and nothing hogging…
The issue with doing that though is that most Electron apps don’t use the same version of Electron. I have apps I’ve built that are still running pre-v1 because updating has been too much of a headache.
Re: Standalone Signal Desktop
#95Earlier quoted context omitted.
I think he is waiting for it to be a certain level of 'done' before he open sources it. Open sourcing something creates it's own workload.
No, I think it's more than that. He specifically said that it won't be possible to open-source some parts.
You both are right actually :)
Re: Standalone Signal Desktop
#96"If you’ve never used Signal Desktop before, this is a great chance to start. Download the app, pair it with your phone, and experience private messaging with all ten fingers." So it is not _really_ standalone. You still need a phone. This is still a geeky version of WhatsApp. In fact, why would I want to use this instead of WhatsApp if they're basically using the same encryption features and I have to trust the same…
You need to pair it once with your phone for installation.
I don't have a phone that can install the app. So I can't use it.
Re: Standalone Signal Desktop
#97Earlier quoted context omitted.
native in that it's not a web-app, sure, but it sure doesn't feel like a native citizen on the mac. window can't be resized, standard menus are missing, standard keyboard shortcuts for text fields don't work, conversion text can't be selected, no way to cut or copy text (tho paste does seem to work). is it implementing its own ui toolkit? qt maybe?
These are valid observations. Right now the focus is on features and performance, but the app is going to be polished before the 1.0 release to have a more native feel: native notifications, shortcuts, textfields, etc.
cool, good to hear. with enough dedication and an eye for ui detail, i believe it is possible to make a custom-widget app feel like a good citizen -- the unity editor is a good example of this, imo. it's a ton of work tho!
(actually, i'm not sure if it's possible to make your app friendly to screen readers w/o using native widgets. maybe?)
if you do pull it off, you'll end up with a great ui toolkit for go. that would be a very interesting thing!
Re: Standalone Signal Desktop
#98Design is somehow looking related to Telegram...
Re: Standalone Signal Desktop
#99Re: Standalone Signal Desktop
#100Earlier quoted context omitted.
These are valid observations. Right now the focus is on features and performance, but the app is going to be polished before the 1.0 release to have a more native feel: native notifications, shortcuts, textfields, etc.
cool, good to hear. with enough dedication and an eye for ui detail, i believe it is possible to make a custom-widget app feel like a good citizen -- the unity editor is a good example of this, imo. it's a ton of work tho! (actually, i'm not sure if it's possible to make your app friendly to screen readers w/o using native widgets. maybe?) if you do pull it off, you'll end up with a great ui toolkit for go. that woul…
Non-native widgets can certainly be accessible with screen readers and other assistive technologies. But it's a lot of work. You'll need to implement the UI Automation provider API for Windows, AT-SPI for desktop Linux, and the Cocoa accessibility API for Mac. And you probably won't get any of them right the first time. So I think it would have been better not to create a custom toolkit.