This is a very rough list of things to do in Pachli. Some of these are already filed as issues that may have more information, others aren't because I'm trying not to overwhelm the issue list with work that might be several months away.
This list is likely incomplete. See Issues · pachli/pachli-android · GitHub for more.
What and why: Finish the work of splitting the code in to modules:
core:... modules with core functionality
There's some weird stuff in some server responses to /api/v1/instance and /api/v2/instance.
Here's some I've seen in the wild. Format is:
Some of these have been fixed in newer versions of the servers but the fixes haven't fully rolled out.
This is a reply to https://social.polotek.net/@polotek/111973724539175076 which rapidly became too long for a single Mastodon post.
I'm a client developer. I'm largely[^1] building a client that meets my needs, and hopefully it meets others needs as well.
When I see someone having a bad experience (your problem statement was "I can't seem to find many interesting conversations"[^2]) I'm interested in understanding the problem because maybe the client can be changed to improve that. I'll benefit, and so will everyone else that uses the client.
For example, would your experience be better if it was easier to browse or follow the local timelines of servers that are for specific communities? This might show you more people that you would be interested in following because they share your interests.
| /* | |
| * Copyright 2024 Pachli Association | |
| * | |
| * This file is a part of Pachli. | |
| * | |
| * This program is free software; you can redistribute it and/or modify it under the terms of the | |
| * GNU General Public License as published by the Free Software Foundation; either version 3 of the | |
| * License, or (at your option) any later version. | |
| * | |
| * Pachli is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even |
| /* | |
| * Copyright 2024 Pachli Association | |
| * | |
| * This file is a part of Pachli. | |
| * | |
| * This program is free software; you can redistribute it and/or modify it under the terms of the | |
| * GNU General Public License as published by the Free Software Foundation; either version 3 of the | |
| * License, or (at your option) any later version. | |
| * | |
| * Pachli is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even |
At the time of writing the current release of Pachli is 2.1.1, forked from Tusky 23.0, and contains many quality of life improvements and bug fixes. Some of these have subsequently appeared in later versions of Tusky (I try and indicate them below with a "*").
[!NOTE] This is a bit rough-and-ready, but I think it's accurate. Obviously this will become out of date after a new Pachli or Tusky release. Corrections as comments to this gist are welcomed.
The most significant and impactful are probably:
[!IMPORTANT] This is a draft, the translation feature hasn't launched yet.
Pachli Current, and any version of Pachli from 2.0 or later.
Tap the "..." menu at the bottom right of the post, and choose "Translate" or "Undo translate" as appropriate.
| Version | Date | Changes |
|---|---|---|
| 3.0 | 2024-01-22 | Re-write; include the operation information in the nodeinfo |
| 2.0 | 2023-09-25 | Re-write; replace the original suggestion to use the OpenAPI definition with a simpler specification |
| 1.0 | 2023-08-14 | Initial draft |
One of the release tasks is putting together the release notes.
This involves going back through all the merged PRs, figuring out what they did, and boiling that down to a one or two sentence summary.
This is significantly easier if the PR is self-contained. This means:
Took a little play with this, and there's some stuff you might want to try.
Let's think about the type of data in the game.
You already know types like int, string, etc (more on types in https://nikclayton.writeas.com/on-values-types-variables-functions-and-function-hoisting).
We can also create our own types, and decide what are legal values for those types to have. This is especially useful when we're trying to model something like a game, where there's generally a restricted set of values that are valid at any given time.
You already know that it's possible for types to have a limited number of possible values. Whether it's an integer type that can't be used for floating point values, or a boolean type that can only be used for the values true and false.