on master help sign in
Add definition of 'ship'
commit189968926f476da1cd9fc950d9bacfb06fb6bb4f authorMichael Hartl <michael@michaelhartl.com> dateFri 1 May 2020, 11:47 (6 years ago) parent0f0437e
1 file changed+1−1
content/blog/introducing-os1.md+1−1
content/blog/introducing-os1.md+1−1
@@ -58,7 +58,7 @@ First, each chat channel is only shared between the host and the members of a ch
5858
5959Second, each chat message is encrypted and signed by your Urbit ID. Again, we don’t call Urbit ‘secure’ yet since it’s unaudited — but we’re working to have Urbit audited this year.
6060
61−Third, chat in Urbit OS is a protocol for sending messages between ships. It’s easy to imagine extending chat in all kinds of fun and interesting directions. Chats that only accept certain message types, chats that have disappearing history, chats that you can only post to during certain times of day, and so on.
61+Third, chat in Urbit OS is a protocol for sending messages between computers on the network (known as “[ships](https://urbit.org/docs/glossary/ship/)” and identified by their Urbit IDs). It’s easy to imagine extending chat in all kinds of fun and interesting directions. Chats that only accept certain message types, chats that have disappearing history, chats that you can only post to during certain times of day, and so on.
6262
6363(If you’re curious to try one of these things, or have an idea about something you’d like to experiment with — consider submitting a proposal in our [grants program](https://grants.urbit.org/). We regularly reward contributor work with address space.)
6464