Hello @Riz , because I could not find this in the documentation: Is Timmimi able to save both in a sidebar and on the web.
The reason I ask this is that I am building a Tiddlywiki notetaking sidebar extension which shall not reopen from the web every time I close the sidebar.
On the other hand, I use a server to share my notes between devices.
Hey, Currently parallel saving as you mentioned is not possible with timimi. Fundamentally, timimi does not alter what tiddlywiki does. It only takes care of the system side of things. What you are asking should be happening in the tiddlywiki side of things.
Hi @well-noted,
Well there is not much to say yet. So far only the icon is ready
But I just learned how mozilla a sidebar-addons could work.
As I do most of my work in the browser, some time ago I thought it would be great to have a notetaking sidebar. I was disappointed, how primitive the offers are compared to what would be possible in a tiddlywiki.
I just did an experiment with a “deepseek”-sidebar which also could be interesting for an ai-afficionado like you are. So opening and interacting with a webpage is pretty easy to realize in a sidebar you can test this with OpenInSidebar.
For Tiddlywiki the only catch is that it (unlike tabs) closes and reloads when you switch sidebars.
So it would be good to combine this with the file backups plugin in order not to be dependent on a server for the notes.
The next step would be a TiddlyWiki which gives us all necessary functions in the narrow space of the sidebar.
I think your streams rewrite will be important there too.
No.
There is an old PR PreferredSaver by xmaysonnave · Pull Request #4716 · TiddlyWiki/TiddlyWiki5 · GitHub, which has not been merged, basically TW code formatting was never fixed.
I did test the functionality once and it seemed to work.
This is not timimi. i don’t know about sidebar either. here is another tiddlywiki saving method. It can be saved both locally and on the server.
I do something like this in vivaldi’s sidebar. It does not reload the page each time the sidebar is switched.
Hi @well-noted cool, I think note-sidebars could be a thing to enhance user-growth…especially if they come bundled with an uncomplicated saving-option.
@Riz , @pmario and @tomzheng I think, I would prefer the easiest way to do this and I think this would be Mario’s mechanism to save in a folder in the downloads.
I think there was a sort of publish-plugin to save a public version parallely- but I do not find it anymore.
I’m not sure I understand your work-flow. When you say you’re saving to a server … what kind of server? Where?
In terms of losing your work when the sidebar closes, consider the official “Browser Storage” plugin together with Btheado’s “BrowserStorage” plugin. I use this with files hosted on TiddlyHost, so that work isn’t lost even if TH signs me out.
I think this is should an addon for newbies and experienced users who have a server.
This could be explained on the startpage of the sidebar.
It seems usefull to allow the users to load the wiki from the web with a preconfigured choice or a template page.
The Browserstorage-plugin is a very good idea. Browserstorage and server save parallely, don’t they?
Yes. But you have to test very well. I did some tests and it was not always consistent, when it should sync back to the server.
I guess that is the problem. We would need a good mechanism to untangle saves on server and browserstorage anyhow . It tends to multiply the multiple-device-problem .
And if I think of this closely it would be useful to either have a mechanism encrypting the upload automatically or a way to secure it via httacces on the server or anything alike. Any ideas?
There are several levels of encrypted communication in a client server environment.
- HTTPS … in general encrypts the communication data “in motion”. Which avoids “man in the middle attacs”. Configuring a public facing server for HTTPS is obligatory.
- Local Storage … is data “at rest”. If you want to read the browser local storage, you have to have physical access to the device. So the easiest way to block access there is strong OS passwords. If you need to protect your data if someone dismantles your hard drive from the PC you should use OS level encryption, which is completely transparent for apps and does not need any work for TW.
- Encrypted Local Storage … See 2). If you need encrypted local storage, because you want to — You will need to have a closer look at TiddlyPWA – The TW core does not encrypt local storage at the moment.
-
.htaccess
files are used by servers to create a “username” / “password” prompt if you want to enter the site. This is mainly configured by “proxy” servers, which are in front of a TW server. – This depends on how you did configure your server.
Hope that makes sense.