Support
As of TwoTile 1.0.9 (public beta).
How to contact us
There are two contacts, shared by all software made by poola-vii. We recommend the first one, https://github.com/poola-vii/support. Whichever you use, make it clear that your message is about TwoTile.
| Contact | Best for |
|---|---|
| 1. https://github.com/poola-vii/support (recommended) | It has a form for each kind of request, so you can include everything we need. You can also read other people’s reports and our replies |
2. Email (poola.vii.support@gmail.com) |
For people who don’t have, or don’t want, a GitHub account |
| Request | How to send it |
|---|---|
| Bug reports, questions about how to use TwoTile, and feature requests | Post from Issues in the first repository, choosing one of the forms. Posting requires a GitHub account (free). If you don’t have one, email is fine too |
| Security vulnerability reports | Send them with Private Vulnerability Reporting from the Security tab of the first repository. Don’t post them in a public issue. If you don’t have a GitHub account, send them by email |
| Something you wrote in a Microsoft Store review | When we notice it, we reply publicly and point you to these contacts, because Store reviews don’t allow one-to-one conversations |
We don’t make public what you send us by email. If we find that it affects other users too, we may write about it in the first repository or in Known Issues, in a way that doesn’t identify you.
Please don’t include
Anyone can read public issues. Don’t include the following. Even by email, don’t send credentials or raw logs.
- Raw logs: As described in How to Collect Logs, read them and remove anything private before you paste them
- Personal information: your name, address, phone number, email address, workplace, and so on
- Credentials: passwords, tokens, API keys, and so on
- Details of vulnerabilities that haven’t been made public: use Private Vulnerability Reporting
If we find that a post includes any of these, we may edit or delete it.
What to tell us
See §3 of How to Collect Logs. With these three things, what you did and what happened, the TwoTile version, and the Windows version, we can look into most problems.
Scope of support
What we do
- Look into bugs in the latest version released as a public beta
- Answer questions about how to use TwoTile
- Keep Known Issues up to date
- Fix what we decide to fix (in the next version)
What we don’t do
These are things we can’t do. It doesn’t mean we take your report lightly.
- Support for old versions. Please check whether the problem also happens in the latest version before you tell us.
- Environments we’ve decided not to support. ARM PCs, 32-bit Windows, and operating systems other than Windows.
- Anything listed under “By design” in Known Issues. We chose that behavior for a reason. We’re still happy to hear your opinion.
- Custom work for a particular environment. We don’t add features just for one specific app.
- Sorting out problems caused by combining TwoTile with other software. If you run TwoTile with another window manager, they fight over the windows.
- Support by phone or in person.
What we can’t promise
This public beta is made by an individual in their spare time and distributed free of charge.
- We can’t promise how quickly we’ll reply. It may take days or weeks, whichever contact you use.
- We can’t promise to act on every report. We may decide not to fix something. If so, we’ll tell you why.
- We can’t promise to keep distributing TwoTile. We may stop. If we do, we’ll announce it at the download source.
- During the public beta, behavior may change without notice. Big changes are noted in the Changelog.
For details, see the Terms of Use.
Language
We accept questions in Japanese and English. Replies to questions in English may take longer than replies in Japanese.