mastodon-jfx is a desktop client for Mastodon written in kotlin using TornadoFX. It is designed for power tooters, particularly ones with multiple accounts spanning multiple instances. It is currently in an Alpha state. It is not yet feature-complete and the Look & Feel is in progress.
* Resorted apps, clarify what's FOSS and proprietary, and ToC
Cause CLI apps and Bots overlapped, I mostly combined them under Command line clients.
* That's not needed anymore
* Not needed, is already clear from the name 'web tools'
* Translated FAQ to french from mastodon funding question to search box question.
* Revert "Translated FAQ to french from mastodon funding question to search box question."
This reverts commit db0a35802a.
* Updated french translation for FAQ
* update after review
* minor adjustment on hastags question
As Mastodon temporaliry saves uploaded content to memory and disk (if
/tmp is a disk), unlimiting client max body size makes the server
vulnerable to DoS attack.
Without headless a lot of (for a server) unneeded dependencies needs be installed (on Debian stretch), like icon sets and x11-utils. Elasticsearch works without problems when you only install openjdk-8-jre-headless (that has much less dependencies).
Consolidated all basic configuration steps for the ideal case to top of document, moved all memory-related and "advanced" configuration to bottom. Removed remote Elasticsearch config from document entirely and replaced it with a link to ES documentation on the topic instead.
db:setup is used in all guides except Docker Guide, which uses db:migrate
to create the database. db:setup is actually superior over db:migrate for
the purpose in terms of performance and compatibility.
db:setup is performant because it does not perform redundant migrations.
db:migrate, on the other hand, executes migration code which will be
dismissed by later migrations. db:migrate also waits for seconds to allow
to interrupt migrations if it is not favorable to run them on a running
server, but db:setup is obviously executed on a instance which is not
running yet, and the wait is unnecessary.
db:migrate has a compatibility issue. It requires a compatibility layer
to keep it working, and such one may be broken, or not provided by
dependencies such as Paperclip.
This commit replaces db:migrate with db:setup in the building guide. The
procedure cannot be applied to migration from an older release, where
the old procedure could, but it is not problematic because it has
dedicated Updating section.
* Add files via upload
additional and updated files for french translation of the user guide
* Add files via upload
French translation of the user guide
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
The anchors with special chars were not working, so I've changed them.
* Add files via upload
additional and updated files for french translation of the user guide
* Add files via upload
French translation of the user guide
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Update User-guide_FR.md
* Clarify Docker instructions for prebuilt images
Made clear there are two options for getting the Docker image: pulling the prebuilt image, or building your own. Using a prebuilt image is easier for anyone who hasn't made code changes on their instance.
* Fix errors in Docker prebuilt image instructions
Kevin Liu