| 12 Apr 2024 |
|  @tamero:nope.chat joined the room. | 20:23:13 |
| 13 Apr 2024 |
|  @arnavkumar:matrix.org left the room. | 08:16:10 |
| 14 Apr 2024 |
 connyduck | adding information about translations to our faq: https://github.com/tuskyapp/faq/pull/28 | 13:00:25 |
| 17 Apr 2024 |
 mcc111 | A thought, I've got one room in my apartment where the wifi doesn't reach, and I find that if I boost or fav things in this room in Tusky usually it will fail (checking later the fav/boost did not happen) but I get no error tellling me it failed. Maybe that's something I'd like to look into once the refactors land. | 16:32:37 |
| connyduck | I can think of multiple ways to improve this
- a snackbar at the bottom telling you about the error
- the like/boost button just silently going back to the unselected state
- some kind of retry mechanism that keeps trying to send the event in the background once network is back
| 16:38:25 |
| mcc111 | 1 or 3 sound good to me | 16:50:10 |
 jmrubillon | 3 would be the nicest way of dealing with it. Transparent for the user. May need to consider what happens to the user's action if the post no longer exists or has been modified while the user was offline. | 17:14:21 |
| mcc111 | One problem with 3 is it could interact oddly with "permanent" failures like airplane mode.
With posts, we have this whole "Drafts" area we can use for people to review their failed interactions, but it would be impractical to do such a thing for pending favs/boosts. | 17:21:36 |
| jmrubillon | Whether "permanent" or temporary, one would need to consider what happened to the fav'ed/boosted post since loss of contact. And then there's the question of how frequently does one retry? | 17:44:16 |
| mcc111 | it's definitely something to think about. just showing an error on the other hand is straightforward and might be something we could do quicker (maybe even as a stopgap) | 17:59:25 |
| jmrubillon | True. | 18:01:52 |
| 19 Apr 2024 |
|  rauschen_ set a profile picture. | 07:33:04 |
| 21 Apr 2024 |
|  🛆~#!/usr/taureg💡 changed their profile picture. | 10:45:25 |
| 22 Apr 2024 |
|  marceloexc joined the room. | 03:43:27 |
| 29 Apr 2024 |
|  @voxel:chatwave.org left the room. | 08:22:10 |
| 30 Apr 2024 |
|  @jacksonchen666:jacksonchen666.com joined the room. | 16:53:25 |
| 2 May 2024 |
|  @gnu1dea:matrix.org joined the room. | 08:24:22 |
| @gnu1dea:matrix.org | How can I add Tusky to ntfy if it isn't automatically? | 10:42:43 |
| connyduck | Restarting Tusky should do the trick | 15:08:51 |
| @gnu1dea:matrix.org | Hmm… even an OS restart didn't do it | 16:16:23 |
| connyduck | 🤔 maybe one of them is not at the newest version? Maybe logging in & out of Tusky helps? | 17:07:23 |
| @jacksonchen666:jacksonchen666.com left the room. | 19:43:38 |
| @gnu1dea:matrix.org | Yes, thank you: logging out & in again did it! 😊 | 21:28:23 |
| 3 May 2024 |
| connyduck | Tusky 25.0 is out | 11:19:46 |
| 4 May 2024 |
|  Kevin P. Fleming joined the room. | 12:00:45 |
|  @goingwithout:matrix.org left the room. | 12:35:24 |
| connyduck | Tusky 25.1 is out, it fixes two crashes at startup that prevented some users from using the app | 18:42:24 |
| 6 May 2024 |
|  micaai joined the room. | 13:15:17 |
| 8 May 2024 |
| 🛆~#!/usr/taureg💡 changed their display name from ~#!/usr/mittwerk to ~#!/usr/mittwerk🇺🇦️. | 06:15:30 |
| 12 May 2024 |
 nailyk | I was always wondering: is it on purpose that the messages displayed in the 'private conversation' (the one with the ✉️ icon) is displayed the messages which have been sent only ? And not the received ones ? | 21:52:50 |
