"The Norse Map is a Wargames-style visualization of ongoing attacks on servers around the world. Though it shows honeypots rather than actual private or government targets, the result is a live snapshot of trends in computer mischief."
Now there are many hundreds of such protocols in application today. HTTP is an access protocol and one with content negotiation too. The W3C has a boat load of specifications within the SOAP space that are relevant. The semantic web is another deep source. Even the now long in the tooth Object Management Group's CORBA specifications all cover the same ground.
The point of course is that we really don't need another green fields specification and especially one for static data dumps. Instead we need to agree to access protocols and availability contracts. Unfortunately, I have nothing more to add right now as it is not really my problem.
Our development team uses Skype for messaging, voice conference, and screen sharing. It has proven itself a reliable tool year in and year out. Unfortunately, for a software development team it is sometimes unhelpful, especially when it mistakenly interprets data or code as emoji or formatting instructions. I assume that Skype developers use Skype for their communication too and so will have the same frustrations with it interpreting message text as our team has.
Skype's Preferences dialog does allow disabling emoji but not formatting (at least on the Mac). To remove Skype formatting in messages were, for example tilde means
strike-through and asterisks means bold do the following
- Quite Skype,
- Edit the file $HOME/Library/Application Support/Skype/shared.xml,
- Replace <EnableWiki>1</EnableWiki> with <EnableWiki>0</EnableWiki>,
- Save the file, and
- Restart Skype.
Update: Blogger's editor seems to have similar issues!