| 12 Feb 2019 |
| 04:47:46 |  Ward | Use export.json to copy a complete wiki.
curl -s http://found.ward.bay.wiki.org/system/export.json | jq '.|keys' |
| 04:54:55 | Ward | We think Glitch is interesting in its own right and an excellent first platform for our work. Anil Dash dropped in on one of our Wednesday video chats and answered all of our tough questions about sharing online. You should join us some Wednesday. We love visitors. Details here: http://fed.wiki.org/frequently-asked-questions.html |
| 05:02:29 | Ward | I wonder what it would mean to share a 3D immersive space in federated wiki. I have speculated before that navigating between places is not a strength of 3D. Maybe we could bring something of value to the experience.
http://ward.asia.wiki.org/wiki-nature-for-vr.html |
| 05:49:21 |  koolala | The new VR spaces are all about sharing Things instead of spaces. Like the elements of a federated wiki are the paragraphs, images, and factories for words- in VR you share sounds, characters, contraptions, scenery. Dreams gives people tools to make everything you can imagine in 3D from scratch kinda like a keyboard creates words from nothing.
Sharing Text is one of the most underlooked Things right now. You have all these objects being shared but not raw information. Like I imagine a federeated wiki where you can walk up to a person and drag a page off the screen in their hand onto the screen in yours. Or pulling info 'off of' a terminal. |
| 14:17:36 |  yala | In reply to @Ward:matrix.org
Use export.json to copy a complete wiki.
curl -s http://found.ward.bay.wiki.org/system/export.json | jq '.|keys' Had you seen https://github.com/antonmedv/fx before? It was new to me. |
| 15:47:07 |  paul90 | In reply to @Ward:matrix.org
sent an image. I've just publised the update to the map plugin. |
| 15:47:46 | paul90 | So, wiki-plugin-map@0.3.6 adds support for map overlays |
| 13 Feb 2019 |
| 14:55:25 |  eric | koolala, I remixed the glitch-hosted wiki and changed all of the .data configurations to .wiki. This has the effect of including the wiki content when the site gets remixed.
Here's the glitch view of that: https://glitch.com/~entertaining-sandwich
And here's the wiki view (along with some thoughts that occured to me about the choices I made when I chose the original configuration) |
| 14:55:39 | eric | https://entertaining-sandwich.glitch.me/view/welcome-visitors/view/content-remixed |
| 15:29:50 | Ward | Perhaps the status directory could remain in .data while the pages move to .wiki? I would feel more comfortable seeding a new site with existing pages if the start logic added a fork action to every page. |
| 17:01:09 | paul90 | maybe the wiki pages/status should stay in .wiki and any content for forming a specific community get copied into default data and copy that? |
| 17:02:34 | Ward | Michael Mehaffy and I met Monday to discuss how Sustasis Foundation should manage the online versions of their recent publications in federated wiki. Here is a video he made of the conversation.
https://www.youtube.com/watch?v=lLy0N0tOVVI&feature=youtu.be |
| 17:03:02 | paul90 | Q. when remixing is the source site known to the one being created? If so, having a list of pages, and forking them to the new site might be better. |
| 17:12:29 | eric | I have not yet learned what lifecycle events are invoked in a glitch remix operation. For example, I assumed that postinstall.sh would be something that only happens once, but seems to happen more frequently. I haven't investigated to really understand it. I don't know if the fork knows anything about the parent. Though, perhaps we could script something to ask the underlying git repo. |
| 17:12:56 | eric | Also, I'm going to be 30 min late to our hangout today. |
| 17:28:05 | Ward |
I'm Marshall Miller; I'm the product manager for the Growth team at the WMF
(https://www.mediawiki.org/wiki/Growth). Our team is working on increasing
the retention of new editors in mid-size Wikipedias. I wanted to chime in
because of the interesting things some of you are saying about what is
working and not working for new editors who are trying to learn. Our team
is always looking for input and perspectives from all parts of our
community, and I hope that some of you could weigh in on our team's work.
|
| 17:29:09 | Ward | An interesting post from Marshall Miller to the wikipedia research email list.
https://lists.wikimedia.org/pipermail/wiki-research-l/2019-February/006654.html |
| 17:32:05 | Ward | For anyone that doesn't get enough video chat on wednesdays I am in the zoom room now. https://zoom.us/j/818108478 |
| 17:36:57 | Ward | Last week we suggested writing about topics from the chat. I started one page but did not finish. It is still on my todo list as I think about it often.
http://ward.bay.wiki.org/evergreen-browser.html |
| 17:50:41 | Ward | Just tweeted: Federated wiki dev/user video chat starts in 10 minutes. Visitors welcome.
https://zoom.us/j/818108478 |
| 19:49:47 |  daviding | Really interesting discussion today, bridging the work that David Bovill has done in Livecode, comparing with Ryan Bennett's wiki desktop, and Eric and Paul's work on DAT. |
| 19:51:44 | daviding | I think (and would like to be corrected if wrong) is that all of the technologies write to the file system, so that if a group started writing locally, and did enough that they wanted to get an online host, we could FTP the files up, and save the work. |
| 19:53:17 | daviding | The concern for me is preservation of the Creative Commons licensing on authorship. Copyright isn't relevant when a person is editing on his or her own computer, but does become relevant as soon as he or she publishes onto a website and then fully joins the federation. |
| 14 Feb 2019 |
| 02:26:09 | eric | CC-BY-SA license is declared in the wiki client. It appears in the lower left corner of every rendered wiki page. As far as I know it is not represented in the underlying JSON. Should it be? |
| 02:28:39 | Ward | No. Federated wiki is a realization of that particular license. |
| 15:15:40 | eric | daviding, one of my favorite things about federated wiki is the simplicity of the data and persistence. It is just a collection of files that contain simple json objects. So scp and ftp and tar and rsync are all perfectly useful tools for moving the data around. |
| 16:11:43 | Ward | Michael Mehaffy has prepared a 15 minute "highlight reel" that is not only shorter than our conversation but proceeds in a logical order.
https://www.youtube.com/watch?v=EzS60DaltAU&t=21s |
| 15 Feb 2019 |
| 17:31:45 |  Robert.Best | Has anyone ever paired a fedwiki farm(s) with a more monolithic wiki? (something like a MediaWiki etc) Something where you compose and create within fedwiki, but then all the pages are aggregate into the monolithic wiki, and then that is almost the begginings of a talk page for groups that do want to try and converge on some sort of shared understanding together and publish one wiki together. Maybe where if there is only one page with a certain name on the farm, then it becomes the default page you see on the monolithic wiki... and if there are multiples then you are still able to see the alternative perspectives (maybe with the fedwiki view of the pages but with the whole farm in the neighborhood), but this group would be continually deciding who's page should be the default/most prominent in each case. (Using whatever decision-making process they choose) |
| 17:32:04 | Robert.Best | Redacted or Malformed Event |
| 18:08:45 | Ward | Robert.Best: Sustasis intents to aggregate and publish works authored initially in the federation. I can't see how they could administer a traditional wiki because they are just not that big and there are too many griefers on the modern internet. |
