Spyke
Admiral Patrick
dubvee.org

TL;DR: I think it's a bug in how v1.4.41 handles admin-hidden communities. You should be able to just click the "Eye" button to reveal the post, but I doubt I'll fix it on the 1.4.41 version since 1.5 is close to release.

If you click the "eye" button to reveal it, what community is it?

Could be one of the following:

  1. You could have intentionally or unintentionally filtered the community in the Tesseract settings.
  2. It could be a bug for how it handles communities hidden by the admins

For the first, go to Settings -> Filtering and see if any are listed in the communities section.

For the latter, I'd need to know if the community is hidden by the admins to see if it is a bug in the way those are handled.

(I'm the Tesseract dev)

The current release version is pretty far behind the dev branch I use daily, and I've completely rewrote how those filters work, but I tried #1 on the old version and it shows a different message:

Which makes me think it must be a bug in how admin-hidden communities are handled. If you can let me know what community that is, and confirm if it's admin-hidden, that would be helpful.

As I said, I've completely re-written the way the filters work in v1.5 so I'll have to add a check so that hidden communities aren't set with the filter flag if you're subscribed to them (which I think is how the API handles it).

I just checked the filter processing code on the 1.5 dev branch, and it doesn't trigger on hidden communities at all, so if that is the case, it should be fixed in the upcoming version.

4
yumanreply
programming.dev

thanks for the reply. filtered is empty and the community is ![email protected]

this is how it shows in the sidebar (subscribed). went through all options and nowhere is it listed as blocked/silenced/whatever.

yes, clicking "show" reveals the post.

2
Admiral Patrickreply
dubvee.org

Ok, thanks. That red eye slash icon means it's an instance-hidden community so there's no workaround other than clicking the button to show the post. I've confirmed this is a bug in how instance-hidden communities are handled by the filtering options. It's fixed in 1.5 but it's not quite ready to release yet.

2
Zorque
lemmy.world

Are there private communities in the fediverse? It might be that it's set that you have to be invited/subscribed to be able to see it.

1
Admiral Patrickreply
dubvee.org

So it is an admin-hidden community then? If so, that confirms the bug. Should be fixed in the upcoming v1.5. I doubt I'll release a hotfix for this since 1.5 is close to release and improves on 1.4.41 in just about every single way.

Clicking the "eye" button should reveal it to the user, though, like any other item they've filtered.

1
UlrikHDreply
programming.dev

I haven't hidden the community yet and the post is visible both on the standard frontend and the tesseract frontend. Not quite sure what's going on in OP's picture, checking the database, all the recent posts seem normal.

1
Admiral Patrickreply
dubvee.org

Are we sure it's the British Telly community? Unless OP manually revealed that post, then the two hidden ones above may be something else.

Regardless, they can click to reveal it as a workaround, and I still think it's just improperly handling communities marked as hidden since this is the code that seems to be triggered:

https://codeberg.org/tesseract-ui/Tesseract/src/commit/38f215e3ea164efce24cf3bf2d7f4f9ecde99633/src/lib/components/lemmy/post/Post.svelte#L352

// Community Hidden
if (post.community.hidden) {
    hidePostReason = 'Community is hidden'
    return true
}

That's fixed / no longer applicable in (upcoming) 1.5 since I re-wrote the whole filtering subsystem and no longer flag those to be filtered/hidden.

1
UlrikHDreply
programming.dev

c/die_reklame has been set to hidden by an admin due to being a community primarily driven by a bot, but it seems like it wasn't added to the public hidden communities list. That's our mistake, we will update the list to show it as hidden.

Hiding communities isn't something done by moderators, it's something we do at an admin level according to our instance's policy.

2

You reached the end

hidden community? | Spyke