Hi everyone,
It would be great if you could bring me all your feature requests, wish lists, and ideas over at Feature Requests Wanted! · TiddlyWiki/MultiWikiServer · Discussion #120 · GitHub
or do it in this thread, either one works. And if someone else posts a feature that you also want, please upvote it.
It can be literally anything as long as it is somehow even remotely related to a use case related to TiddlyWiki. 
Thanks,
Arlen
I want this.
Hi @Arlen22 - Here’s my wish list - tried to put a mix of things together.
A way to use it at work
I’m unable to use it on my main machine (work) - Windows Corporate Laptop without admin privileges. No Node, Bash, Git, …Something like either BOB.exe had (executable version), TiddlyWiki App (electron), TidGi, etc.
A way to access it when away from desk on my iPhone
I remain hopeful that some combination of MWS, Tiddlyhost, and Jeremy’s iPhone app will all bring this together someday. Until then, I don’t have access to enough technology to make this all work together like my competing software.
Easy way to delete bags?
This might be available now, but I remember when testing on a personal machine that I created a bunch of bags to test how it all worked, and then couldn’t figure out how to delete them. This drove me a bit nuts, I’m not even sure if I could rename them? I might be mis-remembering.
Somehow make large imports better
This isn’t directed at MWS specifically, but my main wiki has about 100K tiddlers in it. Some are “packaged” using plugins which makes import/export much easier, but my main note tiddlers (~ 25,000) need to be “normal” tiddlers and importing them means breaking into blocks of ~1,000 at a time. Given that I have a plugin with ~45,000 tiddlers in it works extremely easily, I suspect it has a lot to do with the import mechanism UI having to SHOW all the tiddlers on both sides. I would love an additional “blind” utility to filter-to-export and import large json files full of tiddlers in bulk.
Have you considered making a MWS publicly reachable to the internet?
I think this would solve your two first requested features (it did it for me).
My wishlist, sorted by importance:
A public roadmap that shows priority and tells which features are going to be developed first, (my intuition is that this discussion is the first step to build that).
Oauth as mentioned by @Scott_Sauyet. It would be great that once someone logs in with a google account, a user and a private bag were automatically created on MWS.
Allow MWS to act as a Sync Server, similar to what TiddlyPWA achieved, I find it really useful to have the option to work on your wikis even without internet.
From the Planned Features, my favourite two are the possibility to upload gygabite files, and instantaneous sync of changes.
Best,
I spend more time here these days than on GH discussions, so mine is here. I will spend some time thinking of others, but my first request is crystal clear in my mind:
Auth: I would love it if MWS could allow instances to pair with OAuth providers to handle logging in. Ideally, it would then also allow different views (in my case edit vs read-only, but possibly more sophisticated) to logged-in and other users.
I think any conforming OAuth2 provider would be fine, but perhaps we might need to restrict to those providing OpenIdConnect implementations, such as Apple, Facebook, GitLab, Google, Microsoft, Okta, and such. But if we just need OAuth2, there are many more options, including Amazon, Discord, Dropbox, GitHub, StackExchange, Wordpress, and so on. (Wikipedia List.)
I can’t say I’ve had the pleasure of trying out the MultiWikiServer plugin yet, but if possible, a prebuilt demo download would be nice.
Also, I have added the tag “MultiWiki” to the post, as I initially thought this was a post for any feature requests haha
I admit that I don’t even know enough to understand the landscape of technical thresholds here.
BUT: If users could gain managed-role editing privileges via university SSO authentication systems (such as for LMS or other portal/gateway institutional systems… Active Directory?) that’s THE HOLY GRAIL from my point of view.
If university students and faculty — who aren’t themselves running node.js or doing any other server-side geekery — can experience interacting with a TiddlyWiki collaborative project… that would change everything.
I really believe all my students would come out of my courses thinking not just “That professor curates a cool complex website” but “I need that tool!”.
That’s a somewhat different, but complementary, use.
What I described (in a language I’m sure Arlen understands, but probably should not have used in this forum without more description) is the way many websites let you “log in with Google/Facebook/Github/XXXTwitterXXX/etc.” The application doesn’t know anything about passwords, biometric scanning, etc., but offloads that work to a third-party provider. That provider verifies the user’s identity, and passes back some set of credentials, such as, perhaps, full name, email address, and the site-specific user id.
Integrating with your school’s identity provider would probably handle more than just user authentication; it probably also comes equipped with authorization, allowing you to assign both Emily and Tony to the course Metaphilosopy: Swallowing our own Tail, allowing Emily but not Tony to see the course work and grades for user id 1234567 and the reverse for user id 9876543. While a sophisticated use of the Oauth tool I was looking at could do something similar if it maintains its own list of permissions for users by supplier and id, that’s much more sophisticated then I was looking for, although, depending on the backend model of MWS, it might not be too hard.
I have no idea if this is possible, and my uninformed assumption is that it’s not possible, but I have quite long passwords to my single HTML file encrypted wikis and it feels very clumsy to type them often with one finger on the (Android) smartphones. If I can unlock the smartphone with the fingerprint, I would be very happy if it was possible to unlock the encrypted (with different passwords) wikis with just the fingerprint as well?
Ah yes, I wasn’t assuming that you were talking about the same thing, but it’s related enough to light me up with delight at the thought that TiddlyWiki might someday meet this challenge.
Actually, on a related note, I wonder whether there’s any chance that TiddlyHost might be able to integrate with google or other web-wide OAuth standards.
Then (again thinking big) if @simon could somehow enable a MultiWikiServer in TiddlyHost’s backend, sharing read/write privileges could become as straightforward as it now is with google docs and such…
Easy to say, but surely not easy to do!