Site_Feedback

I've never considered this before, but taking a quick look, it does seem possible to do it. It would be just like how the site will (optionally) convert youtube links into inline video (as you mentioned). A twitter status link could be converted to an embedded object that has the tweet displayed nicely in it (clickable, with image/video, etc.)

I'm not sure it will work, but a quick test seemed to show it could. I'll try to see what I can do.

(for testing)

https://twitter.com/NASA/status/101885955575991091...

OK, so I added this. It's under Subscriber options ( https://gametz.com/Subscription.html ) Graphics Options -> Embed Tweets

It's currently off by default. Maybe test it a little, then I could force it on (for subscribers only ...maybe, not even sure that's a great idea). It's like the youtube embed, so it's sub-only. Otherwise, it will just show the status link.

I just noticed, it can mess up the scrolling on the page if you're jumping to a #new (common with the forums here). For example, when I post this, it will jump the page a bit and you don't end up quite where you wanted (the bottom where the text entry box is). I'm not sure I can do much to fix that, the tweet stuff is variable in length and happens after the page load (which is good as you don't want the page to wait for it either).... anyway, it's probably fine... just noticed it.

Awesome! Very cool, thanks @Bill.

Testing:

https://twitter.com/CNET/status/101889673708639846...

Testing with video and GIF...

https://twitter.com/mammamiamovie/status/101392262...

https://twitter.com/Deadspin/status/10188521719059...

Looks like it works awesome. Thanks again!

https://twitter.com/Wario64/status/101887565440482...

Test

Sexcellent. Thanks Bill.

I just saw what you were saying about jumping up the page a bit when you go to NEW in a thread. Not a huge deal, really.

Yeah, this topic is particularly bad because of the quantity.

Now that this is working, you might want to turn it on by default. I have to figure a lot of subs might not see this thread.

Better idea: turn it on if they have YouTube turned on, figuring if they want one kind of embedded content, they'd want both, or vice versa.

Time to make a new topic in the long dormant: http://gametz.com/forum/Announcements forum.

OK, I turned this on for anyone who has youtube video embedding on.

Announcements forum - maybe I should just get rid of it. Also, maybe get rid of FAQ too.

Great addition!

Bill, the links not going to the "#new" anchor locations is still kind of bugging me.

Would something like this help, if it was done after the Twitter stuff loads?

https://stackoverflow.com/questions/22993658/linki...

I had considered it, but I suspect it will just be another pile of problems. I guess I'll give it a shot and see if I can make it better. I agree it's annoying. You can just turn off the embedding too.

I was just looking into this. I'm not finding a simple way to do it. Part of the issue is that it uses a sourced js files from twitter to do the magic. So, that's where the jump code would need to go, but it's not my code. So, that complicates things. I could copy the code to my site and edit it somehow (hard, because it's minified and compacted, really hard to read and understand enough to edit it). Also, if it did change by Twitter, I wouldn't get updated.

It might also be possible to wrap the source insert in a something that does a callback after it loads, but this is also non-trivial as far as I can tell. I feel like this needs to be simple given that it's just for tweets and there's a lot of other more important stuff on the pages here (that could be effected the more complicated this gets).

I'm also concerned about the multiple-tweets on the page case (which is likely when this is most important as the jump gets more and more of the more tweets are shown). Currently, it does the source of the offsite js code for each tweet. I tried to get it down to 1 per page, but it didn't work (not sure why - not great as it shows I don't really get how it's working). But, that also means there would be multiple callbacks to redo the jumping (the original #new jump, then each tweet would do it after it loads). That's worrisome and could easily go badly or be more annoying.

So, yeah, I don't know if this is feasible.