Restore List Management from Profile and Fix Holos Account Search #213
Labels
No labels
bug
contribution welcome
duplicate
enhancement
later
not planned
out of scope
question
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
tom79/Holos-App#213
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I would like to report a feature request along with what appears to be a bug.
When I receive a notification that a Holos user has followed me, I often choose to follow them back immediately. At that point, I would like to be able to add their profile directly to one of my lists from their profile page.
If I remember correctly, this functionality was available in an earlier version of Holos, but it seems to be missing from the current release v1.11. The only workaround now is to open the Lists menu and manually add the contact to the appropriate list.
However, this leads to a second issue: when I search for that Holos account in the Lists section, no results are returned. By contrast, searching for any other Mastodon account works as expected.
Could you please consider:
Restoring the ability to add a profile to a list directly from its profile page.
Fixing the search function in the Lists section so that Holos accounts are found correctly.
Thank you for your excellent work and for considering this request.
A few versions ago, Holos had an issue: users were able to add an account they do not follow into a list. But this is not possible, because the follow action is needed to receive the pushed content from other accounts. When a follow request is sent, I added the ability to add an account into a list (though no content is received until the request is accepted).
I also found a separate bug in the list "Add members" search: typing the full handle (user@domain) or a leading @ returned nothing. That is now fixed.