FeedFerret - Revision history

Woozle: /* Tasks */ moved RSS discussion into plug-ins; further refinement

2011-08-24T22:11:42Z

Tasks: moved RSS discussion into plug-ins; further refinement

← Older revision		Revision as of 22:11, 24 August 2011
Line 34:		Line 34:
	==Tasks==		==Tasks==
	===core functionality===		===core functionality===
	* ~~Modify~~ [[mwsite:Extension:RSS\|Extension:RSS]]		* the core de la core: kernel which accepts massaged feed data and creates properly-formatted wiki pages
	** create a page for each feed item		** should also have some functionality to check for duplication -- some formats (RSS/Atom) are prone to this
	*** may need some checking to prevent duplication; desktop feed readers sometimes aren't so good at this		* Input plugins for each type of feed we want to be able to receive:
	*** should use an editable template, wherein we can specify basic [[Semantic MediaWiki\|SMW]] markup for each item		** '''[[RSS]]/Atom''' (move this out of core design and into a plugin)
	* Plugin architecture to allow multiple feed formats		*** adapt [[mwsite:Extension:RSS\|Extension:RSS]] or maybe start fresh with PHP XML functions
	** RSS/Atom (move this out of core design and into a plugin)		**** may need some checking to prevent duplication; desktop feed readers sometimes aren't so good at this
	** Twitter -- adapt from [[ThinkUp]]		**** should use an editable template, wherein we can specify basic [[Semantic MediaWiki\|SMW]] markup for each item
	** Facebook -- adapt from [[ThinkUp]]		** '''[[Twitter]]''' -- adapt from [[ThinkUp]]
	** Google+ -- start with data upload, see if there's an API or a way to page-scrape		** '''[[Facebook]]''' -- adapt from [[ThinkUp]]
	** other microblogs as requested		** '''[[Google+]]''' -- start with data upload, see if there's an API or a way to page-scrape
			** '''other microblogs''' as requested
			** '''[[Diaspora]]'''?
			** '''[[Orkut]], [[Friendster]]'''?
	* Unified feed-out for aggregated feeds-in		* Unified feed-out for aggregated feeds-in
			** needs to support transfer of media (images, audio, video)
			*** recipients may choose whether to copy or link, so media URLs need to be permanent
	* Feed-out for comments and categories		* Feed-out for comments and categories
	* On-site blogging, status posting		* On-site blogging, status posting

Woozle: forwarding around censorship

2011-08-22T01:31:01Z

forwarding around censorship

← Older revision		Revision as of 01:31, 22 August 2011
Line 57:		Line 57:
	** system for mapping node-wide categories on one site to node-wide categories on individual other sites		** system for mapping node-wide categories on one site to node-wide categories on individual other sites
	* rating system		* rating system
			* means of forwarding posts around censorship walls -- if the architecture is done right, any user should be able to post to any node that hasn't actively blocked them, without affecting who receives the post
	===aesthetics / polish===		===aesthetics / polish===
	* some way for users to choose tags from a list, as well as being able to add their own in a user-friendly way		* some way for users to choose tags from a list, as well as being able to add their own in a user-friendly way
	** possible types of tags: global, node-wide, and user-specific		** possible types of tags: global, node-wide, and user-specific
	* dynamic user interface (posts and comments appear without entire page reloading)		* dynamic user interface (posts and comments appear without entire page reloading)

Woozle: /* core functionality */

2011-08-21T02:26:52Z

core functionality

← Older revision		Revision as of 02:26, 21 August 2011
Line 44:		Line 44:
	** Google+ -- start with data upload, see if there's an API or a way to page-scrape		** Google+ -- start with data upload, see if there's an API or a way to page-scrape
	** other microblogs as requested		** other microblogs as requested
	* Unified feed-~~outfor~~ aggregated feeds-in		* Unified feed-out for aggregated feeds-in
	* Feed-out for comments and categories		* Feed-out for comments and categories
	* On-site blogging, status posting		* On-site blogging, status posting
Line 52:		Line 52:
	** choose who may receive notifications of your posts (if they want them)		** choose who may receive notifications of your posts (if they want them)
	** choose whose notifications you want to see		** choose whose notifications you want to see

	===refined functionality===		===refined functionality===
	* types of tags: node-wide, user-specific		* types of tags: node-wide, user-specific

Woozle: tasks

2011-08-21T02:21:24Z

tasks

← Older revision		Revision as of 02:21, 21 August 2011
Line 32:		Line 32:
	Other stuff to be done:		Other stuff to be done:
	* [[LiquidThreads]] needs to be callable from non-talk pages. They may be working on this, and they may get to it before I do. Probably their implementation will not be as flexible as what I need. Not sure what I need yet, but it needs to be flexible.		* [[LiquidThreads]] needs to be callable from non-talk pages. They may be working on this, and they may get to it before I do. Probably their implementation will not be as flexible as what I need. Not sure what I need yet, but it needs to be flexible.
			==Tasks==
			===core functionality===
			* Modify [[mwsite:Extension:RSS\|Extension:RSS]]
			** create a page for each feed item
			*** may need some checking to prevent duplication; desktop feed readers sometimes aren't so good at this
			*** should use an editable template, wherein we can specify basic [[Semantic MediaWiki\|SMW]] markup for each item
			* Plugin architecture to allow multiple feed formats
			** RSS/Atom (move this out of core design and into a plugin)
			** Twitter -- adapt from [[ThinkUp]]
			** Facebook -- adapt from [[ThinkUp]]
			** Google+ -- start with data upload, see if there's an API or a way to page-scrape
			** other microblogs as requested
			* Unified feed-outfor aggregated feeds-in
			* Feed-out for comments and categories
			* On-site blogging, status posting
			* Avatars
			* Visibility and notifications ("circles" in G+speak) -- this needs to be thought through, but the basic idea is:
			** choose who can see your posts
			** choose who may receive notifications of your posts (if they want them)
			** choose whose notifications you want to see
			===refined functionality===
			* types of tags: node-wide, user-specific
			** system for mapping node-wide categories on one site to node-wide categories on individual other sites
			* rating system
			===aesthetics / polish===
			* some way for users to choose tags from a list, as well as being able to add their own in a user-friendly way
			** possible types of tags: global, node-wide, and user-specific
			* dynamic user interface (posts and comments appear without entire page reloading)

Woozle: resolved redundancy; more explanation

2011-08-17T02:20:31Z

resolved redundancy; more explanation

← Older revision		Revision as of 02:20, 17 August 2011
Line 12:		Line 12:
	* the ability to export the commentary in a format which the original sources could incorporate in their on-site comments (like [[trackback]]s)		* the ability to export the commentary in a format which the original sources could incorporate in their on-site comments (like [[trackback]]s)

	~~All communication would~~ be ~~done using~~ [[open format]]s (~~pre-~~existing ~~where possible)~~.		The basic design of FeedFerret will be platform-agnostic (any device could be a node); the only component which must be specified in detail is the data exchange format.

			Since that is the key piece, it should use existing [[open format]]s as much as possible (starting with [[RSS]]/Atom), and where necessary extend an existing format rather than creating a completely new one.

	With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].		With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].
	==Prototype==		==Prototype==
	~~Since [[MediaWiki]] is what I know~~, I~~'m going~~ to ~~develop my prototype as~~ a ~~MediaWiki extension -- but the concept should be platform-independent; the data-exchange format is the key piece~~.		Although any device could be a node, I will be focusing on web servers initially as the fastest way to start creating a network.

	Since ~~that is the key piece, it should use existing~~ [[~~open format~~]]s as ~~much~~ as ~~possible (starting with [[RSS]]/Atom~~)~~, and where necessary extend an existing format rather than creating a completely new one~~.		Since [[MediaWiki]] is what I know, I'm going to develop my prototype as a MediaWiki extension -- but the concept should be platform-independent (as explained above).

	Software components to be adapted:		Software components to be adapted:

Woozle: notes -> prototype; explanation of why MW

2011-08-17T02:15:57Z

notes -> prototype; explanation of why MW

← Older revision		Revision as of 02:15, 17 August 2011
Line 15:		Line 15:

	With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].		With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].
	==~~Notes~~==		==Prototype==
			Since [[MediaWiki]] is what I know, I'm going to develop my prototype as a MediaWiki extension -- but the concept should be platform-independent; the data-exchange format is the key piece.

			Since that is the key piece, it should use existing [[open format]]s as much as possible (starting with [[RSS]]/Atom), and where necessary extend an existing format rather than creating a completely new one.

	Software components to be adapted:		Software components to be adapted:
	* [[mwsite:Extension:RSS\|Extension:RSS]]: RSS/Atom reader for MediaWiki -- mainly useful as sample RSS/Atom reader code. If it already stores the feed data, then that's a good start, but I think I want it to create a permanent wiki page for each feed item (for a number of reasons), and I doubt it does that.		* [[mwsite:Extension:RSS\|Extension:RSS]]: RSS/Atom reader for MediaWiki -- mainly useful as sample RSS/Atom reader code. If it already stores the feed data, then that's a good start, but I think I want it to create a permanent wiki page for each feed item (for a number of reasons), and I doubt it does that.

Woozle: notes

2011-08-17T01:39:40Z

notes

← Older revision		Revision as of 01:39, 17 August 2011
Line 15:		Line 15:

	With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].		With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].
			==Notes==
			Software components to be adapted:
			* [[mwsite:Extension:RSS\|Extension:RSS]]: RSS/Atom reader for MediaWiki -- mainly useful as sample RSS/Atom reader code. If it already stores the feed data, then that's a good start, but I think I want it to create a permanent wiki page for each feed item (for a number of reasons), and I doubt it does that.
			** This would be the first of several "feed interface drivers", eventually including drivers for [[Facebook]], [[Google+]], etc. so they can be at least read-only (and maybe writable somehow). Is there an API for G+ yet?

			Software components I'm currently hunting down:
			* a MediaWiki [[mwsite:Manual:Hooks\|hook]] that will let me periodically poll each RSS feed in turn (I know there is something like this which is triggered, I think, every time a page is viewed, because MW uses it to run jobs in the "job queue").
			* [[Semantic MediaWiki]] API. I will probably need to be able to output custom formats for the [[/talkback]] and other feeds.

			Other stuff to be done:
			* [[LiquidThreads]] needs to be callable from non-talk pages. They may be working on this, and they may get to it before I do. Probably their implementation will not be as flexible as what I need. Not sure what I need yet, but it needs to be flexible.

Woozle: prelim notes

2011-08-15T00:55:41Z

prelim notes

New page

<hide>
[[page type::proposal]] [[page type::design specification]]
[[thing type::software]]
[[status::design phase]]
[[platform::web]]
</hide>
==About==
[[FeedFerret]] is a proposal for web-based [[feed-aggregation]] software with some additional features not generally found in feed aggregators:
* the ability for users to comment on feed items
* the ability for users to categorize/tag feed items
* the ability to see what comments others have left on items, and respond to those comments in a threaded way
* the ability to export the commentary in a format which the original sources could incorporate in their on-site comments (like [[trackback]]s)

All communication would be done using [[open format]]s (pre-existing where possible).

With the addition of a [[blog]]ging feature, FeedFerret would then be one core component of a [[distributed social network]].