I didn't want to keep this unpublished so you don't think I'm systematically ignoring your posts. But generally a feature request needs to have a descriptive headline so people know what they're looking at. Also, this type of feature is way outside the scope of what the client is supposed to do. There are enough ways out there to access RSS or twitter feeds, Soulseek doesn't need to become another one. I don't mind people voting on stuff like this, but I don't really see myself ever doing it.
I didn't expect a "ticket" that included IP addresses and chatlogs to be published. No really -- no worries there. It's good you got rid of that spammer, though. Great job, Nir!
I disagree with your notion that Soulseek should only incorporate old, stale, original Napster type functionality, and nothing more.
Any modern p2p has RSS feeds built in! Go look at utorrent or transmission for examples.
Including RSS and Twitter will encourage more people to use the network. More people = more donations.
SoulseekQT should have 1 RSS feed preconfigured, to display information about SQT updates. You can configure this in Drupal easy, and it's not much programming client-side either.
Okay, I understand what you're saying. I don't think this is the right kind of feature for Soulseek, but there's no reason people shouldn't at least be able discuss it. I'll edit the headline to be more descriptive.
"I don't think this is the right kind of feature for Soulseek"
"Including RSS and Twitter will encourage more people to use the network."
100% Disagree more people = more trouble to Soulseek