iframes on my blog a no-no?

[Trixie]

I'm working on making http://trixie.com/ useful by using an aggregator to syndicate my own blog posts there and having a small tgp-like thing in one column.

Out of sheer laziness and ignorance, I used an iframe for the tgp section because I wanted to hurry up and get it working; my question is, what's with the opposition to iframes? I am not hotlinking someone else's content, only my own (the tgp is on one of my other domains). What possible problems could I run into by leaving it in the iframe?

Any thoughts on that or anything else you observe there? I am still working on the site, so any feedback is greatly appreciated.

[T Pat]

The only two things I have against Iframes are:
1, a lot of the cheaters used them to do sneaky shit
2, they are of no value for gaining search engine listings
But it's your blog so I can't think of a reason why anyone would have a problem with it

[Trixie]

Thanks for your response. I guess my concern is whether or not people will trade traffic with me based on that. Although I don't anticipate doing a ton of link exchanges, I also don't want to make it impossible to do so if the iframe breaks everybody's rules.

I guess I just need to figure out how to get TGP rotator to post directly onto a sidebar widget.

[Useless]

I don't think the Iframe should or could be a problem. It's not any different than embedding any other outside content on to your page. Well, it is different in that SEs can read and follow the content within an Iframe. Also, it's your own content that you are including. By comparison, people/sponsors who produce RSS feeds can pull some tricks, but everyone trusts RSS implicitly.

You shouldn't have difficulty finding trading partners. It's a high quality blog with many, many well-written posts which had to require a lot of time and thought. There are very few adult blogs which are that text rich. Most of them are RSS-fed splogs with zero original content.

If anything, those gallery thumbs are doing you a favor by allowing you to capitalize on SE traffic that doesn't want to read a blog.

[Thumbler]

If you're concerned with an iframe, why not just use an include instead?

[Trixie]

Originally Posted by Thumbler

If you're concerned with an iframe, why not just use an include instead?

I haven't learned how - I'm not even sure I know what that is. Do you mean a server side include?

That's what I'm saying -- the iFrame was the easiest thing for me to do right away without figuring out something new (to me).

[Trixie]

Originally Posted by Useless Warrior

I don't think the Iframe should or could be a problem. It's not any different than embedding any other outside content on to your page. Well, it is different in that SEs can read and follow the content within an Iframe. Also, it's your own content that you are including. By comparison, people/sponsors who produce RSS feeds can pull some tricks, but everyone trusts RSS implicitly.

You shouldn't have difficulty finding trading partners. It's a high quality blog with many, many well-written posts which had to require a lot of time and thought. There are very few adult blogs which are that text rich. Most of them are RSS-fed splogs with zero original content.

If anything, those gallery thumbs are doing you a favor by allowing you to capitalize on SE traffic that doesn't want to read a blog.

Thanks for the feedback, my sweetest sugarbuns!

[Licker4U]

Originally Posted by Trixie

Thanks for the feedback, my sweetest sugarbuns!

Oh God, did you just call UW sugarbuns??? OK, from now on UW will be known as "UW Sugarbuns"

[Trixie]

When UW & I have civil exchanges it makes me feel very good, like I have a banquet of delicious fleshy baked goods laid before me.

I considered "stickybritches" but wasn't sure if that would properly convey my affection for him.

[Thumbler]

I was thinking of a php include like this

<?php include("http://www.mydomain.com/file.html"); ?>

[Trixie]

Originally Posted by Thumbler

I was thinking of a php include like this

<?php include("http://www.mydomain.com/file.html"); ?>

Thanks for the tip/clarification.

[Toby]

Server security settings probably won't allow PHP includes from external domains.

If it does work, I'd suggest talking to your server admin.

A safer solution would be to have a simple script that retrieves and saves a local copy of the desired file, then use that local copy as your include file. Set a Cron to periodically update that file at a specified interval.

[papagmp]

Originally Posted by Toby

Server security settings probably won't allow PHP includes from external domains.

If it does work, I'd suggest talking to your server admin.

A safer solution would be to have a simple script that retrieves and saves a local copy of the desired file, then use that local copy as your include file. Set a Cron to periodically update that file at a specified interval.

I was going to just post the same - and if the server settings do allow it, you'd better get ready to be hacked - even if the includes only go across domains.

After much thought, we went with a script. So far, the one's we've implemented are working very well.

[Trixie]

Thanks very much for the advice & info, Toby & papa -- I will be sure to revisit this thread/your posts when I'm ready to wrap my pea-brain around it and step away from the iframe .