874
edits
Changes
added information about locked-down feeds, w/ link to tutorial
In the following examples, just type in this editor. Updates happen the next time you summon Ubiquity.
== Choices, Choices... ==
You may notice a drop-down menu mentioning something about a "feed type" just above the editing field in the command editor:
http://www.toolness.com/images/20090318121423.jpg
For now, just make sure this drop-down is set to "Regular". We'll tell you more about what this means later.
= Hello World: The First Command =
[[Image:Subscribe.png]]
If the user chooses to subscribe to a Regular command feed from an untrusted source, they will get a security warning message before they can install the command. (And in Ubiquity 0.1, ALL sources are considered untrusted, so don't take it personally!) Because Regular Ubiquity commands command feeds can execute arbitrary javascript with chrome privileges, subscribing to a command from a website means allowing that site full access to do whatever it wants to your browser. We want to make sure people understand the dangers before subscribing to commands, so we made the warning page pretty scary.
[[Image:Warning.PNG]]
=== Feed Types ===
Recall that back near the beginning of the tutorial, you set the "feed type" to "Regular". As you may have guessed, there's actually more than one way to write a command feed. The advantage of Regular feeds is that they let you do whatever you want, so it's really easy to innovate, but the disadvantages lie in subscribing to misbehaving or malicious code. You can alternatively write what's called a ''Locked-Down Feed'', which is much safer and doesn't raise a warning page when a user subscribes to it—but the consequences are that you have less freedom of implementation as a command author. If you're interested in learning more about Locked-Down Feeds, check out the [[Labs/Ubiquity/Locked-Down_Feed_Tutorial|Locked-Down Feed Tutorial]].
=== Trust Networks ===
In the future, we're going to have something set up that we call a "trust network". When you try out a Ubiquity command from a website, and determine that the command is safe (or unsafe), you'll be able to leave an approval (or a warning). When your friends with Ubiquity installed visit the same site, they'll see the approval or the warning that you left. In this way, users will be able to rely on the judgement of other people they already know and trust in order to help them make decisions about whether a command is safe to install or not.
