Friday, April 25. 2008Flatforty SurveyTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
"1. Do you like/use the flatforty function? If so, why? if not, why not?"
I absolutely do - I personally find that it is usually fairly obvious what thread a comment belongs to (the thread title appears above the comment in the flatforty display), and it is massively more convenient than scrolling through an article, trying to find the newest comments (I always use the threaded view when reading comments, so newly added ones can appear in multiple places), especially when there are several articles currently under heavy discussion. I prefer reading it online - I think it's a little too high-traffic for RSS, personally. I was very pleased to see it return this morning
1. I use the flatforty function as a crude workaround for seeing new posts to an article. Often, I read an article at a time where there a very few comments. When I come back a few days later to see new comments, it is very difficult to see which comments are new, so I use the flatforty function instead.
This workaround of course has some limitations, I guess flatforty was not designed for that: - maximum of 40 new comments - I don't see the context of the comments (parent post or thread) - flatforty has comments to all articles, not just the one I'm interested in. 2. No, I wouldn't use the RSS feed Thanks for working on the dot and for fixing the flatforty function.
You may want to make the flatforty link in this blog entry actually working, at the moment it doesn't since the link is gref'ed instead href'ed. =)
I also like flatforty as is. Maybe optionally allowing set amount of recent comments shown or setting a duration (comments last x hours, today, last x days etc.) would be an improvements, but that would invalidate flatforty's name. What I really want to see is a date/timestamp for the dot articles in the rss file. The item's called and should contain a date/time according to RFC822. After adding that Clee should have no more reason to not include the dot on planety.
Btw: I added a RFC 822 timestamp and a guid to each item on the dot rss. It will take a while for www.kde.org to sync them, though, so hold your breath.
Someone had turned off the cron job for the flatforty static updates. I just turned it back on, since there were a lot of complaints about it being broken...
Ah, so it was you! Thanks! I realized I must have broken something, but I forgot the difference between the dynamic the static version. That's also why I was unable to reproduce it. Anyway, glad to have it fixed.
|
QuicksearchMy Books on Qt 4Calendar
KategorienStatisticsLetzter Artikel: 2010-12-03 12:16
120 Artikel wurden geschrieben
222 Kommentare wurden abgegeben
1599 visitor(s) this month
PLUGIN_EVENT_STATISTICS_TEXT_DAYVISITORS
7 Besucher online
Blog AdministrationShow tagged entries |