fritter VS documentation

I'd like to see more attention put into carving out a subset of Mastodon's functionality that would allow you to host your fediverse node on a static site, à la blog feeds powered by RSS/Atom.

Prior art: Fritter <https://github.com/beakerbrowser/fritter>

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.