Copyright 2010, 2012, 2014 Adobe Systems Incorporated (http://www.adobe.com/), with Reserved Font Name 'Source'. All Rights Reserved. Source is a trademark of Adobe Systems Incorporated in the United States and/or other countries.
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL
Send suggestions for changes to the Source Sans OpenType font project maintainer, [Paul D. Hunt](mailto:firstname.lastname@example.org?subject=[GitHub] Source Sans Pro), for consideration.
## Further information
For information about the design and background of Source Sans, please refer to the [official font readme file](http://htmlpreview.github.io/?https://github.com/adobe-fonts/source-sans-pro/blob/master/SourceSansProReadMe.html).
<p>To check that you have the correct font file, compare the font version of your font file to the font version provided in the Release Notes section below.</p>
</p>Source Sans Pro was designed by Paul D. Hunt under the guidance of Robert Slimbach. It is Adobe's first open source typeface family, conceived primarily as a typeface for user interfaces. Source Sans Pro draws inspiration from the clarity and legibility of twentieth-century American gothic typeface designs. Distilling the best archetypical qualities of these models, Paul followed a rational design approach by simplifying glyph shapes by paring them to their essential form. However, in order to more easily differentiate similar letter shapes (such as uppercase I and lowercase L), some additional details have been added. Besides providing such explicitly clarity in short text strings, another fundamental design consideration was to create a typeface that reads well in extended settings. This can be seen in the general proportions: Source Sans Pro has been designed with a more generous width than many other comparable gothics, and its shorter majuscule letters, combined with minuscule letters with longer extenders, create a more pleasant reading texture in longer text passages.</p>
Source Sans Pro currently supports a wide range of languages using Latin script. The non-italic fonts also support both modern and polytonic Greek, as well as glyph coverage for extended Cyrillic. Other members of the greater Source type system include Source Code Pro, a monospaced version of Source Sans designed specifically for coding, and Source Serif Pro. As an open source project, it is expected that incremental updates will be made over time to extend glyph set coverage and functionality. If you are interested in contributing to this open source project, please visit this project page on GitHub for information on how to become involved. Source Sans Pro can be adapted and redistributed according to the terms of the Open Font License (OFL) agreement. </p>
<strong>Menu Names And Style Linking</strong>
<p>In many Windows<sup>®</sup> applications, instead of every font appearing on
the menu, fonts are grouped into style-linked sets, and only the name of
the base style font for a set is shown in the menu. The italic and the
bold weight fonts of the set (if any) are not shown in the font menu, but can still be
accessed by selecting the base style font, and then using the italic
and bold style buttons. In this family, such programs will show only the
following base style font names in the menu:</p>
<p>Source Sans Pro<br>
Source Sans Pro Black<br>
Source Sans Pro ExtraLight<br>
Source Sans Pro Light<br>
Source Sans Pro SemiBold<br></p>
<p>The other fonts in this family must be selected by choosing a menu name
and then a style option following the guide below.</p>
<tr><td>Menu Name</td><td></td><td>plus Style Option... </td><td></td><td>selects this font</td></tr>
<tr><td>Source Sans Pro</td><td></td><td>[none]</td><td></td><td>Source Sans Pro Regular</td></tr>
<tr><td>Source Sans Pro</td><td></td><td>Italic</td><td></td><td>Source Sans Pro Italic</td></tr>
<tr><td>Source Sans Pro</td><td></td><td>Bold</td><td></td><td>Source Sans Pro Bold</td></tr>
<tr><td>Source Sans Pro</td><td></td><td>Bold, Italic</td><td></td><td>Source Sans Pro Bold Italic</td></tr>
</a>Font specific resources include the <ahref="http://helpx.adobe.com/font-folio-type.html">Font Folio and Type Product Help page</a> and the <ahref="http://forums.adobe.com/community/typography_fonts">Adobe Type user-to-user forums</a>.</p>
<ahref="http://www.adobe.com/type">Adobe Type Showroom</a>
<ahref="http://www.adobe.com/type/family_readmes.html">Index page for all family Read Me files</a>
Adobe, the Adobe Logo, Source, Illustrator, InDesign, PageMaker and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Windows and OpenType are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Mac, Mac OS and TrueType are trademarks of Apple Inc., registered in the U.S. and other countries. All other trademarks are the property of their respective owners. <br/>
To avoid confusion we're dropping the 'l' and calling them 'bogs'.
**WARNING** This is very new and experimental software, **not intended for use in production**. Pull-requests are welcome, and if you find anything wrong feel free to report it in public.
Try it online at http://bogbook.com/ !
bogbook is a distributed social networking application using [TweetNaCl.js](https://tweetnacl.js.org/#/) to publish signed append-only logs to your browser's localStorage.
The bogs are then gossiped between your bog client and bog 'pub' servers using websockets. You're responsible for syncing your messages between different bog 'pub' servers. Bog 'pubs' themselves don't talk to each other, instead they only talk to clients.
When you click on a public key, your client will connect to your current pub to see if there are any new messages from the public key that you've clicked on.
### But what about ssb?!
This is _not_ [secure-scuttlebutt](http://scuttlebot.io/). But it is influenced by my 3+ years working on the project, and there are many similarities between bogbook and secure-scuttlebutt.
The biggest difference is that all of the bogging happens in the client, making it a browser-first bogging network. Last I checked, ssb isn't leaving the server.
Right now we have no private bogging, and no blob distribution (besides profile photos, which are saved to your log in base64).
### how to
git clone email@example.com/bogbook/bogbook.git
Bogbook should launch in your browser. If it doesn't, navigate to http://localhost:8080/
All of the bogbook cryptography is produced using [TweetNaCl.js](https://tweetnacl.js.org/#/) which is a port of [TweetNaCl](https://tweetnacl.cr.yp.to/), a cryptography library written in 100 Tweets.
bogbook generates an ed25519 public/private keypair on load using `nacl.sign.keyPair()`, which is then stored in localStorage at `localStorage['id']` as a JSON object with the public/private keypairs base64-encoded.
When you post a new message, bogbook will
+ iterate up the message sequence number
+ hash the contents of the previous message using sha512
+ sign the contents of the current message with your ed22519 private key
+ hash the new message (including the signature) using sha512
before appending the feed to the log stored in your browser.
Please note: All logs are append-only, public, and plain text at the current time. While you _can_ moderate your local database and pub servers by deleting logs associated with public keys, it can be difficult to unsay something, so don't drink and bog, people.
Some browsers clear localStorage upon exit, others will clear it if you wipe your browser cache. Remember to save your public/private keypair somewhere, because no one can regenerate it for you.