Here's my idea:
I'm going to try and create an extension that will try and find the following:
<a href="...#new">x new</a>
And then create a nsIAlert saying if a post was found.
Anyone want to help me since I know almost nil about extension developing?
----
Ryan McCue
Life is like a sewer. What you get out of it depends on what you put into it.
(Tom Lehrer)
You are here
FF Extension
December 14, 2006 - 8:41pm
#1
FF Extension
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I'm guessing this would be for forum posts... and if so, what's wrong with the RSS notification system? It should work well, and I can cache it all for better server load. Reloading individual pages while logged in puts a big strain on the system. When you're logged in, Drupal's cache is bypassed so it has to create the whole page from scratch each time. Server load is still quite high, so I'm toying with the idea of limiting connections by IP per minute as it is.
Sometimes, the impossible can become possible, if you're awesome!
There's no feed available for the tracker.
It would refresh at 5 minute intervals anyway. It's just cause I have to go back and refresh the page and then check if there are any new posts. It gets annoying when you are doing multiple things.
----
Ryan McCue
Life is like a sewer. What you get out of it depends on what you put into it.
(Tom Lehrer)
"If you're not part of the solution, you're part of the precipitate."
I'm actually considering caching the tracker so it only pulls every so often... say every 5 minutes and dumps it to an HTML file. It's actually one of the heaviest pages database-wise. If I cache it, a reloader wouldn't be a huge deal.
Sometimes, the impossible can become possible, if you're awesome!
I'm usually listening to music, programming in PHP and C++ (and some JS too) and on chat. I don't have time to go back manually and do it.
I vote against caching the tracker. The whole point is that it's supposed to get the most recent posts, not the most recent posts from 5 minutes ago.
----
Ryan McCue
Life is like a sewer. What you get out of it depends on what you put into it.
(Tom Lehrer)
"If you're not part of the solution, you're part of the precipitate."
It may be a necessity. I'm already manually caching all the most popular pages (FFP, homepage, apps, suite, etc) as straight HTML but when it gets busy, the server loads are still rough. I know eventually I'll need to go two servers or switch the main server to be all cached pages and use a second for forums or something... but I'd like to delay that as much as possible until there's some money coming in to pay for it.
Sometimes, the impossible can become possible, if you're awesome!
if there was a way to charge a nickle for each post it would help pay for your ISP bill.:-) Seriously, if we all think before we post messages that add little to a particular thread, all our workloads would be reduced. I believe that some are using forums as a social outlet. Please think about your reasons for posting, there is no need for 5 of us to tell a poster to search first.
Maybe refreshing tracker every 15 -20 minutes would slow down non-essential posts.
my 2 cents, now back to my hole,
Clair
that has nothing to do with the tracker loads. No matter how many new posts there are - none, 24, 382 - the tracker is still dynamically generated.
Only 1 of us usually tells a poster to search first, sometimes I answer a question when someone already has, to clarify what the first person said.
Maybe you could limit the use of the tracker to people over say 100 or maybe even 1000.
Anyway, back to the point. I have a Greasemonkey script which will check the page to find if there are new posts. Now I just have to get it to work
----
Ryan McCue
Life is like a sewer. What you get out of it depends on what you put into it.
(Tom Lehrer)
"If you're not part of the solution, you're part of the precipitate."