-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Own instance not selectable #202
Comments
This is sort of by design because your home instance is the default anyways when no instance is selected. But I suppose it would help avoid confusion if it did in fact show up when you search for it. Let me see what I can do about this. |
have i misunderstood the search? i thought i could use it to filter for moderations per instance? |
Ah, I see. The value of the instance box defines which server the modlog is fetched from. In the original issue (#195), I noted that it appears that some modlog entries propagate to other servers, while others do not. The point of adding this box was basically to allow users to check other servers for their version of the modlog without having to leave Photon. Honestly, this whole thing was really just a quick proof-of-concept I hacked together, didn't expect it to get merged so fast. |
So anyways, I guess opens up an interesting conundrum, because your expectation certainly isn't wrong, and it's difficult to explain to the end user what the difference is between a mod action being taken on a specific server and that action appearing on a given server's modlog. TBH, I'm pretty new to Lemmy myself and I don't know exactly how this happens myself, if anyone can point me to the relevant docs, that would be great. All I've been able to ascertain by experimentation is what I said earlier — there isn't a single, globally unique version of the modlog but instead, every instance has its own version. And sometimes that includes actions taken on other servers, and other times it doesn't. |
In the end, you can see all moderative actions in the log that are known to the server. |
Correct. |
Perhaps we should remove the instance search as you can just change your guest instance URL if you want to see a different modlog |
Well, I certainly didn't intend for my first draft at this to get merged so quickly, so I wouldn't be upset if you do remove it. However, I think there's been some good feedback here and I think there could be an improvement made over using the guest instance, because that takes several extra clicks to change. |
I do have to admit that on second thought, I certainly helped contribute to @Tealk's confusion because the instance autoselectbox is clearly labeled "filter by instance". So I really can't blame him for his expectation here. |
I guess the question would be what happens when you click on a non-Lemmy server. It looks like the Mastodon API does have a similar endpoint to Lemmy's |
Is it not possible to design the filter so that it filters according to the moderator? |
@Tealk I believe that's already implemented, but according to what I'm seeing in the code, that option only shows up if you are an admin on your current instance. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce (if applicable)
Steps to reproduce the behavior:
Expected behavior
only the logs of your own instance are displayed when you search for them
Screenshots
Versions
The text was updated successfully, but these errors were encountered: