📚 node [[agora like]]

Agora Like

⥅ node [[betula]] pulled by user

Betula is a single-user self-hosted bookmarking tool for the independent web. It is simple to run and use. I started making it at the end of 2022. It is my main project currently. When I program, I usually program Betula.

=> https://betula.mycorrhiza.wiki | Website => https://fosstodon.org/@betula | Fediverse @betula@fosstodon.org => https://matrix.to/#/#betula-space:matrix.org | Matrix space => https://lists.sr.ht/~bouncepaw/betula | Mailing list about development (text only) => https://boosty.to/bouncepaw | I post screenshots of development on my Boosty

= Some Betulæ I know of The first one is mine! As you can see, the pattern of using links as the subdomain has emerged.

=> https://links.bouncepaw.com => https://links.flancia.org => https://links.danilax86.space => https://links.riskiwah.xyz => https://links.hd-dn.com => https://links.ihatereality.space/ => https://links.goldstein.rs => https://betula.trickyfoxy.ru => https://links.ndpi.io => https://betula.klava.wiki

Note that every instance is one-person only! Want to have your own Betula? Set up your instance. Having problems? Contact me.

= Relation to [[Mycorrhiza]] Both projects are part of the [[Mycoverse]]. What does it mean now? Not much, except it means that both projects are heavily connected ideologically and will be connected technically in the future.

Both projects use [[Mycomarkup]] as the only markup language.

= How to reset password? *. Open your Betula file with sqlite3. *. Run delete from BetulaMeta where Key like 'Admin%'; *. Restart Betula. //Is it required? *. Betula will prompt you for a new username and password when you open it.

= Simplest bookmarklet This one is obsolete. An advanced bookmarklet is built in Betula itself (visit the Bookmarklet page). But if you want it, here it is.

javascript:window.open(%22https://links.bouncepaw.com/save-link?url=%22+window.location.href+%22&title=%22+document.title,'_blank')

Change the URL with your own.

Read more about the bookmarklet: => Betula bookmarklet

⥅ node [[codex-editor]] pulled by user
⥅ node [[cosma]] pulled by user
⥅ node [[federated-wiki]] pulled by user

Federated Wiki

Federated Wiki

I had known about Federated Wiki for a while, hearing about it through IndieWeb originally and Wikity. But I never really grokked or explored it.

I then started getting in to personal wikis in 2019.

And then in 2021 after reading the chapter on Federated Wiki in [[Free, Fair and Alive]] and [[Mike Hales]] posting on social.coop about how some of the neighbourhood features works has made me understand more about the exciting ideas it encapsulates.

I'm not yet using it because I'm happy with my wiki in org-roam but I'd like to explore Federate Wiki and its ideas more, one way or another.

Federated Wiki sites share pages circulating within a creative commons. A single-page browser application can read from many sites at once and save changes in that browser. Users who host their own sites can login there to have their edits shared back to the federation as they edit. [http://fed.wiki.org/view/welcome-visitors website]

FedWiki is the next wiki-generation. It is a [[software]] that allows everybody to create individual wiki pages while circulating its content in a global - federated - environment. It opens multiple paths for individual knowledge organization while demanding equal responsibility in creating a knowledge [[commons]] . This knowledge commons emerges out of thousands of wiki sites people freely contribute to.

In short: FedWiki provides an [[discrimination-free infrastructure]] that allows for co-creation in diversity.

"Just as the wiki changed how people write, FedWiki will change how people work." (Ward Cunningham)

YOUTUBE 3nB8ml6UowE Keynote by Ward Cunningham, May 19th2015. [http://lanyrd.com/2015/writethedocs/sdmwxk/ html]

Catalog of federated wiki sites with domain names for page titles and brief descriptions tuned for search.

We publish federated wiki software as a Node.js package ready to run on a variety of platforms. This is usefully run on a personal laptop or an industrial server in the cloud. Most people get started by joining a community and launching sites and/or servers with their help. The server software supports a multi-tenant "farm" option useful for small groups or heavy users. [https://www.npmjs.com/package/wiki npm]

A community of open-source developers maintain both the client-side and server-side applications most frequently used to browse and edit pages. Pages themselves are composed of paragraph-sized items of various kinds. This same community provides a core set of plugins for rich content pages and a variety of experimental plugins that push boundaries of web computing. [https://github.com/fedwiki github]

Ward Cunningham started the federation in 2011 with a workshop project called Smallest Federated Wiki or simply SFW. The data visualization and sharing mechanisms were supported by Nike's Sustainable Business and Innovation group. Early history has been documented in a series of video screencasts. Search for "video".

⥅ node [[fedwiki]] pulled by user

FedWiki is the project of a federated [[wiki]], or a federation of wikis, led by Ward Cunningham, the creator of the first wiki.

I generally dislike FedWiki for its JS-heavy unintuitive and non-robust UI, poor support of mobiles and bad UX. It was kinda easier to find content to read on a //classic wiki//. Not sure about editing, you can't edit someone's fedwiki, you gotta set up your own to publish your forks of pages.

The community is mostly puzzled with adding more and more plugins to the ecosystem. I sometimes visit their meetings. Great people, I like their company! Added in 2023: I no longer visit the meetings.

Another thing to dislike about FedWiki is their dialect of [[Markdown]] which is barely compatible with Markdown at all, it is actually closer to [[Gemtext]]. I hate that they have the audacity to call it Markdown. Just give it a name! You sure made markups before, Ward, don't be shy.

Despite my dislike, the project is still respectable. First of all, it is ten years old. This is impressive. Also, that paned interface is cute. See [[Cartographist]] for a similar approach.

And never forget what they did to wikiwikiweb. Slaughter.

= Links => http://about.fed.wiki/view/welcome-visitors/view/about-federated-wiki | An attempt at explaining what it is

=> https://www.freefairandalive.org/read-it/#8

people using Fedwiki sites are like gardeners or farmers. They can plant as many fields or gardens as they want, and reap the harvest from their own Fedwiki, but anyone else can also use someone’s harvest to enhance their own fields and gardens. Instead of toiling under a regime of private, competitive exclusion, the system encourages cooperative gains through commoning

=> https://wiki.cafe FedWiki hosting.

FedWiki

about federated wiki

Smallest Federated Wiki Goals

  • Demonstrate that wiki would have been better had it been effectively federated from the beginning.
  • Explore federation policies necessary to sustain an open creative community.

I very much like FedWiki and [[federated wikis]] as a principle.

However, a downside of FedWiki (as far as I understand it) is that it is one platform, one tool, that facilitates the federation. A monoculture.

I would prefer a more distributed, protcol-based approach. [[Agora]] works in this sense as each individual can write their garden whichever way they see fit, and just needs to fit in to some accepted formatting protocols to be aggregated.

See also the [[IndieWeb]] approach, where the onus is less on aggregation and more on a certain protocol of communication.

See [[Interlinking wikis]].

FedWiki does seem to offer much simpler actions for copying content from one wiki to another. Agora doesn't have this built in as such. IndieWeb maybe more so (retweets, quotes, likes, etc, are catered to through webmentions)

Functionality

All content posted on Fedwiki sites is automatically licensed under a Creative Commons Attribution-ShareAlike 4.0 license upon publi- cation — meaning that it is “born shareable” the moment someone publishes it, making it available to the federation of sites.

[[A Platform Designed for Collaboration: Federated Wiki]]

The Fedwiki recordkeeping “journal” tracks who has posted what, so authorship can be chronicled even if people make mashups of someone else’s content.

[[A Platform Designed for Collaboration: Federated Wiki]]

The Fedwiki commons does have one vulnerability to outside control that it has not, as yet, been able to evade: the authentication of digital identity. Because of the complexities of providing a commons-friendly alternative, Cunningham and his colleagues have relied on the identity systems developed by Google and Facebook that function as a default for many sites on the internet.

[[A Platform Designed for Collaboration: Federated Wiki]]

Criticism

⥅ node [[massive-wiki]] pulled by user
⥅ node [[mycorrhiza]] pulled by user

Mycorrhiza is a wiki software I have been developing for some time. Go [[https://mycorrhiza.wiki]] . See [[микориза]] for more information in Russian.

⥅ node [[pubpub]] pulled by user
⥅ node [[roaman-agora]] pulled by user
⥅ node [[roamanpub]] pulled by user
⥅ node [[solid]] pulled by user

Solid

Social linked data.

As separate markets for data and apps emerge, Web development needs to adopt a new shape ◆ Most Web applications today follow the adage “your data for my services”. They motivate this deal from both a technical perspective (how could we provide services without your data?

Paradigm shifts for the decentralized Web | Ruben Verborgh

Interesting article on the Solid (Social linked data) platform. It describes a lot of the decentralisation concepts that are explored and implemented in the indieweb movement (surprised the article doesn’t mention indieweb, in fact, given the W3C link), but comes at it from a Linked Data angle. The language around markets and competition doesn’t really appeal to my personal politics, but good to see the philosophy of moving away from centralised silos being explored in different ways.

I feel like Solid, [[ActivityPub]] with a generic server and C2S, and [[Indieweb]], are all kind of chipping away at the same thing. You have all your data in one place (either self-hosted or someone-else-hosted) and you decide which apps you want to let interact with it.

Saturday lunchtime Tim BL gave a talk on Solid. People were queueing out the door to get in. I caught some of it on screen but not loads. When Tim talks about it it sounds pretty exciting and positive. If you go to the Inrupt website it sounds like corporate newspeak. I fear that venture capital will never truly want what is best for the world on general, just whatever lines the pockets of the investors.

#mozfest #solid

How solid is Tim’s plan to redecentralize the web? - Irina Bolychevsky - Medium

I really like the [[Personal Data Store]] concept. You own your data, and you choose to let apps interact with it for your benefit. It’s pretty much what the IndieWeb is doing (though perhaps for the more limited subset of things that don’t need verified claims).

I don’t like the commercial nature of most PDS offerings (including Solid now).

Either way, some good general food for thought in this article.

⥅ node [[yubnub]] pulled by user

Yubnub

📖 stoas
⥱ context