Wrote this page! Describing possible moderation actions and spam-fighting methods...
Wrote this page! Installation instructions, modeled after the ones @firstname.lastname@example.org wrote before:
The ending bits are a bit of a lie for now, Mastodon does not include a `dist` directory with templates for the nginx config and systemd services, but I think it should, and I am planning to add that.
Okay, this took a whole day but I mapped out all entities in the Mastodon API along with in which version a particular attribute was added:
Wrote this page:
User Guide: Decentralization
Is there something you think is still missing from that page?
Wrote this page:
User Guide: Basics
Yay! All pages in the User Guide section have content now.
Okay, I remembered to add this page: Upgrading Mastodon to a newer release
@Gargron haven't read it, but feeling a little concerned about docs on moderator actions and spam-fighting methods authored while watching John Wick… 😳
@gargron seems like that page should be under the "Administrator guide" heading rather than the "User guide".
@gargron yeah, but most users aren't mods, right? And iptables won't be available to mods, I would think.
(I'm not bothered by or objecting to any way you want to do it, just noting a potential confusion as a non-expert reader.)
@Gargron May I suggest some notes on this page as to what a silenced/suspended user/site can see? Both remotely and locally - if email@example.com is following me, for instance, and my admin suspends hater.town, can firstname.lastname@example.org see my public toots?
This is a thing that I really feel nobody has a clear picture of unless they've invested the time to decipher the source or to set up a couple of instances to test with.
@anthracite @Gargron I second adding it, but an instance-level suspension will block anyone on that instance from getting anything in any of their timelines etc. but it doesn't prevent people from looking at publicly accessible web pages, such as public account pages which contain all public toots.
Public toots are always completely public. You can't prevent people from reading them via account pages without removing the account pages entirely.
@Gargron It's basically a frontend for iptables. The equivalent to those iptables rules is:
ufw allow ssh
ufw allow http
ufw allow https
It doesn't make a huge difference but I think ufw is easier to understand and maintain, and the guide seems to target inexperienced admins after all.
@Gargron thanks :) i still can’t figure out the profile metadata key/value pairs though. Should a patch on them be a json object?
@Gargron I have no idea what this means but I recognize that it must've taken a while, so thank you.
@Gargron Gotcha. Was just wondering whether it was meant for the absolute novice general public or for people who are already reasonably tech savvy but don't understand decentralization.
@Gargron minor editing note: “Just like an e-mail address. For convenience sake, Mastodon allows you to skip the second part when addressing people on the same server as you....”
First sentence is a fragment, which is fine for this kind of doc but as the second sentence is on a completely diff topic it produces a but of confusion. Either rewording the first sentence or adding a return so the second sentence is a new paragraph should fix the problem
@gargron Looks okay to me. I don't have an account in the git, so can't do it myself: can you change "private" to "followers only" in this chart:
Or change the WebGUI ;)
@Gargron 100x yes! This page contains whole bunch of things that either everyone kept repeatedly asking during the last wave of sign-ons or something that took me a while to figure out.
One small suggestions -- as this document sets the tone for the users. Could you give a few examples of using cw, or even a screenshot of how using cw looks like? In my experience this is the thing new users get confused the most.
I would add this as a PR but I didn't find commits for this on source.joinmastodon.org, maybe this is a local branch?
@Gargron Which compels me to ask -- please add 'contributing' section to describe contribution guidelines and point to current repos where PR requests could be submitted.
@Gargron Maybe some explanation why search on users and toots is different/not possible and the reasoning behind it? This is an argument I get every now and again why Mastodon is so difficult.
@Gargron The old upgrade instructions note that the re-precompiling of assets can be memory intensive and recommends stopping Masto services beforehand. I have to do this or the whole thing falls down on my VPS, for instance. Might be worth keeping that pointer?
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!