mastodon VS documentation

I'm the admin of a small server, which I set up a few months ago with the one-click install and then migrated to glitch-soc (https://glitch-soc.github.io/docs/). Recently I tried updating it to the new version of glitch-soc due to recent security updates. However I seem to have broken my server.

I imagine it might turn out to be something similar to https://glitch-soc.github.io/docs/

Have a look at glitch - a fork of Mastodon that looks and feels and behaves mostly just like mastodon but has Markdown support.

A good start to see Mastodons upstream finally implement features considered so necessary that they existed in a fork for years beforehand[0].

I'm not trying to sound cynical, this is legit a good change. Other fedi implementations have supported different message formatting (mainly markdown) for ages and that shit still degrading away to plaintext on Mastodon is extremely aggravating if you decide to (for example) use a bulletpoint list.

[0]: https://glitch-soc.github.io/docs/

You don't have to maintain a soft fork; Glitch-soc is a "friendly fork" which shares maintainers with upstream and has lots of great features, including a configurable post length limit.

What the fuck is your problem? Why do you some here just to see? Are you so fucking retarded that you don't think this issue have been brought up before? Do you think I'm just making up this on the spot? https://github.com/glitch-soc/mastodon/pull/1502 https://github.com/GlitchCatFedi/Policy/blob/main/Global%20Fulltext%20Search.markdown

Can we expect to see any of the https://glitch-soc.github.io/docs/ features coming to Mastodon mainline soon? Post formatting? Highlighting of misleading links? or local only posting?

Mastodon Glitch Edition

So this one is a fork, and infosec.exchange is a fork (https://github.com/glitch-soc/mastodon); are the mastodon committers opposed to incorporating those changes, or this fork situation is "as it should be" while these experiments run their course?

I'm all for experimentation, but since "the exodus" I've become acutely aware of how many instances are out there advertising their version number, so the first big rails (or mastodon itself) vuln is going to be some ooooonooooz

The Fediverse is inherently difficult to understand and use. Their documentation, sadly, is written as a sales pitch for the federation piece of it, but doesn’t make it simple to understand. This summary is better, but parts of the explanation still don’t make sense when trying to access content. I couldn’t figure out how to see Mastodon toots from other servers, as an example.

My next task is triaging and labelling issues and pull requests in the documentation repo on GitHub, with an aim to bring in as many of those existing contributions as we can. I am particularly focused on the API, and I am not currently so familiar with other topics (Mastodon server installation, administration, etc), so I'll be relying on additional help! I am aware that some of the issues and PRs have been waiting for a while, but I'll do what I can to get things improved here.

that said, you can achieve what you're asking but it's tricky: https://github.com/mastodon/documentation/blob/archive/Running-Mastodon/Serving_a_different_domain.md

I recommend you go through their documentation. It's very well written. https://docs.joinmastodon.org/

I honestly begin going to the Mastodon docs and reading. https://docs.joinmastodon.org/

https://github.com/mastodon/documentation documentations are here. I guess you can upload your documentation in the manner in the style as seen there. Although the documentation that you want is more related to code.

Anyhow, if you want to really learn what it is about, their docs are actually good at explaining that https://docs.joinmastodon.org/, but it is definitely too much for normal people.

Before I dive in too far, let's talk about microblogging and federation as Mastodon describes it. For microblogging, the Mastodon docs say:

The only other issue I hit was getting certbot to work. I found the answer to that little problem via an update in this GitHub issue (namely: disable the site altogether, run certbot in standalone mode, and then enable the site and update the certs section). I need to push a PR for this as well, but wording it will be a pain.