Can't get to page 36
-
Seriously guys, ?!
The Dem bones thread. I stopped reading on my phone on the page 35. When I click on 36 I'm being taken to https://what.thedailywtf.com/topic/21042/trigger-warning-dem-bones-dem-bones-dem-dry-bones/701 and it never ends!
First I thought it was my iPhone's fault (Safari, iOS 10, iPhone 6), but then the same thing happened on my desktop with FF 49.0.1.
WTF?
Fake ETA
It got loaded while I was typing this, which means it needed around 2 minutes to work. I know performance issues are hard to track down and crack, but this one is pretty serious, when certain pages of a website take a very long time to load. I know of a forum software that had this kind of problems and those made us abandon it.
-
OK, started reading. Could this be because of 's pathological need for posting thousands of links, which makes oneboxing go awry?
(I mean this post.)
-
@kt_ said in Can't get to page 36:
OK, started reading. Could this be because of 's pathological need for posting thousands of links, which makes oneboxing go awry?
(I mean this post.)
Probably.
-
Maybe the fix could be to make oneboxing optional? I.e. you have to click "onebox this link" to get it to load? Maybe like a user setting? I know this probably sounds like a lot of work, but it renders this site unusable at times.
-
@kt_ said in Can't get to page 36:
Maybe the fix could be to make oneboxing optional? I.e. you have to click "onebox this link" to get it to load? Maybe like a user setting?
I have a feeling that wouldn't help in this case.
-
@ben_lubar said in Can't get to page 36:
@kt_ said in Can't get to page 36:
Maybe the fix could be to make oneboxing optional? I.e. you have to click "onebox this link" to get it to load? Maybe like a user setting?
I have a feeling that wouldn't help in this case.
Do you have a feeling what this could be caused by, exactly? My onebox idea is a shot in the dark.
-
@kt_ said in Can't get to page 36:
@ben_lubar said in Can't get to page 36:
@kt_ said in Can't get to page 36:
Maybe the fix could be to make oneboxing optional? I.e. you have to click "onebox this link" to get it to load? Maybe like a user setting?
I have a feeling that wouldn't help in this case.
Do you have a feeling what this could be caused by, exactly? My onebox idea is a shot in the dark.
What I meant was that would never intentionally turn off oneboxing.
-
@ben_lubar said in Can't get to page 36:
@kt_ said in Can't get to page 36:
@ben_lubar said in Can't get to page 36:
@kt_ said in Can't get to page 36:
Maybe the fix could be to make oneboxing optional? I.e. you have to click "onebox this link" to get it to load? Maybe like a user setting?
I have a feeling that wouldn't help in this case.
Do you have a feeling what this could be caused by, exactly? My onebox idea is a shot in the dark.
What I meant was that would never intentionally turn off oneboxing.
I meant that we could protect ourselves from 's oneboxing efforts. Like turning onebox off by default and only oneboxing what we want by explicitly clicking "please onebox this for me, I'm not afraid, I know how to deal with furries".
-
@kt_ iframely runs without knowledge of who's requesting the post, so that wouldn't work.
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
-
@ben_lubar said in Can't get to page 36:
@kt_ iframely runs without knowledge of who's requesting the post, so that wouldn't work.
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
This sounds awesome, if it's possible. I'd be thankful for that. :)
-
@ben_lubar said in Can't get to page 36:
@kt_ iframely runs without knowledge of who's requesting the post, so that wouldn't work.
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
Maybe make iFramely box in a highly standard way that's consistently sized with a nice little "Click to expand" icon to load the real iFramely-generated content on demand?
That could be a potential solution to solving jellypotato without completely disabling iFramely.
-
Firefox 22
-
@bb36e said in Can't get to page 36:
Firefox 22
Yes, I believe my theoretical solution could support even Firefox 22.
Edit: Me, My, it's all the same, right?
-
@kt_ said in Can't get to page 36:
Maybe the fix could be to make
oneboxing@Fox optional?I feel like some people should have their posts marked as opt-in.
Filed under: and I do realize I'm on the list
-
Can you get page 37?
-
-
@Maciejasjmj said in Can't get to page 36:
@kt_ said in Can't get to page 36:
Maybe the fix could be to make
oneboxing@Fox optional?I feel like some people should have their posts marked as opt-in.
Filed under: and I do realize I'm on the list
Well, I think only in the lounge in one thread some people would be happy with that. :]
-
@ben_lubar said in Can't get to page 36:
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
That sounds like a jellypotato soup recipe, though.
-
@Onyx said in Can't get to page 36:
@ben_lubar said in Can't get to page 36:
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
That sounds like a jellypotato soup recipe, though.
This would be great, cause recent fixes have decreased the amount of jellypotato and I'm starting to feel abandoned... :(
-
@ben_lubar said in Can't get to page 36:
@kt_ iframely runs without knowledge of who's requesting the post, so that wouldn't work.
I wonder if there's a way to render the post without the iframely stuff and then update it with the iframely stuff when the requests return...
Or it could just cache the iframely stuff and not re-render it every time the post is requested.
I mean, yeah, that means it can be out of date, but is that really better than having it rebake every time someone views it?
-
@anotherusername I'd even go a step farther and just make the rendered version of any URL grabbed by iframely saved in the database once it's grabbed for the first time.
-
@ben_lubar that's really what I meant by "cached", although I'd expect it to rebake if the post gets edited, and/or if a mod/administrator can explicitly request a rebake.
-
@anotherusername what currently happens is NodeBB caches the contents of the last 1MiB of posts requested in the last hour. There's no iframely caching in the plugin, although I think the iframely server has a LRU cache as well.
-
@Tsaukpaetra said in Can't get to page 36:
Maybe make iFramely box in a highly standard way that's consistently sized with a nice little "Click to expand" icon to load the real iFramely-generated content on demand?
Twoboxing?
-
@ben_lubar said in Can't get to page 36:
the last 1MiB of posts requested in the last hour
So… large enough to handle a test site but not large enough for a production site?
-
@ben_lubar said in Can't get to page 36:
last 1MiB of posts requested in the last hour
So what happens if a single request is 1.1MiB?