| 1 | | Place holder for gnusocial options |
| | 1 | = Options for GNU Social server setup = |
| | 2 | |
| | 3 | Related discussion: https://quitter.se/conversation/2262019 |
| | 4 | |
| | 5 | Below GS refers to GNU Social |
| | 6 | |
| | 7 | == Plain GNU Social == |
| | 8 | Just a custom theme |
| | 9 | |
| | 10 | Pros: |
| | 11 | - updates and maintenance easy since we are working straight from |
| | 12 | upstream |
| | 13 | - all GS features work as designed, e.g. polls, groups etc |
| | 14 | Cons: |
| | 15 | - no auto-updates |
| | 16 | |
| | 17 | == GNU Social + meteor == |
| | 18 | |
| | 19 | Pros: |
| | 20 | - we are still pretty close to upstream, just using meteor service |
| | 21 | in addition |
| | 22 | - auto-updating UI |
| | 23 | - GS features such as polls etc should work |
| | 24 | Cons: |
| | 25 | - some users don't like auto-updating, and some claimed it to be a |
| | 26 | bit "messy" (see quitter discussion above) |
| | 27 | - having the additional meteor service has some extra maintenance |
| | 28 | overhead, although from my own experience setting it up for dev.social it doesn't seem so bad |
| | 29 | |
| | 30 | === tech notes === |
| | 31 | Some helpful links from @vinz |
| | 32 | |
| | 33 | http://www.verbosity.ca/statusnet-identica-ostatus-microblogging/getting-real-time-updates-statusnet |
| | 34 | |
| | 35 | http://whird.jpope.org/my-statusnet-meteor-and-realtime-setup/ |
| | 36 | |
| | 37 | https://github.com/vinzv/gnusocial/tree/master/meteor |
| | 38 | |
| | 39 | == GNU Social + qvitter plugin == |
| | 40 | I'm not very familiar with the details of this one. |
| | 41 | |
| | 42 | Pros: |
| | 43 | - nice-looking interface which reminds of Twitter (easy to attract |
| | 44 | user of that service) |
| | 45 | - it handles auto-updates in a manner which some people prefer to |
| | 46 | meteor, i.e. it just displays e.g. "3 new posts" instead of |
| | 47 | disrupting the time-line |
| | 48 | - from discussions with @hannes2peer@quitter.se I have the |
| | 49 | understanding that auto-updates are just the JavaScript client |
| | 50 | polling, so no additional service (such as meteor) is needed |
| | 51 | |
| | 52 | Cons: |
| | 53 | - AFAIK the qvitter UI does not yet implement all GNU Social |
| | 54 | features, and at least on Quitter.se you sometimes have to |
| | 55 | fall-back to the old UI, this is ugly and confusing for new users |
| | 56 | |
| | 57 | == GNU Social + chimo's updater == |
| | 58 | |
| | 59 | chimo says it's experimental and not well tested |
| | 60 | |
| | 61 | https://github.com/chimo/gs-wsRealtime |
| | 62 | |
| | 63 | Pros: |
| | 64 | - looks like a really neat WebSockets-based system, i.e. real-time, |
| | 65 | not polling |
| | 66 | |
| | 67 | Cons: |
| | 68 | - setup and dependencies looks pretty heavy (although I'm not very |
| | 69 | familiar with PHP dependency management) |
| | 70 | - "Ratchet doesn't support SSL. One work-around is to use nginx to |
| | 71 | proxy those requests." |