LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i thought someone mentioned somethign very similar recently, and it would have been far too resource intensive... depends how often the feed would be used, but a dynamic user specific feed on a website would mean it would be called each time someone viewed that website. i would think it would need to be cached for 30 minutes or controlled some other way, other wise there are potentially nasty implications.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
It's an interesting idea. All the syndication feeds used to be live, but about 2 years ago I had to switch them to cached, as they just get requested far too often. As this idea would basically add 150,000 feeds, we couldn't pre cache them all (well, we could - but it wouldn't be worth it). I have a couple ideas in my heads as to how it could potentially be solved, but I am still working them out. First, I'd like to gauge the demand for this feature though. Who's interested?
thinking about the implementation, i know that /. has banned the firefox livemarks as a reader (or at least mine!) so i'm asuming the actaul client is detectable, so could be restricted to certain user-only clients (ie. not going to be hit on a webpage)
Originally posted by acid_kewpie thinking about the implementation, i know that /. has banned the firefox livemarks as a reader (or at least mine!) so i'm asuming the actaul client is detectable, so could be restricted to certain user-only clients (ie. not going to be hit on a webpage)
It must be just you they don't like. Mine seem fine
I haven't tested it, but considering it uses the http protocol the client is probably sending a useragent variable so it should be possible to detect.