Welcome to friendika - I ask questions

general advice to my sentences:

if it does not make #sense immediately, consider it a #koan and search for "the way"

@ggoogi: "Not gonna get into 'chaos theory' here, but I do see it everyday. "

me: "please make some screenshots then" 

#systems

my current conclusion about being #online - use real #identity + #publish in #free #licence 
you could change my conclusions if you wish  

http://www.skilledtests.com/wiki/Blog:Observations/easier_access_of_your_data

#open

#thoughts about what #wikiversity (could be|is):

points to investigate, #interaction aspect, page-only-focus... 
#wiki 
http://en.wikiversity.org/wiki/User:Erkan_Yilmaz/observations#in_progress

Git is hard at the beginning but it is worth.

Scenario:
1) I read an online book (fork) and find a typo.
2) I fix it (patch), and, in my version (branch) of the book, this should show instantly.
3) My fix should be available (pull request) to be "incorporated" (merged) into the main book (master branch).

I think this is the kind of work to a backend based on git. Git relies on hardlinks and it's very "economic" about harddisk space. And it's fast.

(bare) Git is too hard for "normal" people. It has to be a good system (good interface, and everythig) based on (at least like) git.

This merge problems can be circunvented with a well designed system. But, I think this kind of system doesn't exist yet. So let's keep an eye on the options. Thanks for your tips.

trying to get hold of everyone from the #2008 discussion, via twitter (1) + #wikiversity talk pages

(1) https://twitter.com/#!/Erkan Yilmaz/status/168927160038465536

@cormaggio Do you mind sharing your #experiences with #PLE since 2008?


(1) http://en.wikiversity.org/wiki/Wikiversity:Colloquium/archives/February_2008#Wikiversity_as_a_Personal_Learning_Environment

(2) http://en.wikiversity.org/wiki/Wikiversity:Colloquium#Personal_learning_environment_.28PLE.29_retry_question_after_4_months

another thing against #git enabled #editing is: needs setup + sometimes merge problems appear (had this 2 times recently)

for #Mediawiki: I think these 2 #extensions could be for you:
a. Extension:FlaggedRevs (1) - more features, used in some #Wikipedia
b. Extension:Approved Revs (2) - simple, but effective I think

the git editing: I am currently doing also with #Openadvice #book (3)
works for me with someone adding teh pull request, but I guess for newcomers would be not so satisfying experience

(1) http://www.mediawiki.org/wiki/Extension:FlaggedRevs
(2) http://www.mediawiki.org/wiki/Extension:Approved_Revs
(3) https://github.com/lydiapintscher/Open-Advice

@Erkan Yilmaz I would love your feedback about this issue. My main reason to have such feature is for trying to make a book!

The book would be open for anybody to read and to "suggest" modifications (fix typos, or even comment about something wrong). But the author needs to approve them. It would be great also to have such suggestions visibles too until rejection/approval, so that 2 people don't loose time suggesting the same thing.

Perhaps doing a book colaboratively with an "editor" role "releasing" the "official" version.

I can't help thinking about something 'git' based. But, if MediaWiki has a plugin, it's better to follow the flow.

search results for: personal #learning environment (4 months ago + today): 

http://en.wikiversity.org/wiki/User:Erkan_Yilmaz/observations/2011_October#Google

#ple

Knowledge tree: will have a look, thx again

Thanks, I'll look into #GNUpedia + #Nupedia

Yes, the limited access for changing an article is a way (with identified accounts).

I guess the steps for a "normal" peer review could be adapted easily.

Maybe wikis don't fill your requirements, and perhaps something like http://www.knowledgetree.org/Main_Page might be better for your needs?

I do believe I might disagree, both philosophically and technically. GNUpedia and Nupedia both failed because of the formal review process, maybe you can learn something from the history of these projects?

By combining Mediawiki with a directory service, wiki view and page write access, and a formal review process that requires reviewers to have the article under review's RSS-feed on their bookmark bar in their browser, then I think you can get quite far - actually writing the articles and reviewing them.

The catch is formatting, though LaTeX and a lot of other things can be supported, and LibreOffice with wiki export should probably be investigated.

hnet - experimental #decentralized + anonymous #database

spreads #data across non-traditional #storage engines
(e.g. #images, gists, pastebin, #twitter streams, #irc, ...)


By #design: it's not reliable, fast, or consistent 

https://github.com/hookio/hnet#readme 

found via @unhosted

thanks + OK (setting up one is a future option)

I intended to find some #wikis using a kind of #formal #review #process for articles (#wikipedia certainly is not)

to see how they did it, what #problems they had and such...

background info (in #German): (1) some people want to initiate a #project with #wikiversity


(1) http://de.wikiversity.org/wiki/Wikiversity:Cafeteria#Anfragen von Wissenschaftlern .2F Wikiversity als Forschungsplattfom.3F

Mediawiki extension by the Wikimedia foundation, version 5 in beta

https://www.mediawiki.org/wiki/Extension:ArticleFeedbackv5

I haven't used it myself, so if you try it, please share a review.

Who knows a !wiki that uses some kind of #peer #review process ? Found so far #scholarpedia (and some others, unclear): 
http://skilledtests.com/wiki/Wikis_and_reviews 

#wiki

Erkan Yilmaz is now friends with Algernon Whistlewright

top5 artists from past 7 days:

鄧麗君 (Teresa Teng)

譚盾 (Tan Dun)

孫燕姿 (Stefanie Sun)

歐陽飛鶯 (Ouyang Feiying)

백지영 (Baek Ji Young)


#lastfm statistics: 80 plays for above artists

licence change for #wiki text edits: CC-BY-SA (before: CC-BY-NC) 

#creativecommons #more #open now

http://skilledtests.com/wiki/Blog:Observations/licence_change_for_wiki_text

To be steeped in #natural history (Two Steps from Hell - Heart of Courage) 
8 min #video

only 167 views, but worth more actually
via @Bob Mottram 


http://www.youtube.com/watch?v=9nmBXt5h3gE

I love friendica bugs #irony

♲ Bob Mottram

articles on #nanotechnology (1):

2009: 87000

1991: 8000



nanomaterials often "... not yet usable on an industrial scale." (2)


(1) Nature Nanotechnology, October 2011

(2) Oliver Kraft, IAM, Karlsruhe in: lookKIT 04/2011, page 15

hint for #job seekers in #QA / #testing / ... :

page: Figures about test effort costs (1)
-> top10 visitor locations:
7 German cities (2)
Vienna (Austria)
Berne (Switzerland)
London (UK)


(1) http://skilledtests.com/wiki/Figures_about_test_effort_costs

(2) Frankfurt am Main, Munich, Stuttgart, Bonn, Cologne, Dusseldorf, Berlin

Erkan Yilmaz is now friends with fabdo dostmusik

@Aysemiin boğmayı dene hele Idiots: yok yahu, #wiki link var mı bilgiden? bir de ricam var: #kore den aynı şeyleri araştırıyorum arada sırada (1) bunlardan başka bildiğin varmı ?


#language #korea #turkey 

(1) http://skilledtests.com/wiki/Korean_language

re: https://twitter.com/#!/Aysemiin/status/165434068878635008

what I don't like right now? a #browser which has a #memory #leak #thisuserisnotamusedrightnow

@Aysemiin haklısın ama bakıyorumda hoş gecmiş zaman, bir kac tavsiyen varmı onlardan? 

re https://twitter.com/#!/Aysemiin/status/165429279931371520

@Aysemiin ne yaptın ki o kadar cabuk bitmiş? tek müzik mi dinledin yoksa?  

re: https://twitter.com/#!/Aysemiin/status/165424885684899840

!wikieducator has >49.5 mio views since 2006 February #wiki #wikieducator

before a #wiki disappears save it: currently 139 wiki #xml dumps http://code.google.com/p/wikiteam/downloads/list

my good deed for today: bring #orexio to #unhosted

StatMediaWiki (interactive version 0.1.7) is working better now  #mediawiki #wiki #analysis

http://www.skilledtests.com/wiki/Blog:Observations/exploring_StatMediaWiki_-_collect_and_aggregate_information_about_your_wiki

more details: http://developer.pardus.org.tr/people/ozan/blog/?p=144

What happens when #government gets involved into #opensource #development? example #Pardus - a #Turkish #Linux distro 

http://liste.pardus.org.tr/pardus-devel/2012-January/002345.html

@parlamentum you should have asked who is #authorized to answer those questions + insist on #meeting them or get their #contact info  

re: http://parlementum.net/conversation/824684#notice-903588

I'm in a situation where I need at least one more #hand thinking about  old #university lecture #ubiquitous #computing OR I'll just take a #tape and "pin" that thing on the backside of my hand or hang around my neck...

I need to figure out how to fully mirror my wiki locally.

What's wrong here (1): #men crying with specific voice range? nothing, it's just 京剧 京劇 #beijing #opera - though there are better ones for 34mins Mei Baojiu, Méi Lánfāng 梅蘭芳 梅兰芳, Yu Zhenfei

(1) http://www.last.fm/music/Mei%2BBaojiu%253B%2BMei%2BLanfang%253B%2BYu%2BZhenfei/_/Broken+Bridge+%28Duan+Qiao%29

1. #google.com search (from Germany): wiki -ruby


2. OK: 1st link: #wiki page at #wikipedia 
3. still OK: indented, link to en.WP

4. 2nd indented link about: Steve Jobs 

What could be changed in this #scenario ?

Ah that's interesting. I didn't red anything about federeted wikis till now.

Perhaps the #federated #wiki concept can help in deletion #discussions - #fork as long and hard as you can

(1) http://www.skilledtests.com/wiki/Blog:Observations/What_is_a_federated_wiki

I always knew you're way ahead of time

ah because my friendika site is still in the future.

Thanks! I wonder why this didn't show up on my statusnet timeline?