Differences

This shows you the differences between two versions of the page.

--- navierstokes [2014/09/29 09:13]
sekula [Download Latest Release]
+++ navierstokes [2016/04/16 12:53]
sekula [Download Latest Release]
@@ Line 21: / Line 21: @@
 ===== Download Latest Release =====
-{{:navierstokes-0.9.1.tgz|}}
+<code>
+git clone https://hub.polari.us/code/index.cgi/navierstokes/
+git checkout v1.0.1
+</code>
 Release notes:
-  * Bugfix: direct messages on Diaspora were being shared to other networks (notes beginning with "@")
+  * BUGFIX:
+    * Images posted to Pump.io now have the To field correctly set
-  * This is a BETA release. Use it at your own risk. It's very likely that the same post will appear 500 times in one hour on your favorite social network and cost you half of your friends.
+  * General exceptions handling and CURL usage improvements
   * Email any bugs you find to <navierstokes+NOSPAM@polari.us>
-----
+Browse the code: [[https://hub.polari.us/code/index.cgi/navierstokes/]]
+----
 ===== Requirements =====
@@ Line 46: / Line 50: @@
     * cd fuzzywuzzy
     * python setup.py install
-  * FBCMD
-    * This is needed if you want to bridge to Facebook.
-    * [[http://fbcmd.dtompkins.com/]]
   * t (Ruby Gem for interacting with Twitter)
     * This is needed if you want to bridge to Twitter.
@@ Line 54: / Line 55: @@
     * gem install t (requires Ruby 1.9 or greater)
   * txt2html: needed for clean text -> HTML conversion (e.g. from Twitter messages to Pump.io)
+  * ImageMagick: needed to rescale image attachments
 In general, here are the Python libraries needed to make this package operate:
@@ Line 85: / Line 87: @@
 ===== Installation =====
-  - Unpack the tarball. This automatically creates the navierstokes/ application directory
+  - Check out the code from the git repository above. This automatically creates the navierstokes/ directory.
   - You should create a configuration file for NavierStokes: ~/.navierstokes/navierstokes.cfg. The syntax for the file is explained below.
   - If you intend to bridge between Pump.io and other networks, you must use PyPump to register a client (e.g. NavierStokesApp) on Pump.io. Follow their instructions for getting the client credentials and tokens. Enter those into the <code>~/.navierstokes/navierstokes.cfg</code> file (see example below). PyPump docs: [[https://pypump.readthedocs.org/en/latest/]]
@@ Line 111: / Line 113: @@
 client_tokens: XXXXXXXXXXXXXXXXXX
 sharelevel: All
+noshare_keyword: noshare
 [diaspora]
@@ Line 118: / Line 121: @@
 aspect: public
 sharelevel: All
+noshare_keyword: diaspiverse
-[facebook]
-type: facebook
-username: My Name On Facebook
-album: Timeline Photos
-sharelevel: Public
 [twitter]
@@ Line 145: / Line 143: @@
 </code>
-Note that "sharelevel" means at what level of publicity from other networks you want a notice shared to this one. I've set this, for now, the way I like it. If you set this to "Public", ONLY notices that are public on other networks will go there. For instance, I only like to share things that are public on pump.io with Facebook and Twitter. Things on Twitter are public by default, so they will ALWAYS be shared with other networks.
+Note that "sharelevel" means at what level of publicity from other networks you want a notice shared to this one. I've set this, for now, the way I like it. If you set this to "Public", ONLY notices that are public on other networks will go there. For instance, I only like to share things that are public on pump.io with Twitter. Things on Twitter are public by default, so they will ALWAYS be shared with other networks.
 "shortenurls" presently enabled will take ALL URLs listed in the message text and shorten them via ur1.ca. In the future, this will be a choice the user can make.
@@ Line 155: / Line 153: @@
 ===== Running NavierStokes =====
-Once you have written a .cfg file and setup account information in it (and, in the case of Pump.io, Twitter, and Facebook, authenticated PyPump, t, and FBCMD against those respective networks as clients), you can try executing NavierStokes manually:
+Once you have written a .cfg file and setup account information in it (and, in the case of Pump.io and Twitter, authenticated PyPump and t against those respective networks as clients), you can try executing NavierStokes manually:
 > python ./NavierStokes.py
@@ Line 216: / Line 214: @@
-  * The logo is a mashup of a Wikimedia Commons image from the Navier-Stokes Equation Wikipedia Page and the logo of the Pump.io, GNU Social, and Diaspora networks. I intentionally left Twitter and Facebook off the logo as I don't want to deal with issues of using their logo.
+  * The logo is a mashup of a Wikimedia Commons image from the Navier-Stokes Equation Wikipedia Page and the logo of the Pump.io, GNU Social, and Diaspora networks. I intentionally left Twitter off the logo as I don't want to deal with issues of using their logo.
   * Bernoulli Fluid Flow image: "BernoullisLawDerivationDiagram" by MannyMax (original) - [[:Image:BernoullisLahenrique gostoso da america latia .,.... wDerivationDiagram.png]]. Licensed under Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons - https://commons.wikimedia.org/wiki/File:BernoullisLawDerivationDiagram.svg#mediaviewer/File:BernoullisLawDerivationDiagram.svg
   * Pump.io logo: "Pump.io" by Mathiasgebbe - Own work. Licensed under Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons - http://commons.wikimedia.org/wiki/File:Pump.io.svg#mediaviewer/File:Pump.io.svg

Cooley-Sekula Document Central

User Tools

Site Tools

Differences

Page Tools