The Official Status Thread
-
@Tsaukpaetra said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
Only if you upload wrongly.
I uploaded it into a different thread.
Rather than re-upload it, I just copy/pasta'd the image url.
Since it's an URL to an image, that normally oneboxes.
NODEBB!
Did you include the full URL or just from /uploads ?
Asking for a user.That sounds like something a developer would want to know, and we know developers aren't users, so I believe you are a liar!
!for @Tsaukpaetra
-
@Fox
Just because singular they gets used, doesn't make it correct (to channelparents: "if all your friends jumped off a bridge, would you?"). I'm from the era where we were taught in school that you just use he as the default, and nobody's panties got in a bunch over it. I can even deal with the s/he format of modern English. But for some reason, "they" just drives me crazy.
-
@izzion said in The Official Status Thread:
you just use he as the default, and nobody's panties got in a bunch
Obviously, because no males ever spoke about females like we do nowadays.
-
-
@Tsaukpaetra said in The Official Status Thread:
Did you include the full URL or just from /uploads ?
Asking for a user.Full url.
-
@Lorne-Kates said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
Did you include the full URL or just from /uploads ?
Asking for a user.Full url.
Interesting. Lemme try:
I smell a regex error...
-
Status: Holy crap, are you going 'cross state for lunch?!
-
Status: USPS tracking is effectively useless. Why the fuck even bother if you are going to handle tracking so poorly? Their tracking site should just rickroll you or give you the middle finger when you try to track a package.
-
This post is deleted!
-
@Polygeekery said in The Official Status Thread:
Status: USPS tracking is effectively useless. Why the fuck even bother if you are going to handle tracking so poorly? Their tracking site should just rickroll you or give you the middle finger when you try to track a package.
My favorite is how I'll get links for tracking. From podunk bumfuck websites, all the way up to Ebay.
"Your package has been shipped. You can track your package online using our tracking site. Your tracking number is 6969LOLPOOP."
The URL is of course http://ups.com/track?id=6969LOLPOOP
The URL, of course, does not work when clicked on. I'll either get a "tracking number invalid" error, or the site will shit itself, error out, and go to the home page.
If I click on "track" and copy/paste the tracking number, I get the information.
For bonus nut-shots, after copy/pasting and clicking GO I end up on http://ups.com/track?id=6969LOLPOOP -- THE EXACT SAME FUCKING URL THAT I CLICKED ON.
This isn't an isolated incident. Every goddamn time I get a "your product has shipped" email. So it's not like it's just an isolated "oops the API is down for maintenace" bug. It's every goddamn time.
And it's not like it's "this shitty site doesn't know how to implement the API"-- it's every goddamn site. And for all it's faults, I think Ebay would know how to implement an API.
Fuck shipping companies. Fuck Canada Post. Fuck USPS. Fuck your package (gigg...)
-
@Lorne-Kates I always bypass their bullshit, highlight the tracking number, right-click, "Search with Google". Even Amazon fucks it up, because for services with functional tracking (UPS and FedEx, DHL is a shithole) they don't display the most recent tracking information. They give the tracking information they last received on their scrape or data dump or whatever.
-
@Lorne-Kates said in The Official Status Thread:
Since it's an URL to an image, that normally oneboxes.
Yes, we blacklisted ourselves because we were DoSing ourselves.
-
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Since it's an URL to an image, that normally oneboxes.
Yes, we blacklisted ourselves because we were DoSing ourselves.
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
-
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
-
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
It was oneboxing a page where someone linked to a post that was on the same page. So it would load the page to check if it could onebox it and that would trigger the page to generate again and call out to onebox again and so on and so forth.
-
@ben_lubar said in The Official Status Thread:
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
It was oneboxing a page where someone linked to a post that was on the same page. So it would load the page to check if it could onebox it and that would trigger the page to generate again and call out to onebox again and so on and so forth.
why is oneboxing recursive? shouldn't it know not to onebox when it's rendering content for a onebox?
-
@accalia said in The Official Status Thread:
@ben_lubar said in The Official Status Thread:
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
It was oneboxing a page where someone linked to a post that was on the same page. So it would load the page to check if it could onebox it and that would trigger the page to generate again and call out to onebox again and so on and so forth.
why is oneboxing recursive? shouldn't it know not to onebox when it's rendering content for a onebox?
nodebb-plugin-iframely doesn't have any way of knowing it's rendering a post for a different server's iframely request.
-
@accalia said in The Official Status Thread:
@ben_lubar said in The Official Status Thread:
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
It was oneboxing a page where someone linked to a post that was on the same page. So it would load the page to check if it could onebox it and that would trigger the page to generate again and call out to onebox again and so on and so forth.
why is oneboxing recursive? shouldn't it know not to onebox when it's rendering content for a onebox?
The site apparently doesn't know it's being oneboxed. So, on initial load, the onebox plugin will process.
Edit:
'd
-
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments
What's a page?
-
@Maciejasjmj said in The Official Status Thread:
mashing the suggested word button on my keyboard.
I thought that was how you got your username.
-
@ben_lubar said in The Official Status Thread:
@accalia said in The Official Status Thread:
@ben_lubar said in The Official Status Thread:
@boomzilla said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
Didn't certain people have multi-page arguments with a certain rat when he pointed out that oneboxing was a DoS, and certain people insisted he was wrong, even though he was 100% correct?
Yeah, that fucker kept telling me how I was wrong. What a little bitch.
I think iFramely (this was before something had to be on a line by itself) was trying to onebox literally every single link. And sometimes it got stuck into an infinite loop or something. Whatever the details, it was literally denying trolling service to TDWTF.
@ben_lubar will remember the details better.
It was oneboxing a page where someone linked to a post that was on the same page. So it would load the page to check if it could onebox it and that would trigger the page to generate again and call out to onebox again and so on and so forth.
why is oneboxing recursive? shouldn't it know not to onebox when it's rendering content for a onebox?
nodebb-plugin-iframely doesn't have any way of knowing it's rendering a post for a different server's iframely request.
it really shouldn't onebox FULL STOP when rendering a request that is a onebox request.
-
@accalia said in The Official Status Thread:
it really shouldn't onebox FULL STOP when rendering a request that is a onebox request.
PRs probably accepted.
-
Status: they should really stop encouraging those who mummify their hands...
-
@accalia said in The Official Status Thread:
it really shouldn't onebox FULL STOP when rendering a request that is a onebox request.
Or at least keep a stack. If it's about to DumbBox something, and the DumbBoxStack contains that link already, don't DumbBox. Otherwise, add to the stack and DumbBox.
-
status: just learned that I will have to fix some expensive bugs - the six-legged, crawl in your bed and nibble on you as you sleep kind. Fortunately, we caught the infestation early, so I shouldn't need to get rid of my (new as of six months ago, and rather nice) bed, but the treatment will cost upwards of $375.
-
@Tsaukpaetra said in The Official Status Thread:
Typically the main reason I use their/they/themself is because I don't know their preferred gender they have have assigned themself.
Isn't that plural? You could use "it"
-
@Mikael_Svahnberg said in The Official Status Thread:
You know the medicine blister packs? Well someone ought to invent one of those and fill it with a sufficient amount of toothfairy tokens for one kid. We never manage to have any coins at home when needed.
My son got a book where the boy gets money for losing his teeth. Not just two coins, but two shiny coins. Thanks a lot, author!
-
@coldandtired said in The Official Status Thread:
Not just two coins, but two shiny coins. Thanks a lot, author!
Get yourself some of those new 1gr coins. Baking soda and vinegar are good for giving them even more shine, I think.
-
@groo said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
Typically the main reason I use their/they/themself is because I don't know their preferred gender they have have assigned themself.
Isn't that plural? You could use "it"
Social connotation of intentional disregard for preferred gender. I.e.::
I talked to @groo today. It doesn't seem to understand where I'm coming from.
-
@Maciejasjmj It's okay. He hasn't noticed I've been stealing them back and giving them to him again the next time.
-
@Lorne-Kates said in The Official Status Thread:
Or at least keep a stack.
Have fun implementing that in stateless HTTP.
-
@ben_lubar said in The Official Status Thread:
Have fun implementing that in stateless HTTP.
Javascript-- or whatever framework is doing "replace hyperlink with text" isn't stateless.
It knows the hyperlink it is replacing.
It knows the content it is getting back.
It knows that if the content contains further hyperlinks to replace, to call into DumbBox again.
:/
-
@Lorne-Kates iframely works by doing a normal HTTP GET request and then parsing the response. If there's some way to parse the response without having the remote server process it first, let me know.
And no, you can't just look at the user agent because NodeBB caches cooked posts and the user requesting the post isn't part of the data given to the post parser.
-
@ben_lubar maybe add a parameter to the URL query string?
-
@groo I have no access to any part of the request in the post cooking code.
-
Status: Um, Outlook, why do some of my OLE Objects get a different icon?
-
Status: fsck frick flap fraps fricken!
I know I submitted that in the form, it shouldn't be null, so why...
Thanks, MVC controller, for reminding me I need to add that in.
now, as to why that column exists or is needed at all... Well that's another
, because it's not used one iota.
What's weird is that, in Dev and Test (when debugging is enabled), the lack of binding attribute thing doesn't phase the site at all!
So, Binding missing attributes doesn't fail in debug mode, just in production mode.
TDEMSYR.
-
@ben_lubar said in The Official Status Thread:
@Lorne-Kates iframely works by doing a normal HTTP GET request and then parsing the response. If there's some way to parse the response without having the remote server process it first, let me know.
I must be missing something.
- iFramely sees a link to wtdwtf
- iFramely makes the GET request
- iFramely gets the content
- iFramely does a string.replace-- taking out hyperlink and injecting the content
- iFramely sees a hyperlink in the content that points to wtdwtf
- So since it the content contains wtdwtf hyperlink, it goes back to #2, recursively
So the last step should pass the stack into step #2.
HTTP requests don't just happen. Something has to kick them off and handle the result.
-
@Lorne-Kates it's more like
- NodeBB begins to render the page
- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
And so on.
-
@ben_lubar said in The Official Status Thread:
@Lorne-Kates it's more like
- NodeBB begins to render the page
- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
0. NodeBB begins to render the page- iFramely sees a link to wtdwtf
- iFramely makes the GET request
And so on.
Exactly. It's recursive. You should be able to do state-tracking between those recursions.
-
@Polygeekery said in The Official Status Thread:
@groo said in The Official Status Thread:
You know the things I argue in the forum rarely reflect my opinion, right?
It is hard to tell what your real opinions are, you delete them so quickly.
Wtf groo is fbmac??
-
@Lorne-Kates said in The Official Status Thread:
You should be able to do state-tracking between those recursions.
Should, but then again, NodeBB isn't aware that it's recursing, and iFramely ain't sharing none of that!
-
@bb36e said in The Official Status Thread:
@Polygeekery said in The Official Status Thread:
@groo said in The Official Status Thread:
You know the things I argue in the forum rarely reflect my opinion, right?
It is hard to tell what your real opinions are, you delete them so quickly.
Wtf groo is fbmac??
I see you're catching up on TDWTF News.
-
@Tsaukpaetra I feel like I'm in a soap opera
😱
-
@ben_lubar replace the link to wtwtd?wtf=1 before passing it to iframely
-
@Tsaukpaetra said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
You should be able to do state-tracking between those recursions.
Should, but then again, NodeBB isn't aware that it's recursing, and iFramely ain't sharing none of that!
The iFramely should just maintain a stack and not request anything it's already requested.
-
@Lorne-Kates said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
You should be able to do state-tracking between those recursions.
Should, but then again, NodeBB isn't aware that it's recursing, and iFramely ain't sharing none of that!
The iFramely should just maintain a stack and not request anything it's already requested.
If it did that, would it wait for the first request to finish or just fail any further requests right away?
If it waits, any forum thread that links to itself will never successfully load and the requests will stay in memory forever and the server will crash.
If it fails immediately, the post cache contains nothing but errors due to multiple users viewing the same topics at the same time and failing immediately is faster than an actual request succeeding.
-
@Lorne-Kates said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
You should be able to do state-tracking between those recursions.
Should, but then again, NodeBB isn't aware that it's recursing, and iFramely ain't sharing none of that!
The iFramely should just maintain a stack and not request anything it's already requested.
That assumes that iFramely can maintain a global state (outside the request), because each request = new state.
-
Status: just used Thunderbird to archive emails from my college account into my gmail account by dragging them all into the All Mail folder. On gmail's side, the emails can be found by searching but don't appear in All Mail. I'm not sure what the point of All Mail is if it doesn't show ALL MAIL. Oh well, at least it worked to the point that they can be searched, and that's all I really care about.
-
@LB_ said in The Official Status Thread:
On gmail's side, the emails can be found by searching but don't appear in All Mail
Wait what? So, you took stuff from a non-gmail account and moved them into gmail's All Mail pseudo-folder?