Getting in touch
Three doors, and the right one depends on what you have. The guide inside the program answers most of it first.
Where to send what
A bug, or something missing
Open an issue on the public repository. Say which version you are on, which is in the settings screen and in vobuda state, and what you expected instead. Every fault that gets fixed gets an identifier and a check named after it, so a good report becomes a permanent guarantee.
A question about using it
The guide is inside the program, in your language: Help, then How to use vobuda. It covers every feature and is written for somebody who does not program for a living. It lives in the binary rather than on disk, so it is there on a machine that has never been online, and an update brings the new one.
The licence, or anything else
Write to [email protected]. If you need something the licence does not give you, ask: the answer is often yes.
Two things worth checking first
Run vobuda state and vobuda log 20. The first prints what is in the window: tabs, blocks, the panel, the theme. The second prints the program's own log. Both go in a report and both usually answer the question on their own.
Then check the version. The program looks for a new one once a day and puts a strip above the layout when there is one, and there is also Check for updates in its own menu. A fault fixed three days ago is the most common reason something is not behaving.
Who you are writing to
vobuda is made by Shifton Inc, which also makes shifton.com and rolchat.com. It is a small team, and the person who reads your issue is one of the people who wrote the thing you are reporting.