this page is just to contain random notes about groupware system(s) that i'd like to build someday.
maybe the main one will be called 'gasket'. (note to self: see names file for other potential names)
of course, we want to unify wiki/blog/forum/CMS as much as possible
- 'user was banned for this post'
- AmendableCode?, with PieTrust? for voting rights
- no negative rep (secure against sockpuppets)
- 'best of' list for blog posts/topics
- threaded discussion, but comments can be marked as 'assimilated' when added into the wiki summary
- rss
- permalinks (including paragraph granularity)
- perspectival post popularity, perspectival front pages
- http://features.sheep.art.pl/BayleShanks
- federation (UnifiedRecentChanges?,
- email notifications, subscribedChanges
- tracking of what you have and havent read
- announcements
- tags (see http://wagn.org/)
- the convenience of TiddlyWiki? ?
- the sparse design of Hatta
- farmable
- PieTrust? AuthorshipCredit?
- must be able to interact with it as if it were an email list
- consider integrating http://incubator.apache.org/wave/ or parts of it?
- add ability to require higher access permissions to write to only some text in a communication (mb implement this by wave transclusion). This allows the use of parliamentary procedure, spam checking, etc for some parts of content but not for others
- organization of content into 'boards', but also a way for someone to just see the top/hot new content throughout
- consider also faceted classification, x-posting, folksonomic tagging,
- " multi-selecting posts, splitting topics, merging topics, locking topics, archiving topics, etc."
should we also include issue tracking? calendaring? FOAF and web-of-trust/facebook-like functionality? should we try to be another redmine or trello? Twitter-like messaging?
halfwiki built with pietrust:
- posts are not shown until someone approves it who has >0 reputation (the author can also be the approver)
- people can't accumulate negative rep, but posts can. you can vote down a post for 'redundant', but you must give the other post, or the summary at the top, as the thing it is redundant with. if the other one was written later, then that doesnt affect the writer's rep; otherwise, it takes away from the writer's rep to the extent that the previous score added to it (?!) -- or maybe just use S/N ratio instead of that (give people less rep for posting comments if they have a high stddev --- naw, mb S/N just gives the initial prior for the bayesian estimate of eventual comment rating which is used to rank order comments for showing users).
effective attention prioritization for occasional users:
- user specifies a timescale (or the system computes one for the user based on how often they visit and possibly how many articles they get thru each time) and sees top results over that timescale
attention prioritization:
- optional perspectival front pages
- social network-based or not (or rather, both combined)
- S/N priors less-rated comments
- possibly attention futures market and/or (possibly robust: see http://lesswrong.com/lw/dno/a_better_bayesian_truth_serum/ and the papers he cite) baysian truth serum
- proportional representation for frontpage
architecture:
- git backend for the wiki summaries
- no need for NoSQL? for comments as db can be sharded by discussion topic. We might want to build this as a set of separate sub-applications, in which case the consistency support of SQL schemas may be useful. We'll have a rich relational-ish, changing schema so Redis is probably out, except perhaps for reputation scores, but why keep that separate? Anyhow, Pietrust can handle some of that. Mongo might still be useful for speed of development, as we dont need transactions, but overall, i'd say SQl probably fits the bill there.
- should look at Drupal, Wordpress, Plone, Typo3, Discourse, Joomla, Reddit, Slashcode, PhpBB?, Simple Machines, MyBB?, vanilla forums, pligg, drigg, wagn, federated wiki, hatta for architectural/schema inspiration tips. Check these lists to see if i forgot anyone: http://blog.chinaunix.net/uid-107584-id-2931649.html, http://devstand.com/apps/popular-cms/ , http://w3techs.com/technologies/overview/content_management/all , http://www.scribd.com/doc/58072442/Content-Management-High-impact-Technology-What-You-Need-to-Know-Definitions-Adoptions-Impact-Benefits-Maturity-Vendors
- ooo: http://lxc.sourceforge.net/
notes:
- Sort only by root comment of thread or off-topic political threads get sorted first
- but should have option for ppl giving Attend reputation to say 'Attend regardless of parent' (e.g. absolute, rather than relative to siblings), in which case the comment itself gets promoted even if its ancestors do not
- Design space of moderation
- Moderation ontology
- moderation score Capped or uncapped
- Generalization of dimensions of moderation
- Witty/boring kind/unkind novel/obvious concise/rambling importance on-topic agree/disagree funny
- instead of witty, could be Well said/poorly said, but i think witty is better
- importance is Attend. importance and on-topic can both be either absolute (promote regardless of parent) or relative to sibling/parent context
- Agree/disagree can be objective or subjective and objective can be logical or factual
- some dimensions could only allow positive or negative evaluations. Funny only positive, logic only negative, maybe (un)kind only negative
- Poorly written because rambling, unnecessarily hard to understand. Well written can also be because Witty which is only positive
- should Z-score the evaluations given by each evaluator
- combination of the different reputation dimensions could be additive or multiplicative
- if it's additive, though, then attack resistance annoyance, because if only one total rep score, rep can migrate across domains
- some readers may want different weights on different scores, even negative weight on supposedly positive things e.g. funny. a simple UI might just allow each dimension to be positive,negative,neutral
- Typing of post, typing of link between parent and reply
- Open e.g. tags folksonomy
- Ui
- Specific fallacies?
- look at http://en.wikipedia.org/wiki/Stock_issues
- other community norms to maybe mention
- Real names, making ppl feel like real life
- "just flag it" community norm
- explicit codes vs norms vs code is law; Governance model for amending codes and code
- ontology over relations between pages
- allow individual authors to present a coherent set of pages which are 'their curated version' of a topic, organized and edited the way they like it, but then, via relations, allow them to be connected to other ppl's versions (other ppl can fork their pages, or can write their own pages and mark them as 'related' to a curator's version. Is this the same as just having a bunch of mini-wikis that are linked together, such that a RecentChanges? exists for any union of them? hmm, FractalWiki?
- FractalWiki? ?
- need to make sure that the site can contain 'political' discussion and 'meta' discussion while segregating this from the rest
Design space of moderation
Capped or uncapped
proposed page versions which are auto approved after time limit unless block (also conservative option to have no approval without affirmative approval)
forks, auto rebased
threaded discussion on discussion pages, option to mark comments as assimilated, which means they are deleted after time limit unless original author disagrees
blocks are supermajority votes, not vetos. they can be overcome. people can be expelled.
takes zero votes to suggest approval, and zero votes to block a suggestion (by zero votes i really mean infintesimal; anyone with nonzero reputation)
Links:
See also [1].
see also http://features.sheep.art.pl/BayleShanks