Moderation part 2 is here!

Part 3 will come soon, with user banning.

New Features

Modqueue and post/comment reports

You can now access a queue of reported post/comments, if you’re a mod/admin! Just head over to Profile -> Moderator (Admin) Zone and click “Modqueue”. Alternatively, you can go to a specific community and view the modqueue for that community.

Here you can easily approve/remove content. Once approved or removed, Voyager will automatically resolve all reports associated with that piece of content.

What’s cool about this in Voyager is if a post is flagged as reported, you will be able to see that flag throughout the app - not just in the modqueue. This can be helpful when going to a thread for additional context, for example.

Note: Reports sync every 10 minutes, or every time you refresh the modqueue.

Note: This feature may not work well on the largest lemmy instances, like if you’re an admin of lemmy.world. So please contact me if you’re having issues. :) It should be considered a beta, for now.

Admin support

There’s now support for Admin moderation in Voyager? But what does that mean?? Well… pretty much every moderation action is the same as regular mods, except every single post/comment can be removed and admins can view all reports, etc.

However, color coding for admin actions has been introduced!

Whenever you see a shield, it will be either green or red. If it’s green, it means you’re explicitly a moderator of that community (or post/comment within) as a signal to you.

If you see a checkmark within the shield, that means that moderation actions will be federated to other instances. While you can remove any post on your instance, for example, if you remove a post on !memes@lemmy.world from your custom instance, obviously this will not propagate.

However, if you remove a post from a local community, that will propagate.

This is a helpful signal when deciding how to act on any one particular piece of content.

iOS build size reduced

RevenueCat used for in-app tipping is quite a heavy sdk. I’ve switched to a custom-built, lightweight solution.

What’s Changed

Full Changelog: https://github.com/aeharding/voyager/compare/1.25.0...1.26.0

  • Sentau@feddit.deEnglish
    3·
    11 months ago

    RevenueCat used for in-app tipping is quite a heavy sdk. I’ve switched to a custom-built, lightweight solution.

    Slightly off topic but have you seen an increase in donations since the introduction of in-app tipping¿? If yes, then other open source apps could also implement this. The current funding and donations space of the open source community is in a poor state. I try to help by donating but I am from a developing country with a low cost of living so my donations are usually small amounts. Hopefully with in app tipping non tech oriented people who moved to lemmy are also donating.

    • aeharding@lemmy.worldOPMEnglish
      2·
      11 months ago

      Yeah, I’d say there’s been an uptick, nothing drastic though. I like that its easier for people than github sponsors/liberapay but google/apple take a 15% cut which is the downside.

      Implementing in-app tipping is pretty straightforward from a development standpoint, at least for the play/apple stores. I think it makes sense for apps to add, as you say, especially for casual and non tech savvy users.

      Oh, and thanks for the donations :)