Sancho Fock's activity
From 07/16/2023 to 07/25/2023
07/25/2023
- 11:33 PM DeadDrop Feature #35 (Closed): Replace scAPI with localLib
07/24/2023
- 10:41 PM DeadDrop Feature #19: Encrypt local config files
- Increased estimated effort, because for this feature it is necessary to refactor the file management and abstract the...
- 10:28 PM DeadDrop Feature #19 (In Progress): Encrypt local config files
- 10:18 PM DeadDrop Feature #33 (Closed): Automaticly delete nonExisting Drops
- 08:28 PM DeadDrop Feature #33 (In Progress): Automaticly delete nonExisting Drops
- 08:24 PM DeadDrop Feature #34 (New): Add popupmenue to DropList
- Pulled item back, because it is easy to implement for Win, MacOS and iOS but not for Android, therefore unassigned it...
- 12:40 PM DeadDrop Feature #34 (In Progress): Add popupmenue to DropList
- 12:37 PM DeadDrop Feature #32 (Closed): Implement Delete Drop
07/23/2023
- 09:08 PM DeadDrop Feature #32 (In Progress): Implement Delete Drop
- 12:48 PM DeadDrop Feature #32 (Closed): Implement Delete Drop
- If the deleting Client is the owner of the drop --> Delete the Drop from Database.
If the deleinf Client is NOT the ... - 09:00 PM DeadDrop Feature #31 (Closed): Optimize NewMessageLookup
- 12:56 PM DeadDrop Feature #3 (Closed): Implement Bulletins (Client)
- 12:44 PM DeadDrop Feature #3 (Resolved): Implement Bulletins (Client)
- 12:43 PM DeadDrop Feature #3 (Closed): Implement Bulletins (Client)
- 12:56 PM DeadDrop Feature #2 (Closed): Implement Bulletins (Backend)
- 12:55 PM DeadDrop Feature #34 (Rejected): Add popupmenue to DropList
- On right click on a DropListItem a Popup Menue shall be opend.
Options : Open and Delete - 12:52 PM DeadDrop Feature #33 (Closed): Automaticly delete nonExisting Drops
- If a Client has a Drop in his Drop List, that does not exist anymore he shall be informed, when he is entering this D...
07/22/2023
- 01:18 AM DeadDrop Feature #31 (In Progress): Optimize NewMessageLookup
- 01:18 AM DeadDrop Feature #31 (Closed): Optimize NewMessageLookup
- Do not load all messages to check for new messages
- 01:07 AM DeadDrop Feature #3 (In Progress): Implement Bulletins (Client)
- 01:05 AM DeadDrop Feature #2 (Resolved): Implement Bulletins (Backend)
07/20/2023
- 02:12 AM DeadDrop Feature #2 (In Progress): Implement Bulletins (Backend)
- 12:22 AM DeadDrop Bug #18 (Closed): Send Message Text not visible when using screen keybord
- 12:05 AM DeadDrop Bug #18 (In Progress): Send Message Text not visible when using screen keybord
- 12:03 AM DeadDrop Feature #1 (Closed): New Message Notification
- 12:03 AM DeadDrop Feature #29 (Closed): New Message Notification Backend
07/19/2023
- 11:57 PM DeadDrop Feature #1 (Resolved): New Message Notification
07/18/2023
- 07:26 PM DeadDrop Feature #1 (In Progress): New Message Notification
- 07:23 PM DeadDrop Feature #29 (Resolved): New Message Notification Backend
- 01:11 PM DeadDrop Feature #29 (In Progress): New Message Notification Backend
- 01:06 PM DeadDrop Feature #29 (Closed): New Message Notification Backend
- The Client shall show an indication in the DropList if there are new Messages in the Drop
- 06:28 PM DeadDrop Feature #30 (Closed): Status Bar Text
- 06:27 PM DeadDrop Feature #30 (Resolved): Status Bar Text
- 12:50 PM DeadDrop Bug #18: Send Message Text not visible when using screen keybord
- Assigned to release 0.2
- 11:35 AM DeadDrop Feature #28 (New): Share / Invite Drops by Bluetooth
- Enable sharing or inviting to Drops via Bluetooth connection
- 11:34 AM DeadDrop Feature #27 (Feedback): Share / Invite Drops by NFC (iOS)
- Enable to share Drop Coordinates or invites via NFC
- 11:34 AM DeadDrop Feature #26 (New): Share / Invite Drops by NFC
- Enable to share Drop Coordinates or invites via NFC
- 11:33 AM DeadDrop Feature #25 (Closed): Attach from Camera iOS
- Enable attaching pictures from the camera
- 11:32 AM DeadDrop Feature #24 (Closed): Attach from Camera
- Enable attaching pictures from the camera
- 11:30 AM DeadDrop Feature #23 (Closed): Enable Attchments
- Enable Sending and viewing File attachments
- 11:29 AM DeadDrop Feature #22 (Closed): Customize End2End Encryption Options
- The User shall be able to select the encryption type(simplecrypt, AES, DES etc) and options (key length etc) for end ...
- 11:28 AM DeadDrop Feature #21 (New): Deviated Drop location
- It shall be possible, to read drops, that are located on other servers. Therefore Dead drop servers mus be able to do...
- 11:27 AM DeadDrop Feature #20 (Closed): Encrypt database content
- All Data values shall be stored encrypted regardless of the drop type
- 11:27 AM DeadDrop Feature #19 (Closed): Encrypt local config files
- The Client configuration Files shall be saved encrypted
- 01:04 AM DeadDrop Feature #17 (Feedback): Protect iOS Client by Biometrics
- The user shall be able to configure if he wants to protect the client by Biometric Features if available in the system
- 01:04 AM DeadDrop Feature #16 (New): Protect Android Client by Biometrics
- The user shall be able to configure if he wants to protect the client by Biometric Features if available in the system
- 01:03 AM DeadDrop Feature #15 (Closed): Protect Client by Password
- The user shall be able to configure if he wants to protect the client by Password
- 01:02 AM DeadDrop Feature #14 (Feedback): Release iOS Client
- Test and Release iOS Client
- 01:01 AM DeadDrop Feature #13 (Feedback): Release MacOS Client
- Test and Release MacOS Client
- 01:00 AM DeadDrop Feature #12 (Closed): Implement Private secure Drops Client
- Private Secure drops are like private drops. But add use end to end encryption
Requires User Roles and invites - 12:59 AM DeadDrop Feature #11 (Closed): Implement Private secure Drops Backend
- Private Secure drops are like private drops. But add use end to end encryption
Requires User Roles and invites - 12:58 AM DeadDrop Feature #10 (Closed): Implement Private Drops Client
- Private Drops are like hidden Drops, but inly available to invited clients
Requires User Roles and invites - 12:57 AM DeadDrop Feature #9 (Closed): Implement Private Drops Backend
- Private Drops are like hidden Drops, but inly available to invited clients
Requires User Roles and invites - 12:55 AM DeadDrop Feature #8 (Closed): Implement invites Client
- Owners can invite others. Invites are similar to the share function, but in invites the client gets authorized with a...
- 12:55 AM DeadDrop Feature #7 (Closed): Implement invites Backend
- Owners can invite others. Invites are similar to the share function, but in invites the client gets authorized with a...
- 12:53 AM DeadDrop Feature #6 (Closed): Implement Displays client
- A Display shall work like a bulletin but only invited clients can write into it
Requires User Roles and Invites - 12:52 AM DeadDrop Feature #5 (Closed): Implement Displays API
- A Display shall work like a bulletin but only invited clients can write into it
Requires User Roles and Invites - 12:50 AM DeadDrop Feature #4 (Closed): Implement USER ROLES
- Read Write and owner. A Drop creator is automaticly owner. A Owner can invite other clients and assign a role
- 12:47 AM DeadDrop Feature #3 (Closed): Implement Bulletins (Client)
- The Bulletin Drop Type, shall be available for creation and use. It shall be possible to query for available bulletin...
- 12:45 AM DeadDrop Feature #2 (Closed): Implement Bulletins (Backend)
- The Bulletin Drop Type, shall be available for creation and use. It shall be possible to query for available bulletin...
Also available in: Atom