The problem you're glossing over: since the message is sent in clear text, the machines who have access to the message contents is not limited to SMTP servers.
Just about any device in between can parse/save/archive the content (sender/destination ISP routers, your ISPs ISP, etc...)
OSS means no sanity checks on feature creep, portability verification, documentation verification, regression testing, and all the other enterprise-project aspects of development that make it a useful technology.
I think this is more project dependant. Any well done project, OSS or not, should have an implementation of these features. If a certain project does not, it's not OSS thats to blame. I think the Apache projects are a good example of how OSS projects should be done, and set an attainable goal to be aimed for for new OSS developers.
Slashdot Mirror
I'd guess it's due to tax laws, not software, being a /very/ regional thing.
The problem you're glossing over: since the message is sent in clear text, the machines who have access to the message contents is not limited to SMTP servers.
Just about any device in between can parse/save/archive the content (sender/destination ISP routers, your ISPs ISP, etc...)
Why not? I'm guessing you just haven't tried very hard. http://xinehq.de/index.php/faq#WMV
I just want to make sure im clear on what your point is. You are suggesting that not being able to transfer files via GAIM is a feature and not a bug?
I think the idea is you can log back in to change it (to something you'll remember this time).
I think this is more project dependant. Any well done project, OSS or not, should have an implementation of these features. If a certain project does not, it's not OSS thats to blame. I think the Apache projects are a good example of how OSS projects should be done, and set an attainable goal to be aimed for for new OSS developers.