autonomous-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [autonomo.us] Introducting Strypey


From: Mike Linksvayer
Subject: Re: [autonomo.us] Introducting Strypey
Date: Fri, 3 May 2013 12:10:05 -0700

On Wed, May 1, 2013 at 8:17 AM, Danyl Strype
<address@hidden> wrote:
> On 30 April 2013 19:49, Michel Bauwens <address@hidden> wrote:
> I assume you are talking about wiki federation? I think this is really
> needed. Having multiple wiki sites, each with their own style and focus, is
> more flexible and resilient than one-wiki-to-rule-them-all, but it also
> results in unintentional silos and duplication of effort. Being able to host
> a particular *page* on multiple wiki sites, and keep them in sync, would be
> great. Some of the challenges are (in no particular order):
> * how do you deal with the fact that every wiki site has its own preferred
> way of formatting page?

WikiCreole! Markdown! HTML! :-/

For wikis-as-we-know-them, probably all run MediaWiki is closer than
agreement on an interchange format.

> * what happens when two (or more) people try to edit the same page on
> different wiki sites? Possible solutions, starting an edit locks the page
> across all subscribers for a set period of time, or some kind of Wave-style
> multi-user editing.

Or the easy to implement solution, dvcs, as implemented by gitit,
probably others.

> * security - spammers will love the fact that changing a page on one site
> (or hijacking the sync process) can change multiple sites. How do you
> prevent this?
> * how do you establish federation relationships for a page in the first
> place, and who should have the permissions to do it?
> * what syncing and security protocols would be used? How would they work?
> How is this decided?

Right, just using a dvcs doesn't fully address any of these.

> I don't think any of us *want* do be doing it on our own. We just start out
> that way, until we discover each other and start to collaborate. To that
> end, I've invited Jacob from CitizenWeb to join this list. I hope this is
> ok. If so, I will start inviting some people from other projects; Friendika/
> Red, my friends at Loomio etc

Yes, that's definitely OK. Thanks!

>> but our wiki is always available as meta-resource for everyone ... it's
>> not always necessary to re-invent the wheel and our wiki is pluralistic by
>> design;
>
> I'm happy to move my list to the page Michael suggested, and open it up to
> wider collaboration. Unless anyone has any better suggestions?
>
> The question remains though, how do we rate projects; technical criteria?
> level of adoption ("Prodromou's Law")? other criteria? Also, how would the
> evaluations we carry out as a research group translate into recommendations
> to developers and users?

I just discovered (and added pump.io to)
https://en.wikipedia.org/wiki/Comparison_of_software_and_protocols_for_distributed_social_networking
which needs work.

But one convention there, pointing to a list and noting the count of
servers running each application, would be one data point to include.
Other estimates like active users, message volume, could be useful
too.

It might be best to focus on that enwp list as it is probably seen by
lots more people than would be on any other site. That still leaves
detailed compare/contrast/mapping of technical details for elsewhere.
Probably also should be noted the existence of
http://libreplanet.org/wiki/GNU/consensus/protocols ... or rather its
current non-existence.

Mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]