The Fediverse is just full of Carols (on the right/brown coat):
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.
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:
// 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.
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:
- You could have intentionally or unintentionally filtered the community in the Tesseract settings.
- 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.
In a sane world, this would be a "You've won a free boat! Claim your prize at the police station" trap, but such is not the world we're living in.
What do you want to practice? Just general sysadmin stuff? Networking? Clustering? Horizontal scaling? All of the above?
Old PCs are just Debian servers waiting to happen. Depending on their specs, you may be able to do VMs or you can utilize container frameworks like Podman, Docker, or LXC to deploy individual applications or application stacks. Or you can just bare metal install anything you want.
Years ago, I bought a batch of 16 Wyse thin clients on eBay for about $15/each. These had 4GB SSDs and 2 GB RAM, so I upgraded about half of them with 64-120GB SSDs (whatever I had lying around) and 8 GB RAM. Thin clients can usually be found pretty inexpensively and are pretty power efficient, but they're not performant workhorses. They're great for practicing networking, VLANs, system orchestration (e.g. Ansible, Cockpit) application clustering and horizontal scaling, diskless workstations, setting up a demo office server and workstations, and even VMs if you're just practicing; they're a little underpowered to run a lot of VMs, but you can certainly run a few small ones just to practice managing them.
Removing under rule 6. Please feel free to resubmit, but be sure to include an explanation in the post body as to why you hold the opinion and why it is unpopular.
Per rule 6, please explain in the post body why you hold this opinion and why it's unpopular.
There's a safety sensor that tells the unit whether it's okay to stay lit
That'd be the thermocouple. I haven't replaced one in a recent water heater, but have done them in gas stoves and furnaces without too much fuss. OP said their water heater is in a cramped space, so may be better for them to just plan to replace it since they'd probably need to disconnect it to be able to work on it at all. Replaced mine in February for about $650 including delivery and new fittings.
FYI: The little blinking light and control box is self-powered. There's a thermocouple inside that generates a small amount of electricity when heat is applied, and that heat comes from the pilot light. When re-lighting, you have to hold the button in for a few tens of seconds after it catches to give it time to heat up or else it will shut the gas off. It's a safety feature so it's not leaking gas when there's no flame.
Could have been corrosion in that small connector due to humidity or other moisture and reseating it cleared enough to get it back working again.
My water heater crapped out a few months ago and had to replace it, and it's probably exactly the same one you're describing.
47
I'm the Tesseract dev, and in the current build, any posts that aren't your own that have [spoiler] (case-insensitive) in the post title will hide all but the post's metadata (title, author, community, etc) and the vote/comment bar. Clicking "reveal" shows the post's contents.
The nitty-gritty implementation details are up to you, but can we, as a group, please come together and handle this flair consistently? I would really love to be able to disable the "Show NSFW" option without missing totally safe-for-work posts due to people abusing the NSFW attribute. I get why people do that, but I'm also tired of playing "porn or spoiler" roulette.
I haven't added this part yet, but I'm planning to put a "Spoiler" toggle on the create post form which will add [Spoiler] to the post title during the submission if the user didn't add it manually.
Or if other apps I'm not familiar with are already doing something like this, let's do that. Either way, let's get on the same page.
Edit: If there are any other special-case flairs that might be handled similarly, I'm all ears.
view more: next ›
Per rule 6: In the post body, please explain why you hold this opinion and why it is unpopular.
Also: you're