|
|
2008-03-09
, 10:15
|
|
Posts: 37 |
Thanked: 10 times |
Joined on Dec 2007
@ Edinburgh, Scotland
|
#42
|
I can get all of those feeds to work when I prefix them with "http://". At least one (Slashdot) failed when prefixed with "Http://" (capitol H). "feed://" failed too. I'll file a bug about the scheme handling.
|
|
2008-03-09
, 16:10
|
|
Posts: 54 |
Thanked: 11 times |
Joined on Feb 2008
|
#43
|
|
|
2008-03-10
, 13:58
|
|
Posts: 37 |
Thanked: 10 times |
Joined on Dec 2007
@ Edinburgh, Scotland
|
#44
|
I did the http versus no http with Engadget, but not with the other links (I assumed from Engadget that it made no difference). You're right, the other three work. Man, I wonder what's so special about Engadget?
|
|
2008-03-13
, 12:55
|
|
Posts: 37 |
Thanked: 10 times |
Joined on Dec 2007
@ Edinburgh, Scotland
|
#45
|
|
|
2008-03-22
, 18:20
|
|
Posts: 148 |
Thanked: 20 times |
Joined on Sep 2007
|
#46
|
|
|
2008-03-23
, 22:22
|
|
Posts: 148 |
Thanked: 20 times |
Joined on Sep 2007
|
#47
|
|
|
2008-03-25
, 15:43
|
|
Posts: 37 |
Thanked: 10 times |
Joined on Dec 2007
@ Edinburgh, Scotland
|
#48
|
I have gone through and added a bunch of feeds to nibbles. I am wondering if there are any plans in the works to improve download speed?
I have basically the same feeds setup in claws-mail rss reader. In claws mail it takes about 2 minutes to update all my feeds and processor is about 50% used.
In Nibbles it takes over 1/2 hour and the processor was pegged at 100% the whole time.
If there is any information I can provide or anything else I can try, please let me know.
|
|
2008-03-25
, 17:26
|
|
Posts: 148 |
Thanked: 20 times |
Joined on Sep 2007
|
#49
|
|
|
2008-03-26
, 12:35
|
|
Posts: 37 |
Thanked: 10 times |
Joined on Dec 2007
@ Edinburgh, Scotland
|
#50
|
I do have more than 4 feeds. I have not done an exact count but it is more in the 30+ range. I can send you the list if you want but I don't see any one feed causing the slow down, it just seems to take a while to process each feed.
I think I've worked out what's happening. When you don't prefix the url with "http://" you get sent the IPv6 socket (which we can't handle - I guess the version of Ruby we have hasn't been compiled with support for it).
I can get all of those feeds to work when I prefix them with "http://". At least one (Slashdot) failed when prefixed with "Http://" (capitol H). "feed://" failed too. I'll file a bug about the scheme handling. Thanks a lot for pointing out this bug.
Note, that the lack of feedback/progress notification is bug #2270. At the moment, there can be a large wait (where nothing is visibly happening) while adding a feed. It's really compounded when adding a new feed and the feed is large.
Good luck, let me know how that works out.
Mark