Good thoughts, Dmitry. I will keep them in mind On Mon, Dec 26, 2016 at 10:51 PM, Dmitry Sokolov <[email protected] > wrote:
> Paul, > I think, Beaker is a huge step towards P2P Web. > Thank you for that. > > Most of my customers are working under Windows OS with files and folders. > Customers appreciate knowing how to backup and synchronise data because > that is critical for their business. Introducing "wiki" or anything else is > already too much for them. Ideally, the whole system must include no > elements to learn. > > What I can also to talk about is kinds of information business is based on: > > 1. paper documents > 2. electronic documents > 3. ideas / concepts / topics, and > 4. the way of organising all bits and pieces of information, above, > for quick access and reuse > > What they know is that > > 1. paper documents are stored in folders on shelves and retained for > certain number of years / months > 2. electronic documents are stored in computers and must be backuped > 3. ideas, etc., are stored personally. Ideas management is a pain and > better not to touch it > 4. overall, information management is a nightmare. Don't even talk > about that. Just give me a solution > > Bottom line: > I can't talk about wikis and wiki stores. > I can talk about ideas > > - stored individually, as single files, > - can be found as easy as the other (Windows?) files by their titles > and > - opened in future by either MS Word, or by a web browser. > - All files and folders can be easily synchronised, accessed and > restored as soon as needed. > > So, these are the frames I am trying to work in. > Your suggestions would be highly appreciated. > > Cheers, > Dmitry > > On Tuesday, 27 December 2016 13:44:03 UTC+13, Paul Frazee wrote: >> >> I can answer some of those Beaker questions >> >> Another question, are these site files easily accessible on the file >>> system? Or is this another "Local store"? :) >> >> >> It's a local store but that's kind of an open question. We could move the >> files into an easily-accessible path (eg ~/Dats) though I do lose a little >> bit of control then. For instance, it might be nice to implement >> transactional writes that fail if another tab writes the file concurrently, >> and I won't be able to supply that guard as easily if apps other than >> Beaker are writing to the files. >> >> That said, we do have some tools for this already. If you watch this >> screencast <https://beakerbrowser.com/docs/howto/use-bkr.html> you can >> see the `bkr` command that lets you do checkouts of dat sites to custom >> folders. We might be able to build on that. >> >> I'm interested to hear what people want/need. >> >> Also, can you run regular chrome at the same time as this? I guess that >>> might be more of a dev question. >> >> >> Yeah it's a different data directory. No collisions >> >> On Mon, Dec 26, 2016 at 5:52 PM, Arlen Beiler <[email protected]> wrote: >> >>> Jeremy, >>> I suppose Beaker has your spell checker that everyone wanted in >>> TiddlyDesktop :) >>> >>> Also, if you do implement a tiddler-based format, would it use the >>> standard data folder format? Or if you need a new format to get >>> authoritative file names, could it possibly be ported back to NodeJS? >>> >>> I have often thought about doing something like this with the TiddlyWiki >>> Dropbox saver, where it would sync individual files. >>> >>> Another question, are these site files easily accessible on the file >>> system? Or is this another "Local store"? :) >>> >>> Also, can you run regular chrome at the same time as this? I guess that >>> might be more of a dev question. >>> >>> Sounds quite interesting. >>> >>> Cheers, >>> -Arlen >>> >>> On Dec 26, 2016 06:17, "PMario" <[email protected]> wrote: >>> >>>> On Sunday, December 25, 2016 at 11:33:27 AM UTC+1, Mat wrote >>>>> >>>>> Very interesting. Only Mac so I can't try anything but just to make >>>>> sure I understand the implications for a TW context; >>>>> >>>>> - is the dat:// scheme not usable in regular browsers? (I find no >>>>> public site using it and basically no info on it outside of the Beaker >>>>> project). >>>>> - ...and therefore, would one need special browsers both to admin a >>>>> TW? ... >>>>> - ...and also to visit (merely read) a TW? >>>>> >>>> >>>> As Jeremy points out, the dat:// protocol is not usable with other >>>> browsers at the moment. ... But if it gets enough traction that other >>>> browsers would loose market share, they may implement it. ... (in the >>>> future) >>>> >>>> It's beta software atm. The version number is 0.5.x. So imo it's still >>>> early enough, to get some of the TW ideas into the project, which will be >>>> beneficial for both projects. >>>> >>>> -mario >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "TiddlyWikiDev" 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/tiddlywikidev. >>>> To view this discussion on the web visit https://groups.google.com/d/ms >>>> gid/tiddlywikidev/8072fd1b-2759-4dbb-bdc6-e464a1a99ee2%40goo >>>> glegroups.com >>>> <https://groups.google.com/d/msgid/tiddlywikidev/8072fd1b-2759-4dbb-bdc6-e464a1a99ee2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "TiddlyWikiDev" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>> pic/tiddlywikidev/n6yUdu2zHWo/unsubscribe. >>> To unsubscribe from this group and all its topics, 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/tiddlywikidev. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/tiddlywikidev/CAJ1vdSQLZ40YDxtTvmUc4ikS%3DHi71zDvpJLoAG9 >>> KNTnGOaCWOQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSQLZ40YDxtTvmUc4ikS%3DHi71zDvpJLoAG9KNTnGOaCWOQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWikiDev" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/tiddlywikidev/n6yUdu2zHWo/unsubscribe. > To unsubscribe from this group and all its topics, 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/tiddlywikidev. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/tiddlywikidev/b682c661-2593-4291-8584-3715d2e4e7c4% > 40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywikidev/b682c661-2593-4291-8584-3715d2e4e7c4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/CAD4FMeicObFY%2Bq1AkDr_e_y5DAMQ82MV3eQvZf-bVNp2G3uP6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
