Source Mode
| Editor Mode
fridemar's Tags
fridemar's Trails
WikiAnnotation means annotation of WikiPages.
The above text is copy of the introtext of the author, which is placed on a WikiPage. As WikiPages are editable by anyone (, if not special restrictions apply), it makes sense, to freeze essential claims of the authors in annotations itself.
( At the same time, this is a test, if DiiGo annotations on a WikiPage are preserved. )
Why is WikiAnnotation important for Online Communities?
Isn't Wiki enough?
Wikis allow inline annotations with normal wiki page editing?
-- FridemarPache
Note: Don't confuse an AnnotationWiki with WikiAnnotation. An AnnotationWiki is a repository for annotations material, to be pasted into rich text/link annotation dialogues, whereas WikiAnnotation makes only wiki pages the targets of annotations. Of course an AnnotationWiki can be itself the target of some WikiAnnotation.
The above text is copy of the introtext of the author, which is placed on a WikiPage. As WikiPages are editable by anyone (, if not special restrictions apply), it makes sense, to freeze essential claims of the authors in annotations itself.
( At the same time, this is a test, if DiiGo annotations on a WikiPage are preserved. )
A trail of
15 pages
This is a WikiTrail, to explore the fragmented activities in discussing, building and practising the OpenBusiness paradigm.
A trail of
10 pages
The following opensource applet comes from http://www.openprocessing.org/visuals/?visualID=661 Click on a square to reorganize the relational view.
A trail of
3 pages
DiigoTrailfireWikiCollaboration
The initiator of a group at Diigo with this name , which is at the same time a MixedCaseTag , opened this WikiTrail to stimulate collaboration between the two great social annotation communities and diverse wikis.
As this AnnotationEngine is not yet a TagWiki, the author presets all wiki words manually to GoogleSearchLinks.
This FireTrail started in the midst of some discussions on the DiigoGroupForum
The following pseudo-links are made to illustrate, how much work could be taken away from users of annotation systems, if the software itself transformed any WikiWord automatically into a LongTag or into a GoogleSearch. (Estimated less then 100 LOC Lines of Code)
AllLowerCaseModeForTagsAsOption:
alllowercasemodefortagsasoption
Hi Soulgrind:
I can feel with you and all the other peers, who are used to work in a relaxed way without the need to bother about the case. As long as Diigo is used for private tagging, why not.
But when subcommunities within the DiiGo sphere want to build SocialCollaboration , they need
precise tags. Think of distributed teams of C++ programmers, who are very sensitive in questions of case.
For non-programmers, please rethink the iPOD (TM) versus iBM (TM) example.
Your example could be used for differentiating tags by TypingShortCuts
Tech=HIghTech
tech=LowTech
In the author's view this is not at all "annoying". It is indeed very convenient.
It takes some carefulness of the SocialTagCommunityUser, but they will
learn the advantage of CaseSensitivity very fast, as soon as they see more examples. On the other hand, as Maggie pointed out, the (private) tags remain editable.
Even the PluralSingularIssue, well known
in the different WikiCommunities, would have a total different importance in TagCommunities.
"game" and "games" could precisely
differentiate between a site, devoted to one game only versus a site,
where more than one game is offered.
MayAllBeHappy
fridemar
A trail of
17 pages
![[Home]](http://usemod.com/meatball.gif)
WikiCommonWealth
MeatballWiki | RecentChanges | Random Page | Indices | CategoriesCurrently a lot of activities goes behind the scenes to take profit of the giant non-monetary wealth, created in the wiki communities. If the wikizen don't wake up and don't take reponsibilities for themselves, we might see soon trademarks like WikiCommonWealth, created and used by people, not necessarily engaged in intrinsic wiki contributions themselves. Hopefully the author is in error, supposing this. Or what would be even worse, there might be domains registered by wikizen, who have not found the nurturing open wikis, where they can CreateAndShareWealth, straight from the beginning and not by speculations and just "sitting it out". Another pitfall in the view of the author would be the initiation of StayPoor wikis, where only ideas of a Social Common Wealth are discussed, but where the wikizens themselves are only playing the role of zero cost workers.
If you search for Google:CommonWealth and Google:Wiki you get an exorbitant list of hits. Therefore some algorithm might have registered the domain: Google:WikiCommonWealth, because it is on the crossroads, where business promises to prosper. Pursuing the vision of a SocialCommonWealth, the author now registered WikiCommonWealth.info and *.biz to save, what can be be saved for wikizen, who want to collaborate in an Google:OpenBusinessWiki and not as invisible speculators.
Discussion The author puts this contribution in his blog, where additional cues can be found, to invite peers, to join the movement. -- [fridemar]
Watch: [1],[2],[3],[4] DiiGo(1), TrailFire:(1), Google:WikiCommonWealth
MeatballWiki | RecentChanges | Random Page | Indices | Categories
Edit text of this page | View other revisions | Search MetaWiki
Search:
A trail of
3 pages
Here the idea of a SocialCommonWealth was presented the first time in the WebHistory with a shocking WikiPage to create awareness.
Other peers are invited to join this approach.
E.g. they could buy and work on the "regional" domains SocialCommonWealth.eu, SocialCommonWealth.us,
SocialCommonWealth.cc (suggesting CreativeCommons).
..
There are a lot of adjacing domains to be bought and collaborated on.
By way of SocialSynergy, based on OpenBusinessWiki transactions, this creates wealth for all participating peers.
Other peers are invited to join this approach.
E.g. they could buy and work on the "regional" domains SocialCommonWealth.eu, SocialCommonWealth.us,
SocialCommonWealth.cc (suggesting CreativeCommons).
..
There are a lot of adjacing domains to be bought and collaborated on.
By way of SocialSynergy, based on OpenBusinessWiki transactions, this creates wealth for all participating peers.
A trail of
3 pages
The initiator of this trail thinks: It might be helpful for
- newcomers (he himself is one)
- the TrailFireProgrammers (here they can get convenient user feedback)
A trail of
11 pages
Advogato: Blog for mirwin
--------------------------------
The following quote tracks the first historical note on an OpenBusinessWiki:
"Wiki's are cool. Very easy to use. Very productive asynchronous transparent collaboration. Communites form. Good ones might be useful in designing tools to move large rocks.
The author made it a public Diigo tag "OpenBusinessWiki".
A trail of
9 pages
CreatingAndSharingWealth
MeatballWiki | RecentChanges | Random Page | Indices | CategoriesWasn't it George B. Shaw, who had the courage to formulate "Scarcity of money is the source of all evil"...
After reading the articles
- [What the MySpace generation should know about working for free]
- [Domain Wiki for 3 Million sold] which produced 365,000 Google hits.
Social Online Collaborating Communities produce a wealth of ideas, information, movies, programs, social relations, etc. but they usually work for free. Sharing of generated wealth is not in their MissionStatement. Counterexamples welcome.
It doesn't need "rocket science" to see, that (future) online communities, who additionally support economic integration, will be more attractive than those, who adhere to the principle: l'art pour l'art.
Some OnlineCommunity, or better CommunityServiceProvider, have in their TOS (TermsOfService) a StayPoor clause. Let's become aware of this suppression mechanism, so that CreatingAndSharingWealth communities can be easier detected and developed.
Discussion:
--- DiiGo:[1] TrailFire:[2] Google:CreatingAndSharingWealth
MeatballWiki | RecentChanges | Random Page | Indices | Categories
Edit text of this page | View other revisions | Search MetaWiki
Search:
Save
Cancel
Delete
Edit
Actions
(3/7)
Trail :
DiiGo TrailFire collaborationHint:
To relocate this mark, click and drag it to any location on the page
Title :