Thread where jerks keep changing the title to something I can't click on
-
Continuing the discussion from About the Look At Me! category:@boomzilla said:
Please respect the OP's ground rules in their topics.
Rules
- Don't look at me
- Don't reply to this thread
-
Screw your rules! Also, screw Thanksgiving!
my Thanksgivings suck. :(
-
my Thanksgivings suck
No kidding, you didn't even thank anything!
Also, I replied to a particular post, not to the thread, so I didn't violate rule #2.
-
Also, I replied to a particular post, not to the thread, so I didn't violate rule #2.
good call! it's fortunate that he didn't say "don't reply in this thread," because then we'd really be up a creek!
-
For the record, this is in response to post 1 of this thread, subverting allegations of betraying rule #2.
Also, I can't see @LB_ at the moment, or even mention @LB_, so @LB_ Must not actually be capable of being seen, and indeed is merely a translation entity for @LB (which also can't be mentioned).None of the rules are on the ground either, so there's that.
-
Also, I replied to a particular post, not to the thread, so I didn't violate rule #2.
Actually, Discourse has topics, not threads.
-
Actually, Discourse has topics, not threads.
Re-read ground rule #2. I'm just obeying the local color.
-
-
And thanks for making a topic title that I can't click on.
-
-
This thread is the only way to make him get a notofication when we talk to him.
-
Protip: Click on the number of replies to access either end of the thread, as opposed to clicking the title which drops you in the middle.
Discoverability. Verring your ability, Discourse-style.
-
And thanks for making a topic title that I can't click on.
Given the rules:
1. Don't look at me
2. Don't reply to this threadA thread title that nobody can click on seemed appropriate.
-
I forgot to mention that it's now 2016, so you should all read rule #2 very carefully.
-
pfft you broke your own rule, that means the rest of us can too.
-
I didn't break any rules. Look even more carefully.
-
Putting exceptions in raw is cheatin' and darn unfair to us well behaved folks.
-
Not reading raw means you are missing out on some of the best humor this site and forum have to offer!
-
Discourse completely strips out the HTML comments, though. They're not in the cooked post at all.
-
Discourse completely strips out the HTML comments, though. They're not in the cooked post at all.
no, but we have a handy dandy button for that.....
-
We added that, and it requires an extra round-trip to the server. For every comment. I'm not scripting that, because I don't want to be blamed for DOSing the server and causing cooties.
-
I was pretty sure that the raw got delivered to the client anyways. Maybe I'm wrong, though...
-
It requires an AJAX call.
-
Damn.
-
@NedFodder you know you can click on the reply count?
-
That takes me to either the first post or the last post, not my next unread post. The un-clickable title fucking breaks the forum, and you assholes need to cut that shit out. </BlakeyMode>
-
I was pretty sure that the raw got delivered to the client anyways.
it can be, @sockbot gets it. but that requires an extra GET parameter
-
@accalia has summoned me, and so I appear.
-
Details?
-
-
The initial page load (new tab / hard refresh) doesn't appear to load the posts by JSON. Or am I wrong about that?
I was thinking about writing a wrapper for
XMLHttpRequest
, but it sounds like I'm still going to need an additional JSON pull sometimes...
-
e initial page load (new tab / hard refresh) doesn't appear to load the posts by JSON.
correct.
I was thinking about writing a wrapper for XMLHttpRequest, but it sounds like I'm still going to need an additional JSON pull sometimes...
yeah, but you could just decide that the first topic (if you reload on a topic) is a crapshoot anyway and say that navigation will sort that out.
preventing the cache from geating more memeory than discourse in a cooties storm might be a different issue too.
-
yeah, but you could just decide that the first topic (if you reload on a topic) is a crapshoot anyway and say that navigation will sort that out.
I do load on a topic when I follow the link from an article.
preventing the cache from geating more memeory than discourse in a cooties storm might be a different issue too.
wat
-
wat
well.... okay nothing is capabble of using more RAM than discourse in a cooties storm, you run out of RAM on your computer first.
-
I guess I haven't noticed that. Discourse uses so much RAM anyway...
-
I think you'll find that “memeory” is storage for infectious ideas.
-
-
Okay, so I've got this...
window.eval(`{ let old_XMLHttpRequest = XMLHttpRequest; XMLHttpRequest = function XMLHttpRequest() { var req = new old_XMLHttpRequest(); var old_open = req.open; req.open = function open(...p) { if (typeof p[1] == "string" && /\\/t\\/.*\\.json($|[?#])/.test(p[1])) p[1] += "&?"[+!~p[1].indexOf("?")] + "include_raw=1"; return old_open.apply(req, p); }; return req; }; }`);
That adds
include_raw=1
to the JSON requests for a topic's posts.Now, if I could just figure out where that information is stored once it's fetched...
-
I'm guessing you need to reopen the Post model and add somewhere to store the incoming information about the raw, and then reopen the Post view, add an observer pointed to the model to detect when a raw becomes available, and stash it "somewhere" that an eventual event handler can get to.
Of course, that could all just be gibberish. I don't know anything about Ember, but Overflow searches seemed to indicate that'd do the trick.
-
I was thinking more that when Discourse fetches the JSON object, it must put that object somewhere, and if I can find it, I don't have to try to make a copy of it first.
-
-
WAT
-
-
Obviously. I just don't know how on the topic list page the one word appeared after the unread post count. I'm sure.
-
-
It's the new Likes thread, only we're trying to see how many times we can change the
subjecttopic title.
-
combined with Left-to-Right and Right-to-Left shenanigans.
-
I assumed it had to be related to that, but wasn't clear how it could cause that fuckuppery. But was too lazy to go look.
-
When in the topic, the words show in a different order depending on whether the title is in the header or not
Neither of these are the same order it shows on the topic list.
-
I was wondering what was going on with the title....