what'd ya do now....no pic in sig for many posters now...

it's important to me to scroll back to find my last post to review subsequent responses

The [twitter] code seems to be having some hiccups as well.

Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

(10-05-2018 02:23 PM)georgia_tech_swagger Wrote:  Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

to translate for us mere simple folk, you're telling me I or others didn't change anything and shite disappeared due to ewe developing your code to gain https:// that is still not fully secure....

ummmmmmmmmmmkayyyyyyyyyyyyyyyy

your response was a condescending joke.....I had programmers under my thumb back in the day....I was their crew chief......

I know your code vs a canned enhancement.....

ewe can't shite the shiTTTer...

(10-05-2018 05:04 PM)stinkfist Wrote:  

(10-05-2018 02:23 PM)georgia_tech_swagger Wrote:  Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

to translate for us mere simple folk, you're telling me I or others didn't change anything and shite disappeared due to ewe developing your code to gain https:// that is still not fully secure....

ummmmmmmmmmmkayyyyyyyyyyyyyyyy

your response was a condescending joke.....I had programmers under my thumb back in the day....I was their crew chief......

I know your code vs a canned enhancement.....

ewe can't shite the shiTTTer...

Whatever. The quick reply doesn't refresh the page ... it redraws it in JavaScript. If you're also doing a Twitter embed this way it isn't going to load when rendering the page again because the Twitter embed wants the full browser request of a full page load for their own analytical (read: marketing and monetization) purposes. That don't get that data on a page redraw in JavaScript. This is before we get into the nasty business of JavaScript framework chaos, which is what I referred to as sadness and suffering. I'm pretty sure there's a new JS framework daily or nearly daily on GitHub. It's ridiculous.

Aint shook by your shiTTTy attitude.

(10-05-2018 08:25 PM)georgia_tech_swagger Wrote:  

(10-05-2018 05:04 PM)stinkfist Wrote:  

(10-05-2018 02:23 PM)georgia_tech_swagger Wrote:  Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

to translate for us mere simple folk, you're telling me I or others didn't change anything and shite disappeared due to ewe developing your code to gain https:// that is still not fully secure....

ummmmmmmmmmmkayyyyyyyyyyyyyyyy

your response was a condescending joke.....I had programmers under my thumb back in the day....I was their crew chief......

I know your code vs a canned enhancement.....

ewe can't shite the shiTTTer...

Whatever. The quick reply doesn't refresh the page ... it redraws it in JavaScript. If you're also doing a Twitter embed this way it isn't going to load when rendering the page again because the Twitter embed wants the full browser request of a full page load for their own analytical (read: marketing and monetization) purposes. That don't get that data on a page redraw in JavaScript. This is before we get into the nasty business of JavaScript framework chaos, which is what I referred to as sadness and suffering. I'm pretty sure there's a new JS framework daily or nearly daily on GitHub. It's ridiculous.

Aint shook by your shiTTTy attitude.

I dunno, man. I'm getting the same results.

(10-05-2018 05:04 PM)stinkfist Wrote:  

(10-05-2018 02:23 PM)georgia_tech_swagger Wrote:  Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

to translate for us mere simple folk, you're telling me I or others didn't change anything and shite disappeared due to ewe developing your code to gain https:// that is still not fully secure....

ummmmmmmmmmmkayyyyyyyyyyyyyyyy

your response was a condescending joke.....I had programmers under my thumb back in the day....I was their crew chief......

I know your code vs a canned enhancement.....

ewe can't shite the shiTTTer...

I think he's right.

you know, I remember -- sometime back -- where GTS intentionally occluded ads with navigational links.

just to farm clicks

(10-05-2018 09:48 PM)EagleX Wrote:  

(10-05-2018 05:04 PM)stinkfist Wrote:  

(10-05-2018 02:23 PM)georgia_tech_swagger Wrote:  Nein. No code on the frontend has changed. The Twitter embed is a bit annoying -- you typically have to refresh to get it to show properly or just load the page again. This is because if you quick reply you're using a ton of Javascript and JS is a universe of sadness and suffering for developers.

No pics in signature .... ehhh do you have a browser plugin strictly enforcing SSL? If people are linking to images in their signatures using http:// ... and the site is now under https:// .... that does generate a quiet warning in the background and still show you the image. But if you turn your browser into paranoia mode it will throw errors for that instead.

to translate for us mere simple folk, you're telling me I or others didn't change anything and shite disappeared due to ewe developing your code to gain https:// that is still not fully secure....

ummmmmmmmmmmkayyyyyyyyyyyyyyyy

your response was a condescending joke.....I had programmers under my thumb back in the day....I was their crew chief......

I know your code vs a canned enhancement.....

ewe can't shite the shiTTTer...

I think he's right.

you know, I remember -- sometime back -- where GTS intentionally occluded ads with navigational links.

just to farm clicks

of course, I have witnesses for what I just said.

(10-05-2018 09:48 PM)EagleX Wrote:  I think he's right.

you know, I remember -- sometime back -- where GTS intentionally occluded ads with navigational links.

just to farm clicks

That was AdSense Responsive Ad Units. Instead of having set sizes Google takes a look at what device the page is being loaded on and automatically adjusts the size of the ad unit. It uses JavaScript to do this. The trouble is it didn't account for the JavaScript menu at the top of the site. So it would place the ad unit underneath it. An annoying bug, not click fraud. And Google would immediately notice click fraud. I still once every 2 months or so get Google reports on old BOTD-ish posts from more than 7 years old. And they even robo-complained about inlaying the ads in the middle of the threads inside boxes with "Advertisement" where the UserID and info would be so it flowed visually better with the threads instead of having big jarring box of empty with one ad centered in it.

You've always had an axe to grind. It's not like I keep you here at gunpoint. Why hang around if I'm such a bad guy?

(10-05-2018 09:57 PM)georgia_tech_swagger Wrote:  

(10-05-2018 09:48 PM)EagleX Wrote:  I think he's right.

you know, I remember -- sometime back -- where GTS intentionally occluded ads with navigational links.

just to farm clicks

That was AdSense Responsive Ad Units. Instead of having set sizes Google takes a look at what device the page is being loaded on and automatically adjusts the size of the ad unit. It uses JavaScript to do this. The trouble is it didn't account for the JavaScript menu at the top of the site. So it would place the ad unit underneath it. An annoying bug, not click fraud. And Google would immediately notice click fraud. I still once every 2 months or so get Google reports on old BOTD-ish posts from more than 7 years old. And they even robo-complained about inlaying the ads in the middle of the threads inside boxes with "Advertisement" where the UserID and info would be so it flowed visually better with the threads instead of having big jarring box of empty with one ad centered in it.

You've always had an axe to grind. It's not like I keep you here at gunpoint. Why hang around if I'm such a bad guy?

awesome. so, "if you don't like my sh*t, then feel free to f*ck off"?

that's an outstanding way to build a board.

warning: parts of this thread are about to disappear

(10-05-2018 10:10 PM)EagleX Wrote:  awesome. so, "if you don't like my sh*t, then feel free to f*ck off"?

that's an outstanding way to build a board.

Play stupid games, win stupid prizes.

(10-05-2018 10:17 PM)EagleX Wrote:  warning: parts of this thread are about to disappear

Nah. Just you.

Geeeeez.

Ya'll talking a foreign language by now for me.

But what do we pay GTS for this site? Likely what I pay.

Zippo. So i get some ads about 50+ dating, or broads in my zipcode that are looking around, maybe a car ad or two?!?

Damn, folks. Dude just tryin to make a dime.

C'mon.

GTS owns this. If one does not like the way he runs it? Leave. Start your own board. Run it like you want.

thank you GTS.....you changed something where life is back to normal

(10-06-2018 10:38 AM)stinkfist Wrote:  thank you GTS.....you changed something where life is back to normal

Nothing changed.

Sent from my ZTE A2017U using Tapatalk