ah i solved it, it's that the max_depth
arg has no sane default, so a client needs to set it manually. currently the server has a hard 300 max value i think.
blocking instances for users was added in 0.19. it works like community block: you don't see any posts from an instance, but you can see the activity of users from that instance on any other instances where they do stuff.
https://github.com/LemmyNet/lemmy/pull/3869
[this is not an endorsement of federating with any meta product. i believe in deplatforming hostile actors, which they've well and truly proven themselves to be.]
i read the page title, then looked at first result and it was mastodon.social and second was mstdn.social.
mayb for your site to match its title you want to not make "federated" the default status sort option?
i also fixed authentication for the 0.19 release, but when your instance actually upgrades (lemmy.ml already has, for testing), it will require you to delete the lem.plstore file in .emacs.d/ and log in again with your password.
& by all means holler if you run into authentication issues during the transition.
EDIT: all good, I worked it out, I found some other api docs.
Is the ModeratorView listing type in this release? If so what feed view is it available in? I can't see it in the lemmy.ml webUI at the moment, nor in the API docs, but the code is merged.
i was going to test these new changes out for my client, but it seems that https://voyager.lemmy.ml is down?
@blawsybogsy
@lemmy.ml