TiddlyWiki VS Mediawiki

> What does ownership mean here?

It means owning the code and the data. With webapps, the code and data are hosted and owned, the users do not own the code, cannot run it independently. This is a clear dileneation between owner and user, and the owners can use that clear line to create artificial scarcity of various kinds. (The most popular being the subscription SaaS model). It's also easier to defend your IP since end users never see your binaries.

I like to make my software single html files whenever possible. People can just save them and run them locally. Havent met anyone who cares yet though.

I like that idea a lot, and I care. I think others care, but yes, it's a niche interest. Take a look at https://tiddlywiki.com/ for an example of a fairly successful project that uses the single html format running locally. However it suffers from limitations on File|Save which often requires a separate runtime of some kind to support.

Another project that approaches this ideal is https://redbean.dev/, @jart's tiny, performant, featureful single-file webserver. In this case the "single file" is a server executable + zip whose state must be updated on the command-line, but I think hits a sweet spot in terms of practicality, and a global minima when it comes to minimizing dependencies. (Redbean bundles SQLite and Lua so it's also possible to do through-the-web state updates as in a traditional webapp.)

My own project, Simpatico, aspires to be something along these lines. Eventually your browser tab is both a client and server process, connecting via websockets to other connected browsers, storing all state locally. I call this pattern "monomorphism", a play on the "isomorphic" javascript SPA. The server[2] is currently written in ~1 node file, but eventually I would like to port to redbean (and greenbean, the websocket version of redbean, but it isn't quite ready yet). The server grew several features to support a fast, practical BTD loop using markdown[1], and safe, performant execution on the public internet[2], but ultimately I'd like to pare it down to serving a single html file and allow the connected clients to provide all diversity of experience. I've used it to explore all kinds of browser apis, from crypto[3] to svg[4] to writing my own libraries (combine[4] and stree[5]). And it's all running locally, and easily hosted on a $5 VPS, and its all open source.

1 - https://simpatico.io/lit.md

2 - https://simpatico.io/reflector

3 - https://simpatico.io/crypto

4 - https://simpatico.io/combine

5 - https://simpatico.io/stree

I use TiddlyWiki. It's a portable editable wiki that doesn't require a web server or web hosting. You open it from your computer, edit it, and save it. You get all of the linking that you'd expect to see in a wiki, and it's super readable and easy to use.

It is a single-HTML-file TiddlyWiki instance that runs in a web browser (offline as well as online), meant to be downloaded and stored wherever suits you best. Everything that you see when working in BASIC Anywhere Machine (everything that makes "BAM" work as an IDE and all BASIC programs) exist in the one HTML file.

TiddlyWiki still works as intended: https://tiddlywiki.com/#GettingStarted but there are so many different clients to run on. Mobile or Desktop ? What OS? What Browser?

This effort https://val.packett.cool/blog/tiddlypwa/ is remarkable as the mobile side of saving is not as robust as on the desktop side of things and there is a scaling limit on performance as the number of tiddlers grows. Also the syncing between tw documents between different desktop/mobile clients can be a challenge with diffing.

Since then I've moved back to plain vanilla vim for a wiki (map gf :tabe ) but tw.html is still good for data other than plain text and TiddlyPWA https://tiddly.packett.cool/ is a great effort to revisit TiddlyWiki again.

You should check out TiddlyWiki as it’s designed around the concept that small linkable notes are the best way to organize.

https://tiddlywiki.com/

It’s html based so you can access it in the same way you would access a website but it can be locally stored. Saving is a bit tricky but there are multiple solutions detailed on their site. https://tiddlywiki.com/

Hi, you can use tw on nodejs with npm package tiddlywiki....

Wikipedia that runs on MediaWiki which is written in PHP. source code

MediaWiki

"https://ibb.co/0F2rWbG/logo.png", 'icon' => "https://ibb.co/0F2rWbG/logo.png",];## UPO means: this is also a user preference option$wgEnableEmail = true;$wgEnableUserEmail = true; # UPO$wgEmergencyContact = "";$wgPasswordSender = "";$wgEnotifUserTalk = false; # UPO$wgEnotifWatchlist = false; # UPO$wgEmailAuthentication = true;## Database settings$wgDBtype = "mysql";$wgDBserver = "wiki";$wgDBname = "wikipapadeluxe";$wgDBuser = "root";$wgDBpassword = "";# MySQL specific settings$wgDBprefix = "";# MySQL table options to use during installation or update$wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary";# Shared database table# This has no effect unless $wgSharedDB is also set.$wgSharedTables[] = "actor";## Shared memory settings$wgMainCacheType = CACHE_NONE;$wgMemCachedServers = [];## To enable image uploads, make sure the 'images' directory## is writable, then set this to true:$wgEnableUploads = false;#$wgUseImageMagick = true;#$wgImageMagickConvertCommand = "/usr/bin/convert";# InstantCommons allows wiki to use images from https://commons.wikimedia.org$wgUseInstantCommons = false;# Periodically send a pingback to https://www.mediawiki.org/ with basic data# about this MediaWiki instance. The Wikimedia Foundation shares this data# with MediaWiki developers to help guide future development efforts.$wgPingback = true;# Site language code, should be one of the list in ./includes/languages/data/Names.php$wgLanguageCode = "en";# Time zone$wgLocaltimezone = "Europe/Berlin";## Set $wgCacheDirectory to a writable directory on the web server## to make your wiki go slightly faster. The directory should not## be publicly accessible from the web.#$wgCacheDirectory = "$IP/cache";$wgSecretKey = "b564d730428f48d0882f0ae67283fc844ba41347848b4868501bdb524ff86342";# Changing this will log out all existing sessions.$wgAuthenticationTokenVersion = "1";# Site upgrade key. Must be set to a string (default provided) to turn on the# web installer while LocalSettings.php is in place$wgUpgradeKey = "d8e35fccd5b424df";## For attaching licensing metadata to pages, and displaying an## appropriate copyright notice / icon. GNU Free Documentation## License and Creative Commons licenses are supported so far.$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright$wgRightsUrl = "";$wgRightsText = "";$wgRightsIcon = "";# Path to the GNU diff3 utility. Used for conflict resolution.$wgDiff3 = "";# The following permissions were set based on your choice in the installer$wgGroupPermissions['*']['edit'] = false;## Default skin: you can change the default skin. Use the internal symbolic## names, e.g. 'vector' or 'monobook':$wgDefaultSkin = "vector";# Enabled skins.# The following skins were automatically enabled:wfLoadSkin( 'MinervaNeue' );wfLoadSkin( 'MonoBook' );wfLoadSkin( 'Timeless' );wfLoadSkin( 'Vector' );# End of automatically generated settings.# Add more configuration options below.

Do you mean Fandom wiki? You would want some kind of open source wiki platform. MediaWiki (used for Wikipedia) is probably the most popular and full featured.

It's all open source https://github.com/wikimedia/mediawiki

A little money, a little installation work, and this: https://github.com/wikimedia/mediawiki

This is overkill. The entirety of Wikipedia is made available for free download by the Wikimedia foundation, the code is open-source, and anyone can set up their own copy of Wikipedia on a normal PC with a big hard disk. Power this off a portable battery and solar panel and you have off-grid Wikipedia without any hardware hacking.

Last time I had occasion to use one - i used mediawiki