All in all, delete beaker browser for now and add it later when things are more stable?
On Mon, 15 Jun 2020, 18:29 PMario, <pmari...@gmail.com> wrote: > On Monday, June 15, 2020 at 2:22:14 PM UTC+2, Riz wrote: > > Also I have questions regarding DAT protocol. Does TW support headless dat >> server or just beaker browser? >> > > At the moment it's Beaker-browser only! > > I personally do see a lot of potential in the peer to peer DAT-protocol > ... Which is now Hypercore-protocol > <https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/>. > ... > > We have been a bit early, implementing a DAT saver, which should be > deprecated as soon as possible. It will only work using the beaker-browser > V 0.8.x ... As the version number shows, it's a beta version and the API > has been subject to change. ... And it did! > > The new beta is 1.0.0-prerelease.x, which is a completely different > concept to V0.8.0 ... Again: It's a completely different thing. Browser and > protocol wise. So the DAT saver won't work anymore. > > If Beaker 1.0 is shipped, the API is considered to be stable. See V1.0.0 > ... So they will have to be more careful, changing APIs in a compatible > way. > > As I wrote, the whole "workflow" has changed considerably. Beaker browser > now uses a "hyperdrive-deamon > <https://github.com/hypercore-protocol/hyperdrive-daemon>", that is > independent form beaker. But it's highly influenced by beaker. ... > > At the moment Beaker browser is the only usable GUI, that can talk to the > deamon. It abstracts most of the complicated things away, but it has its > own opinions how some workflows should look like. > > The rest of the utilities that exist are command line (CLI) based, which > is a no-go for most of our users. > > I am working on a new "single file" saver, that can use the new > Beaker-API. ... BUT the whole thing isn't very harddisk space efficient, > because it doesn't use anything of the "good stuff" that hyperdrive > <https://github.com/hypercore-protocol/hyperdrive> has to offer. > > So the first version, that makes sense for me, will separete the > core-js-code from html-content, which can be done in a save way, since > hyperdrive has a "built-in" versioning system. > > ... more to follow in a new thread, when the time comes! > > have fun! > mario > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/MpxrDwmt0S8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > tiddlywiki+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/ddd0ac3b-6a9c-4c9f-990c-68617410a5edo%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/ddd0ac3b-6a9c-4c9f-990c-68617410a5edo%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAO0b0pGjnYjHeYgFwqPoZkN6ad0hRwF_FOeR%3DXm_EJK%2BoavSvw%40mail.gmail.com.
