Twitter has joined Facebook in adding a profile configuration to always use a secured HTTPS connection for routine tweeting and reading after you log in to the company’s Web site; the login was already secure. Using HTTPS protects you against sidejacking in a public location where someone with Firesheep or other software could hijack your identity by sniffing a Twitter token without needing to know your account name and password. Log in, click your name at the upper right, select Settings, and scroll down to enable the option.
follow link
Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling Take Control ebooks.
Manage Multiple ChronoSync Documents
If you have multiple ChronoSync documents and need to run your syncs or backups manually, you may find it taxing to open each ChronoSync document and execute it manually. There are two easy methods to simplify managing multiple ChronoSync documents.
- You can add the ChronoSync documents to a Container document. A Container holds multiple ChronoSync documents and enables you to control several ChronoSync documents as if they were one document.
- You can make use of the Scheduled Documents Manager window to collect and organize commonly used ChronoSync documents without scheduling them.
Both methods allow you to schedule or manually run your syncs and backups.
Visit ChronoSync Tips
Written by
Adam C. Engst
Twitter Adds Always Secure Option
But do Twitter.app on Mac OS X & iOS honor this setting? I believe they used insecure HTTP when FireSheep was announced and I checked...
It's apparently first for the Web site. Some Twitter-made clients don't have this yet. Many third-party clients offer an option.
Now they've been offline for 4 hours because of screwing up the impementation of this "security feature"! What a mess!