* Complete re-write of Mastodon Production Guide
I re-wrote the Mastodon Production Guide so that it has a better structure.
Work on this re-write was done on my own repo:
https://github.com/staticsafe/mastodon-documentation
* Fix typo in a heading
* Change node.js Repository section to use curl|bash method.
For simplicity's sake
* Add an explanation of the dependencies
Added in the "Various Other Dependencies" section.
* Fix links to the Ruby project, was using the link to Rails previously.
* Add Let's Encrypt section with a short guide to certificate tool installation, certificate generation and automated renewal.
* Use systemctl instead of service in LE section
This is for consistency reasons.
* Add simpleMastodonBot to list of bots
It's a very, very, very simple mastodon bot, and it's real easy to get started.
* Updated link for author of simpleMastodonBot
* Added my client
To the Apps.md list.
* Please add my app.
Hey guys,
we had agreed that my app would be listed here if I still followed the
GPLv3 and added enough modifications and features to really distinguish
from Tusky.
As of the newest update, we have an AMOLED mode, the ability to
customize the cards and Stories and a fullscreen card view that fill up
all the device space.
In addition to the modifications that had already been made, I feel
like this is distinguishing enough to publish it as one of the apps.
Thanks.
a potential resolution to tootsuite/mastodon#3804, achieved by not
encouraging people to use upload methods without filenames
my rationale for this being the right solution is that it brings it to
parity with the media upload method, which has already proven to be
enough for library developers to understand. it should be enough that,
early in the docs, it says that 'When a file parameter is mentioned, a
form-encoded upload is expected.'
i wouldn't mind so much if the base64 upload method didn't expose such
an insidious bug, but even if it didn't, it seems reasonable to want to
encourage developers to upload all media in a consistent way
