Ah, all the good old misconceptions about  NoteSelf arising again, makes me 
feel nostalgic, thanks google groups for effectively burring all the 
valuable information where nobody can find it.

Let's split this by parts, and try to answer all the 
questions/misconceptions. Don't expect them to be in order.
NoteSelf (NS) is my own little project, hope everyone is clear about that. 
As the main page states, it arises from my own necessities and therefor it 
addresses them the way I like it. Sometime after it's conception I thought 
that it will be cool to share my custom solution with the community on an 
easy manner and that is when NoteSelf come out.

The main objective of NS is to bring my custom solution in an easy way for 
the masses, and that will always be. I am a very active person with dozens 
of projects, leaving me little time to support custom requirements. I want 
to provide general solutions, and leave the rest to advanced/adventurous 
users on their own. 
That said, I always targeted *modularity *(more on this later)*, 
flexibility and compatibility.* This means that the required ingredients 
are already out there, but I will only cook them to build NS the way I 
think it should be. There is nothing stopping anyone else from picking 
those ingredients and cooking them on a different way, but expect little 
help from me.

@Danielo - is the mechanism for automatic saving to browser possible to 
> turn into a plugin for TW? I.e a plugin that can be installed like any 
> other plugin.


That will never happen, I mean, me working for turning the automatic saving 
mechanism into a plugin. The reason ? Because it always was. Please read 
below.

I want to remark once again that NS is a tiddlywiki *edition*, not a 
plugin, nor a tutorial neither a showcase. *It is a product.* But a product 
built the way I think it should be: making the different parts as general 
as possible and add mixing them the way I want.  This is very noticeable if 
you ever open the plugins tab of NoteSelf. You will se the following ones:

   - PuchDb library. Yes, even something as important to NS as the pouchdb 
   library is a standalone plugin. Do you want to experiment with it ? GO for 
   it! The heavy lifting has been already done
   - TiddlyPouch. Where everything started. Everyone seems to forget about 
   it in favor of NS edition (which is exactly what I wanted). This was my 
   original idea, a saving plugin implementing the PouchDB saving mechanism. 
   It turned out that it was confusing for 99% of the users.
   - NoteSelf online configurations. A collection of configurations 
   specific for the online version of NS
   - NS Plugin library. Not listed as a plugin, but it actually exists. The 
   reason ? Because NS cares about security, and it is served through https. 
   At that time, TW didn't support https for the plugin library, so I had to 
   build my own.

Not to mention a collection of other non-plugin tiddlers that improve the 
NS experience. NoteSelf components are spread across 5 ( five! ) different 
repositories

   - Pouchdb TW plugin
   - TiddlyPouch
   - Noteself page and online edition, containing all the configurations 
   that I want to be part of NS edition
   - Android application 
   - Cloudant configurator, a small tool to help people configure their 
   cloudant accounts for multi user environments.

I work really hard to keep those repositories consistent and properly 
linked. That's why when someone asks me to split NS into pieces I get so 
against. It already is ! I can't split it more than it is without losing 
the control.

Several of the most common problems have been fixed recently, so I 
encourage everyone that was interested to check again. For example:

The only problem is what happens is if your browser fails, OR you want to 
> transport to a new one. Add some kinda backup of whole TW and you are 
> really there.
>

That is already a reality. All you have to do is click on the save button 
and boom, you will get an HTML snapshot of your wiki with the entire 
collection of plugins directly baked into the HTML. The cool thing is that 
you can open that file and continue saving to the local database since it 
also includes all the required plugins. If this is not sufficient for you 
you will have to convince me that there are dozens of potential users on 
the same situation.  


If I hosted it then when logging in on a fresh browser its empty till the 
> NoteSelf details are entered because this info is stored in the browser and 
> not the tiddlywiki.
>

That is a know limitation and it will continue to be until I find a good 
and more or less secure way to embed that information on the exported file. 
Note that NS can handle several local databases talking to several remote 
ones. If  I allow one of them to be baked into the HTML and take precedence 
you will lose access to the rest.
I also want to make public that *the export section of the control panel is 
outdated*. It's something that I want to fix, improve and make more clear, 
but I have to find the time, or let someone with the will to help to find 
me, two very exceptional scenarios.


What this means is that I can't host a NoteSelf Wiki that anyone can view 
> and can be logged into for editing. 
> I'm not sure if I've missed the point somewhere or if I'm just 
> encountering bugs.
>

At some time, that will become much much easier, and you will not even need 
to host it yourself. 

Well, I only proposed to use TS as a storage. Does NoteSelf require a 
> separate database - isn't that what that TiddlyPouch/Couch is? I.e what 
> uses my local browser to store stuff?
>

Pouch is your local browser storage, Couch is a database just like Oracle 
or MySql and will always be remote. TS can not be used as an alternative 
storage because tiddlywiki only accepts ONE saving mechanism ( not to be 
confused with sync mechanism). At the very beginning I wanted to allow all 
kind of saving combinations, then I reached this limitation. So I keep my 
efforts realistic and instead of trying TW do something it is not designed 
to do, I focused on only  *remote syncing and reliable HTML download*.

 further installing it on my android was one of the most impressive 
> features with a dedicated Icon and saving capabilities. No need for nodeJS 
> or fiddly folders.


Glad you liked that feature, you're probably the first reported user (apart 
from me) taking advantage of this. Many thanks. 

With a little work I believe we can take the existing techniques CounchDB 
> and other savers and wrap a little logic around it to allow a single 
> instance be checked in/out enabling multiple users across time to work on 
> the same instance.
>

You are right about the possibility, but you are wrong about the amount of 
work. It is not little, it is bigger than I can handle in a short period of 
time.

I also think this is a opportunity for some degree of commercialisation, 
> which I think I recall you expressing an interest it. I would be keen to 
> continue the conversation on this, privately or in the forum.
>

I don't have any problem in discussing this publicly on the forum. Yes, my 
intention is to make NS a comercial product, but only to the degree that it 
can own itself. This means, that mean that it's expenses are fulfilled by 
it's incommings while allowing me to have a quality service for free at the 
same time.

Hopefully the situation is clearer now and everybody is happy with the 
answers.
I hope anybody feels dumb about asking, several of this questions deserve 
to be on the FAQ of NS( who reads the FAQs after all) and this google 
groups mechanism does not help neither.
I know I am not as active as I used to be. That's because NS is on a mature 
state, mature enough to fit all my needs. The same happens to TW, when 
someone has it configured to it's likings it stops reading and posting to 
this group. Hopefully there are some active members that points me here 
from time to time.

All the best to everyone.

Regards

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/53342c39-b917-4671-b5bd-429e29d24c92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to