Log in to an account on a GoToSocial instance

Oct 13, 2025 by recoveryshake.com 15 views

Cannot Add Content Filters for a GoToSocial Instance: A Critical Bug in Pachli

Introduction In the world of social media, content filters play a crucial role in managing and organizing the vast amount of information we encounter daily. However, a critical bug in Pachli, a popular client for GoToSocial, has been identified, preventing users from adding new content filters. This article delves into the details of the bug, its reproduction steps, and the expected behavior, providing valuable insights for developers and users alike.

Describe the Bug Adding a new content filter fails with an error, rendering the feature unusable. This bug has significant implications for users who rely on content filters to streamline their social media experience.

To Reproduce To replicate the issue, follow these steps:

Log in to an account on a GoToSocial instance: Start by logging in to your account on a GoToSocial instance. This will ensure that you have access to the necessary features and settings.
Click on the avatar: Once logged in, click on your avatar to access the profile settings.
Select 'Profile settings': From the dropdown menu, select 'Profile settings' to access the account settings.
Select 'Content filters': Within the profile settings, select 'Content filters' to access the content filter settings.
Set a name and add a keyword: In the content filter settings, set a name for the filter and add a keyword to define the filter's criteria.
Click save: After setting up the filter, click the 'Save' button to apply the changes.
See the error: Unfortunately, the filter will not be saved, and an error message will be displayed, indicating that the operation failed.

Expected Behavior The expected behavior is that users should be able to manage content filters with Pachli, allowing them to create, edit, and delete filters as needed. This feature is essential for users who rely on content filters to organize their social media experience.

Screenshots or Video A screenshot of the error message is provided below:

Links As described in the GitHub issue https://github.com/tuskyapp/Tusky/issues/4499#issuecomment-2153302759, Pachli fails because it tries the Filters v2 API and fails, but GoToSocial only supports Filters v1 at the moment.

Versions The versions of Pachli and GoToSocial used to reproduce the issue are:

Pachli 2.10.1: The version of Pachli used to reproduce the issue.
Device: A realme RMX2155 Android device with Android-Version 12 and SDK-Level 31.
Account: The account used to reproduce the issue is @irgndsondepp@gts.da-miez.de, with version 0.18.2+git-602d235.

Additional Context No additional context is available for this issue.

Affirmation I have checked other issues for this project (open and closed) and cannot find one that matches the problem I am reporting.

Conclusion The inability to add content filters for a GoToSocial instance is a critical bug that affects users who rely on this feature. By understanding the reproduction steps and the expected behavior, developers can work towards resolving this issue and providing a seamless experience for users. The provided screenshot and links to relevant GitHub issues offer valuable insights into the issue, and the affirmation ensures that this bug has not been reported previously.
Frequently Asked Questions: Cannot Add Content Filters for a GoToSocial Instance

Introduction In our previous article, we explored the critical bug in Pachli that prevents users from adding new content filters for a GoToSocial instance. In this article, we will address some of the most frequently asked questions related to this issue, providing valuable insights and clarifications for developers and users alike.

Q: What is the cause of the bug? A: The bug is caused by Pachli trying to use the Filters v2 API, which is not supported by GoToSocial. Instead, GoToSocial only supports the Filters v1 API.

Q: Why is this bug significant? A: This bug is significant because it prevents users from managing content filters, which is an essential feature for organizing and streamlining their social media experience.

Q: What are the reproduction steps for this bug? A: The reproduction steps for this bug are as follows:

Log in to an account on a GoToSocial instance.
Click on the avatar.
Select 'Profile settings'.
Select 'Content filters'.
Set a name and add a keyword.
Click save.
See the error.

Q: What is the expected behavior? A: The expected behavior is that users should be able to manage content filters with Pachli, allowing them to create, edit, and delete filters as needed.

Q: What are the versions of Pachli and GoToSocial used to reproduce the issue? A: The versions used to reproduce the issue are:

Pachli 2.10.1
Device: realme RMX2155 Android device with Android-Version 12 and SDK-Level 31
Account: @irgndsondepp@gts.da-miez.de, with version 0.18.2+git-602d235

Q: Is this bug specific to Pachli or can it affect other clients as well? A: This bug is specific to Pachli and may not affect other clients. However, it is essential to verify the behavior with other clients to ensure that the issue is not widespread.

Q: What can be done to resolve this issue? A: To resolve this issue, Pachli developers can modify the code to use the Filters v1 API instead of the Filters v2 API. This will ensure that the content filters feature works as expected.

Q: Are there any workarounds for this issue? A: Unfortunately, there are no workarounds for this issue. The only solution is to modify the Pachli code to use the correct API.

Q: Can I report this issue to the Pachli developers? A: Yes, you can report this issue to the Pachli developers by creating a new issue on the Pachli GitHub repository. This will help the developers to identify and resolve the issue.

Conclusion In this article, we addressed some of the most frequently asked questions related to the critical bug in Pachli that prevents users from adding new content filters for a GoToSocial instance. By understanding the cause, reproduction steps, and expected behavior, developers and users can work towards resolving this issue and providing a seamless experience for users.