To avoid bump floods every time a source site added or removed a banner, I set threads in RSS Feeds to surpressed by default. What the bot needed was a rewrite but I didn’t want to spend the time doing that.
Didn’t realize suppression only hid it in latest for logged in.
Updated category permissions. Disabling two of the feed sources for now.
EDIT: in classic Jeff fashion, the discourse team removed the setting for supprssing a category’s threads. For archival purposes, the RSS archives can be accessed via Categories - Elsewhere Cafe
I’m still hazy on the purpose of these “secret” threads. Was there a memo that I missed about signing up? Or forgot about? I’m not complaining because I feel left out. I just get the impression that almost everyone was essentially left out (unless they accidentally stumbled across them) and am curious why, if so.
I had an RSS plugin installed in… 2019? to auto-post interesting articles and then I added imports of a podcast, and then at the request of a regular, imports of an NPR column.
this was manageable until the plugin started bumping topics every time the site a RSS feed changed a banner. then it reset the date on topics, bumping thirty or forty past threads in one go.
… so I set the category it posted to as suppressed, meaning it wasn’t supposed to show up in latest, as a stopgap until i could fix the RSS plugin. It still showed up in Categories view.
The RSS plugin settings panel broke in 2020 but by then I was busy IRL. And the settings panel to enable/disable thread suppression was removed in a Discourse update at somepoint that year, too.
There were probably tweaks I could have done to enhance visibility of these Tuesday without intruding on existing topics. There was a neat Blog View plugin that I played with for a personal project that could have worked nicely, with effort.
The board isn’t really my baby. LockeCJ keeps the server paid for and patched. ChickieD handles most of the moderation load. (There were maybe… eight? flags in the entirity of 2020). I kinda just float around and once every two years put together a terribly half-baked solution to problems that usually don’t exist.
I apologize for the confusion. I half-assed enabled a feature and didn’t follow through on it. The community deserves much better than the mess the RSS fiasco is.
EDIT:
I want to be clear that the entire fault of the RSS debacle is mine. Code isn’t a one-off you send into the world. It requires ongoing commitment to keep running. And I did not commit.
hey! sorry for the late reply – I swear I occasionally read the site.
Readability is definitely something I want to address in the near future with some theme updates. If I can track down my Kindle, I’ll have a much easier time testing changes. Thank you so much for bringing this to my attention.
It occurs to me I’ve kinda just accepted this as a glitch and got used to it and now it’s been a long time (over a year). Everything else seems to show up fine in onebox mode, but twitter oneboxes are always broken. I have to click through to see it. Does anyone else see it like this?
Fair enough - I hadn’t tried different browsers and extension settings etc. I suppose I should. Aaand, it works just fine on Chrome. So I tried turning off all my extensions in Firefox one by one and that doesn’t appear to make a difference.
Possibly a Firefox-specific bug? Or maybe something else in my settings.
I have that too, though in my case I think it’s my browser not playing well with Discourse. Still images may or may not show up in Twitter oneboxes, videos never do. (This also happens at TOS.) I typically use Samsung Browser (a Chromium mod); if I go to Chrome I have better results… but I’m not too fond of Chrome, so I usually put up with the extra clicks.
I’d be tempted to try a new mobile browser if it allows extensions, as Android Chrome won’t use them at all and Samsung’s support seems limited at best. I’m still doing research on that one.
Edit to add: Firefox mobile doesn’t give me many options either, at least few I’m interested in, and AFAIK I don’t think regular Firefox extensions are compatible. >sigh< Guess tablet-users are second-class citizens in the digital world.
weirdly, couldn’t replicate on Edge and Brave, so I’m guessing it might be something specific to a combinations of browser addons.
android phones older than 4 years old using the default browser may experience issues, since Discourse is a “rolling release” that targets only the newest browsers for compatibility.
I think these image zooms are done via CSS-transitions. My apologies for the delay; it has been awfully busy at work, but I will get right on fixing this.
Is there a particular image/message link that displays this unwanted zooming behaviour?
I think it’s possible to override the zoom transition by patching the site themes, which is relatively straightforward.
