Pyre-Qt issueshttps://git.callpipe.com/pyre/pyre-qt/-/issues2020-01-30T09:59:42Zhttps://git.callpipe.com/pyre/pyre-qt/-/issues/28REQUEST: New messages reflected in the UI2020-01-30T09:59:42ZDevanREQUEST: New messages reflected in the UIWhen I receive a new message, I would like there to be a graphical artifact representing this.
Simple example: The button containing the name of the contact or group could turn blue.When I receive a new message, I would like there to be a graphical artifact representing this.
Simple example: The button containing the name of the contact or group could turn blue.https://git.callpipe.com/pyre/pyre-qt/-/issues/27REQUEST: Ability to create new message2020-01-30T09:57:55ZDevanREQUEST: Ability to create new messageWould be useful to be able to click "New Message", then type in a phone number to send to, and compose my message.Would be useful to be able to click "New Message", then type in a phone number to send to, and compose my message.https://git.callpipe.com/pyre/pyre-qt/-/issues/261-on-1 chats don't show up in UI2020-01-30T09:55:35ZDevan1-on-1 chats don't show up in UIOnly group chats are working for me. I can't see any chats with individuals. I do see that the messages come in through the logs, but they are not reflected in the UI.Only group chats are working for me. I can't see any chats with individuals. I do see that the messages come in through the logs, but they are not reflected in the UI.https://git.callpipe.com/pyre/pyre-qt/-/issues/25Make the database automatically2019-07-05T07:34:30ZYoslMake the database automaticallyThe database should be created automatically if it doesn't already exist.The database should be created automatically if it doesn't already exist.https://git.callpipe.com/pyre/pyre-qt/-/issues/24documentation should reflect dependencies2019-06-18T01:46:06ZYosldocumentation should reflect dependenciespython3-pyqt5
python3-qrcodepython3-pyqt5
python3-qrcodehttps://git.callpipe.com/pyre/pyre-qt/-/issues/23Registering to another phone causes breakage2019-06-18T01:41:01ZYoslRegistering to another phone causes breakagehttps://git.callpipe.com/pyre/pyre-qt/-/issues/22Handle failed authorization from signald2019-05-23T04:24:38ZYoslHandle failed authorization from signaldSteps to reproduce:
1. Register by linking from signal-android
2. register on a different signal-android device
`{'type': 'unexpected_error', 'data': {'msg_number': 0, 'message': 'Authorization failed!', 'error': True, 'request': {'type...Steps to reproduce:
1. Register by linking from signal-android
2. register on a different signal-android device
`{'type': 'unexpected_error', 'data': {'msg_number': 0, 'message': 'Authorization failed!', 'error': True, 'request': {'type': 'send', 'username': '+15555555555', 'messageBody': "This is the message the Pyre-Qt user is trying to send.", 'recipientNumber': '+6665556666', 'expiresInSeconds': 0}}}`https://git.callpipe.com/pyre/pyre-qt/-/issues/21.desktop file2019-05-23T04:16:51ZYosl.desktop filefor expected integrationfor expected integrationhttps://git.callpipe.com/pyre/pyre-qt/-/issues/20Use PEP8 linting consistently2020-04-20T01:13:01ZYoslUse PEP8 linting consistently* [ ] Apply PEP8 to all Python files (in a branch)
* [ ] Establish a workflow for contributors to consistently use PEP8, there are several options to accomplish this.* [ ] Apply PEP8 to all Python files (in a branch)
* [ ] Establish a workflow for contributors to consistently use PEP8, there are several options to accomplish this.Betahttps://git.callpipe.com/pyre/pyre-qt/-/issues/18automatically scroll on post2019-05-18T08:00:29ZYoslautomatically scroll on posthttps://git.callpipe.com/pyre/pyre-qt/-/issues/17basic documentation is inconsistent2019-05-09T03:50:45ZYoslbasic documentation is inconsistent[pyre.chat](https://pyre.chat) and the \[README\](README.md) have varying and incomplete documentation.[pyre.chat](https://pyre.chat) and the \[README\](README.md) have varying and incomplete documentation.BetaYoslYoslhttps://git.callpipe.com/pyre/pyre-qt/-/issues/16The contacts dock and buttons are too wide and cannot be adjusted.2019-05-09T03:04:08ZYoslThe contacts dock and buttons are too wide and cannot be adjusted.It has the correct spacing for a moment, and then extends out.
![Screenshot_2019-05-08_19-53-17.cleaned](/uploads/bb66e69b0d6e11cc8bb6b14cbc4bde4c/Screenshot_2019-05-08_19-53-17.cleaned.png)It has the correct spacing for a moment, and then extends out.
![Screenshot_2019-05-08_19-53-17.cleaned](/uploads/bb66e69b0d6e11cc8bb6b14cbc4bde4c/Screenshot_2019-05-08_19-53-17.cleaned.png)Alphahttps://git.callpipe.com/pyre/pyre-qt/-/issues/15Native notifications from other applications open Pyre-Qt2019-05-08T06:51:43ZYoslNative notifications from other applications open Pyre-QtSteps to reproduce:
Debian Buster XFCE with Wire-desktop installed:
Opening Wire notifications opens Pyre-Qt.Steps to reproduce:
Debian Buster XFCE with Wire-desktop installed:
Opening Wire notifications opens Pyre-Qt.Initial ReleaseAidanAidanhttps://git.callpipe.com/pyre/pyre-qt/-/issues/14Emoji rendering in main window.2020-04-20T01:12:31ZYoslEmoji rendering in main window.Emojis display in native notifications, but not in the chat window.
Feel free to help.Emojis display in native notifications, but not in the chat window.
Feel free to help.StableYoslYoslhttps://git.callpipe.com/pyre/pyre-qt/-/issues/13toggle show/hide in tray menu2019-05-10T07:36:54ZYosltoggle show/hide in tray menuThe tray menu should have an entry that toggles the window, instead of having two entries for show and hide.The tray menu should have an entry that toggles the window, instead of having two entries for show and hide.https://git.callpipe.com/pyre/pyre-qt/-/issues/12Documentation should have instructions on how to use signald2019-05-08T06:52:32ZAidanDocumentation should have instructions on how to use signaldNeither the website nor the readme have anything about signald.
There should be instructions on signald use in the site and readme.Neither the website nor the readme have anything about signald.
There should be instructions on signald use in the site and readme.Betahttps://git.callpipe.com/pyre/pyre-qt/-/issues/10exception on application start when signald is not running2019-05-10T07:39:14ZAidanexception on application start when signald is not runningCan we start signald on our own?
Perhaps as a stopgap we can put up a dialogue notifying the user to start signald.Can we start signald on our own?
Perhaps as a stopgap we can put up a dialogue notifying the user to start signald.Stablehttps://git.callpipe.com/pyre/pyre-qt/-/issues/8Custom Emojis2019-05-19T00:32:19ZAidanCustom EmojisWe have a stated goal of mutant standard
I suggest that we make a folder in ~/.config/ such as ~/.config/pyre that then contains a folder (emojis/) containing PNGs and a file (index) containing mappings of shortcodes (:blobcatuwuface:) t...We have a stated goal of mutant standard
I suggest that we make a folder in ~/.config/ such as ~/.config/pyre that then contains a folder (emojis/) containing PNGs and a file (index) containing mappings of shortcodes (:blobcatuwuface:) to png filenamesStablehttps://git.callpipe.com/pyre/pyre-qt/-/issues/3Signald not started automatically with Pyre-Qt client2019-08-18T03:09:58ZAidanSignald not started automatically with Pyre-Qt clientCurrently the client fails somewhat silently if started without signald providing a socket at /var/run/signald/signald.sock
While it is totally reasonable for a bot to exhibit this behavior, a messaging client probably shouldnt do this....Currently the client fails somewhat silently if started without signald providing a socket at /var/run/signald/signald.sock
While it is totally reasonable for a bot to exhibit this behavior, a messaging client probably shouldnt do this.
There are a number of potential solutions
1. display a dialogue to user telling them to turn on a system wide signald daemon
2. try to start a system-wide signald daemon
3. manage a local signald daemon and start it with the client
I think that it is most reasonable to go with number 3.
Given that signald will persistently contain state that is related to signal-qt it is important that we not allow other signald applications access to our signald instance. In fact, later on down the road if we are keeping an application local signald distribution we can perform authentication maneuvers like encrypting it when not in use.
TL;DR: We should figure out the best way to bundle signald with Pyre-Qt, and run it as a subprocess of our application.Stable