ManyCam free, as opposed to the pro version, is the cut down version of a program which actually contains many more features. ManyCam free effectively turns your PC hooked up to a webcam into a video studio. It allows you to use your webcam with multiple applications at the same time. You're able to broadcast your desktop over your video window and add a list of different types of audio effects to your webcam stream.
May 26, 2012 Cobook allows you to manage your contacts with joy: It always knows what you mean: just type in an email, phone number or other piece of info and Cobookwill sort out where to put it. Keeps your contacts up-to-date: connect your social network accounts and Cobook will automatically look up p. Cobook has given its contacts book app a pretty radical design overhaul for the iPhone today, introducing a brand new look with a cleaner typeface, transparent menus and intuitive swipe-based.
ManyCam uses a webcam or video camera as input for the software itself and then replicates itself as an alternative source of input. Because of this, ManyCam works well with nearly all chat software such as Windows Live Messenger that can use alternative video sources.
ManyCam represents one of the best applications for people who want to introduce their own personalized style into video chat communication, and also can serve as a great multi-protocol video chat management system that can greatly help people who are lacking in free time to better organize their daily work.
ManyCamFeatures:
- Add amazing webcam effects & graphics to your videos and photos
- Use your webcam with many applications simultaneously
- Add amazing microphone audio effects to your broadcast
- Draw over your video window
- Screencast your desktop
- Picture in Picture
- Switch between different video sources
- Create your own custom webcam effects
I have tried to reach the zen of address book synchronisation for many years. However, I have always experienced that some contact information, especially instant messaging and social networking addresses, gets lost or corrupted during the synchronisation.
The most adopted format for representing contact information is the vCard, whose last version is the 4.0 (see IETF’s RFC 6350, 2011), while the most adopted protocol for accessing contact information is the CardDAV (see in the IETF’s RFC 6352, 2011), which is based on the vCard format. Hence, I performed a little empirical study of the actual interoperability of the vCard format.
First, I defined a sample contact:
Second, I added this contact to four different address books:
- Apple Contacts (formerly Address Book)
Third, I exported each of the address books to a vCard file.
Fourth, I created a sample vCard file based on the vCard format 4.0.
Finally, I compared the exported vCard files and the sample vCard file among each other. The differences between these files blew my mind.
In the following, I show these vCard files and discuss the properties which are not interoperable. Note that I stripped the irrelevant properties and rearranged the remaining properties to make the comparison easier.
Sample vCard file
The specification of the vCard is kind of shocking. Believe or not, it does not support social networking addresses yet. Even worse, it supports constructs which are not interoperable, namely grouped properties and non-standard properties.
Grouped properties are properties prefaced with the same group name. They should be grouped together when displayed by an application. I will show examples of grouped properties later.
Non-standard properties are properties defined unilaterally or bilaterally outside the standard. They may be ignored by an application.
Hence, I was forced to represent the Twitter address by a non-standard
X-SOCIALPROFILE
property:Apple Contacts (version 7.1)
The vCard file exported by Apple Contacts is only partially based on the vCard format 3.0 (see IETF’s RFC 2425 and RFC 2426, 1998) and its extension for instant messaging (see IETF’s RFC 4770, 2007).
The web address is represented by a standard
URL
property grouped together with a non-standard X-ABLabel
property:This issue can be solved by changing the type of the web address from “home page” to “home”. This leads to a vCard file where the web address is represented by a standard
URL
property:The Twitter address is represented by a non-standard
X-SOCIALPROFILE
property:Cobook (version 1.1.6)
The vCard file exported by Cobook is only partially based on the vCard format 3.0. With the exception of the name, all the contact information is represented by either grouped properties or non-standard properties.
Google Contacts (15 November 2012)
Google Contacts does not support social networking addresses natively, so I was forced to add them as URLs.
The vCard file exported by Google Contacts is only partially based on the vCard format 3.0 (see IETF’s RFC 2425 and RFC 2426, 1998).
The colon in all the URLs is unnecessarily escaped.
Cobook Contacts 3.0 1
Similar to Apple Contacts, the web address is represented by a standard
URL
property grouped together with a non-standard X-ABLabel
property:I guess this is because Google Contacts specifically targets Apple Contacts when exporting to a vCard file. This issue can be solved by changing the type of the web address from “Home Page” to “Home”. This leads to a vCard file where the web address is represented by a standard URL property:
![Cobook contacts 3.0 reviews Cobook contacts 3.0 reviews](/uploads/1/2/6/3/126374231/727297384.jpg)
The Skype address is represented by a non-standard
X-SKYPE
property:The Twitter address is represented by a standard URL property grouped together with a non-standard
X-ABLabel
property:Memotoo (15 November 2012)
The vCard file exported by Memotoo is only partially based on the vCard format 2.1.
The Skype address is represented by a non-standard
X-SKYPE-USERNAME
property:![Cobook contacts 3.0 0 Cobook contacts 3.0 0](/uploads/1/2/6/3/126374231/839082566.jpg)
The Twitter address is represented by a non-standard
X-TWITTER
property:Conclusion
Given the results of this study, it is not surprising that the import/export of vCard files as well as the synchronisation via CardDAV do not behave as expected most of the time.
Common contact information such as email addresses, telephone numbers, postal addresses, web addresses, and instant messaging addresses can be represented in two ways: using standard properties, or using standard properties grouped together with non-standard properties. The second way is currently used by Apple (and other vendors targeting Apple); it is unnecessary, prevents interoperability, and promotes vendor lock-in.
Cookbook Contacts 3 0 Free
Other common contact information such as social networking addresses are not supported at all.
So what should be done? Here is my suggestion:
First, the IETF should remove grouped properties and non-standard properties from the specification, since open standards should promote interoperability and prevent vendor lock-in. Second, the IETF should add social networking properties to the specification. Third, the IETF should provide an official validator for vCard files. Finally, the vendors should implement the last version of the vCard format, and they should do it right.
Update 22 November
Cobook Contacts 3.0 And Windows 10
I have shared my concerns in IETF’s vCardDAV mailing list. You can follow the thread here.