@weskersucks@lemmy.world did you see this?

Good point, I think I misunderstood OPs post

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.

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.

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.

no, British Telly is showing fine, !die_reklame@feddit.org is hidden. I haven't selected "hide bot stuff" anywhere in settings.

thanks for the reply. filtered is empty and the community is !die_reklame@feddit.org

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.

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.

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.

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.

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.

https://programming.dev/c/britishtelly@feddit.uk is currently visible and not hidden.

However, as it seems to be a bot community, it should be hidden on our instance, so we will hide it and update https://legal.programming.dev/docs/hidden-communities to reflect that.

Thanks! Given the response, I'd say good riddance.

This or the discord is probably the best spot atm

Seems like that community was likely handled by an admin already since I can't find it

Great to hear, thanks as always for your hard work on keeping things running well.

The admins who can deal with it are asleep atm, so we'll have to wait for them to wake.

Our messages arent being sent out to other instances i think? I dont really know.

It has been very quiet hasnt it?

https://phiresky.github.io/lemmy-federation-state/site?domain=Programming.dev

Looks like federation is broken, ive raised it with the admins on discord. May take a while to get resolved though.

I'm Coca Cola, but you can call me the fediverse drink!

Farewell Coca Cola enjoyer; we hardly knew ye!

Praise be, thanks!

I actually did try reporting but couldn't, it hence why I did it this way.

They have been banned. If any other accounts do something like this, please report the DM's so that we have visibility.

I just tried https://p.programming.dev/profile/settings and it's effectively the same. The save spinner continues indefinitely (no apparent timeout, unlike the other). A load of the page in a different tab shows no change.

Edit to add:

This time, however, there is a CORS error in the console. But it has a status of 504, so I'm thinking it may not be an actual CORS issue, but rather a backend timeout issue that's presenting via a CORS resource load.

With the attempts on the main interface, it's same domain so no CORS at play. Perhaps it's still a backend timeout issue but there's no error that gets passed up.

does it work on frontends other than the main one? e.g. https://p.programming.dev/