Jannis Mattheis

Sounds like a good idea, maybe it would be smart to use goreleaser as it already has functionality to create snap releases https://goreleaser.com/customization/snapcraft/

Hey @Claudiohbsantos, I haven't really thought about this, but looking for the config file in the same dir as the executable seems like the better approach.

I think this is already fixed with https://github.com/gotify/cli/commit/61a3e6c290f6145b12a6eda94db6063822232ea3 this isn't released yet, but I'll do this now.

I think it is mainly about the `~/.config/gotify/cli.json` configy. Since v2.0.0 the config was ignored (due to a bug) but this is now fixed in 2.1.0.

Where exactly is the ambiguity? With text/plain the text just get rendered as text, therefore only a `"\n"` is needed. Markdown uses a markdown renderer which implements a certain markdown...

We can add documentation for this to gotify/website, however in gotify/cli we can fix this behavior and just see \n as a linebreak, see above pr.

Here it is recommended to compile the go program in your termux environment https://github.com/termux/termux-app/issues/210#issuecomment-265733873

go build should be enough, there are no extra steps.

Dns lookup works if the cli is compiled on termux. 

I just did: ``` pkg install golang git git clone https://github.com/gotify/cli cd cli go build ./cli init ```