Add TntConnect

[ermshiperete]

No description provided.

[TingPing]

So as mentioned in #797 I don't think we want WINE applications. They will never be native, they are impossible to support and are unofficial.

[ermshiperete]

If you don't want to have WINE applications then it would be nice to mention that on the App Submission or App Requirements pages.

It's true, they will never be native. But I don't see what "impossible to support" and "are unofficial" have to do with hosting an app package - my understanding so far was that the person creating the flatpak application will support the application, not the flathub maintainers/community. And whether a flatpak app is official or not depends on the author of the packaged application.

I agree, it would be much nicer to have a native app instead of having to use a Windows app with WINE, but there isn't an existing one that provides the necessary functionality, and I don't have time to develop one. Having a flatpak application that packs the Windows app and WINE simplifies life for other users in a similar situation. But fortunately flathub isn't the only way to distribute, so if it isn't desirable to have it on flathub I'll have to choose a different option.

[TingPing]

But I don't see what "impossible to support" and "are unofficial" have to do with hosting an app package

Regarding being official a goal of Flathub is for authors to package their own work. WINE usage is almost always not upstream authors.

As for support this is debatable since we allow proprietary software already but its just really hard to debug millions of lines of code that is abstracting a proprietary win32 application. By my definition it will never be actively supported.

But fortunately flathub isn't the only way to distribute, so if it isn't desirable to have it on flathub I'll have to choose a different option.

Yes I am very much leaning on that fact. I believe Flathub can be somewhat strict because of this.