If you’re talking about the Pi-hole thread, that’s because I posted there several days ago after doing some troubleshooting on my device. It seemed relevant at the time, but was really just me unwinding after a long day; when I re-read it the next morning it was obvious blather so I deleted the whole post. So the thread really was updated recently, it just didn’t look like it because I deleted the post that pushed it up in the topics list.
If you’re seeing the same thing on other threads, then that wasn’t me.
I’ve been seeing this happening very frequently on mobile Chrome. It usually clears up if I swipe down to refresh the page, but not always. I don’t think I’ve seen it on a PC browser so far, and at least one of my PC locations has absolutely horrible bandwidth available compared to either the mobile or wifi bandwidth usually available to my phone when I see it.
There’s an update available for Discourse. I was going to take care of it last night, but then looked at the time and realized that the chances of me falling asleep while waiting for it to complete were high enough that I should wait. I’ll try to tackle it tonight if I can.
I don’t know if this is a Discourse issue or a browser bork (stock Samsung browser, a Chromium mod on a Tab S4), but I’m noticing this on the address bar:
I have no idea whether that’s serious or just an “idiot light,” but I thought I’d mention it in case something needs tweaking.
I suspect it’s Yet Another Discourse Glitch because I first noticed it on TOS, and they’ve had multiple glitches today. (Now I get to go report it over there…)
Edited to add: I don’t see the same thing over at meta.discourse.org, which is weird. So I’m confused.
2nd edit: it’s intermittent, not constant, so maybe it’s a connection issue on my end. I have a second device streaming video, maybe it’s a bandwidth issue?
However it is true that if anyone EMBEDS something that starts with http:// to a post, that’ll cause the dreaded “mixed content”. Simply linking to a non-https webpage won’t do it. You’d want to figure out which post is doing that.
while in theory a malicious ISP could mess with embedded HTTP content on a page you view, it’s not a major concern.
because embeds are served up direct from third party servers, there’s no way to force those servers to serve https.
(Really surprised that any websotes are swerving http at all in 2021, since Apache defaulted to https since like 2014. extreme beancounting? or sheer incompetence? dunno which explanation is worse.(
You’d think Discourse would be smart enough to try to convert embedded http links to https. ¯\_(ツ)_/¯
I mean it does all kinds of other stuff behind your back like surreptitiously slurping other content into its CDN, and other link kinds of link manipulation already.
Doesn’t the Other Place convert all Amazon links in posts to affiliate links as a revenue stream?
I could have sworn the Amazon affiliate thing was done in JavaScript client-side because movabletype doesn’t have proper pre-processing parsing support. But there’s also a Discourse plugin available that does the affiliate link morphing serverside at time of topic request by a visitior…
It doesn’t surprise me that some websites are still http. Up until a few years ago, you had to pay extra for an SSL certificate, it was extra complexity, you had to keep renewing it, it was said to slow down your servers, etc. Times have changed, all of that’s in the past, but a lot of old sites are still running. I use HTTPS Everywhere extension but still hit an http site or two per day. Mostly old ones that just haven’t needed updating.
Who here was not previously aware that Canada had secretly invaded Elsewhere?
Explanation: I absentmindedly came here while in Private mode, so I wasn’t automatically logged in, and discovered a bevy of recent threads created by @newsfeed_bot, all tagged Canadaland-podcast. These are readily accessible when I’m not logged in, but hidden away when I’m logged in. I can still find them if I specifically search for them, so the bot isn’t ignoring me. What gives?
Interesting, it appears to be default muted (at least it’s muted for me in Preferences - Notifications - Categories, and I don’t remember muting it). However, mute apparently does not apply to anonymous:
