 | Federated Wiki | 125 Members |
| General Federated Wiki Discussion | 10 Servers |
| Federated Wiki | 125 Members |
| General Federated Wiki Discussion | 10 Servers |
| Timestamp | Message | |
|---|---|---|
| 7 Nov 2019 | ||
| 02:21:33 |  mike_hales | In reply to @mike_hales:matrix.orgTo the Loomio 'Open App Ecosystem' thread, I added a note on fedwiki in the context of a wiki on 'commoning' http://lowimpactcommoning.federated.wiki/view/welcome-visitors/view/commoning-for-lowimpactorg/view/further-notes/view/wikis. Would be glad to get comment on the commons/fedwiki relationship? |
| 15:42:11 |  Robert.Best | everyone here already seen this? https://larrysanger.org/2019/10/introducing-the-encyclosphere/ Seems fedwiki is already most of what being pointed at. |
| 8 Nov 2019 | ||
| 03:17:02 |  Ward | Larry says, “There’s never been anything like this. But if we get together, we can build it.” |
| 03:18:04 | Ward | Should we tell him? I don’t think he would listen. |
| 10 Nov 2019 | ||
| 02:31:56 | Ward |  image.png |
| 02:32:08 | Ward | The Present Plugin now offers a handy Peer Activity page accessed through the footer's hamburger menu. This was conceived as a "roll call" for classroom applications but will work well for hackathons or just general supervision of farm sites. |
| 02:32:28 | Ward | The 1.0 implementation reads the neighborhood sitemaps as they are loaded client-side. However, when all of the sitemaps are on the same machine as they are in this case we should probably retrieve all of the dates server-side and thus speed up display for large peer groups. |
| 16:58:34 |  christopherreay | In reply to @Robert.Best:matrix.org I read it. it sounds like most of the decentralised stuff out there "all we need is a solution to this and the world will change". I get that you are talking about fedwiki, but I'll interested in a more specific analysis of the idea of a... well known group that publishes formats for wiki articles, and had marketing dollars behind it, and formats for sourcing. is that what Larry means? maybe I'm missing the point here, I'm not good when it comes to the general public |
| 17:53:46 | mike_hales | Gradually easing into writing in fedwiki . . the experience feels quite close to blogging. Is there any thought on blogging-type relationships between wiki-writers, and whether wiki might support them - for example with functions like notifications? |
| 19:15:49 | Ward | mike_hales: I understand the blogging feel to the degree that I understand blogging. A difference might be that the accumulation is aligned with subjects rather than the calendar. More like currating than broadcasting. There is also the "fork" which means you take my words, call them your own, and make them fit your experience. This more than just quoting, it can lead to the continuous improvement associated wiki when wiki is working well. |
| 19:18:09 | Ward | Are you writing in public? With one mention from someone we scrape we will be indexing your work too. See Federation Search on the footer's hamburger menu. |
| 19:22:57 | Ward | The closest we've come to notification is Complementary Notice on Fork. http://ward.asia.wiki.org/complementary-notice-on-fork.html |
| 19:29:48 | Ward |  image.png |
| 19:31:06 | Ward | This news from Slack. I've always thought we would have pop editor commands but never got around to coding them. (Each plugin would provide its own.) |
| 19:35:10 | Ward | I am also of the opinion that typographic features used randomly are actually a deterrent to communication. I mention this because Slack doesn't seem to care. Typography to them is just "sprucing up" your message. Presumably your message alone is uninteresting as I've found corporate messaging to be. On the other hand, engineers solving a problem over slack are much more into the problem than sprucing up their text. |
| 11 Nov 2019 | ||
| 02:30:05 | Ward | Custom self-service registration home screens are on their way. |
| 02:30:40 | Ward |  image.png |
| 02:35:01 | Ward | This gateway into wiki can be programmed for each event by revising the "where we do and share" page. Administrators will be able to configure the Registration plugin with markup for what will be collected and where it will go. |
| 02:35:08 | Ward |  image.png |
| 02:40:39 | Ward | A single html file can be styled and then reused with each event by just moving it to the assets/home folder within an event specific site. |
| 02:40:45 | Ward |  image.png |
| 02:42:53 | Ward | The script we provide has two functions that asynchronously query and then render information provided by the host. |
| 02:43:00 | Ward |  image.png |
| 14:53:07 | Ward | It has been mentioned that my css could use some improvement. This is true. And it is an important feature of the custom home screen approach from which we don't want to retreat: one does not need to be an administrator to make a splashy splash page for their site. The describe() function is just a convenience for busy event hosts while the engage() function interacts with mechanisms that are under server administrator controls. See http://ward.asia.wiki.org/landing-page-registration.html |
| 15:27:49 | Ward | * It has been mentioned that my css could use some improvement. This is true. And it is an important feature of the custom home screen approach from which we don't want to retreat: one does not need to be an administrator to make a splashy splash page for their site. The describe() function is just a convenience for busy event hosts while the engage() function interacts with mechanisms that are under server administrator controls. See http://ward.asia.wiki.org/landing-page-registration.html |
| 16:56:57 | Ward | A note on terminology. We've called pages on different sites but with the same title "Twins". These pages are often of the same parent and share some common history. I'm now calling sites (not pages) hosted on the same farm and nested within the same subdomain "Peers". The assumption is that a host as brought together colleagues to be peers for some purpose. An individual might be peers to many communities. If so, it would be helpful if they assemble on their "about us" page a roster of where else they write. |
| 16:57:49 | Ward | * A note on terminology. We've called pages on different sites but with the same title (slug) "Twins". They are often of the same parent and share some common history. I'm now calling sites (not pages) hosted on the same farm and nested within the same subdomain "Peers". The assumption is that a host as brought together colleagues to be peers for some purpose. An individual might be peers to many communities. If so, it would be helpful if they assemble on their "about us" page a roster of where else they write. |
| 16:58:44 | Ward | * A note on terminology. We've called pages on different sites but with the same title "Twins". These pages are often of the same parent and share some common history. I'm now calling sites (not pages) hosted on the same farm and nested within the same subdomain "Peers". The assumption is that a host as brought together colleagues to be peers for some purpose. An individual might be peers to many communities. If so, it would be helpful if they assemble on their "about us" page a roster of where else they write. |
| 13 Nov 2019 | ||
| 17:50:16 | Ward | Federated wiki among the tools for creative exploration. Join our video chat about this and other dev/user topics starting in 15 minutes. https://hangouts.google.com/call/vh8qSgMVs-k-qOFdtwDAAAEI |
| 19:04:51 |  Duke | IMAGUS hoverPictureZoom tiny.cc/imagusc <chrome tiny.cc/imagusf <firefox makes th.ai wiki/pix a bit faster.. imagus easy to use and ESC works nice to turn zoomedpic OFF fast :) |