Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 31 million developers.Sign up
🛠Fix a bug which caused Beaker to freeze due to bad responses from the dat:// protocol. 💂Beaker now uses Chromium's process-level sandbox.
A few fixes and minor updates:
⬆️Upgrade to Electron 4.0.3 and Chromium 69 🔈Add "sound playing" and "muted" indicator to tabs 🔨Add
🛠Fixes to the Dat stack 🛠Various small fixes
🔨Fix issue with dat forking ("Make an editable copy") where files would not be copied.
🚀Performance improvements! We used the latest in ✨computing ✨sciences ✨to make Beaker run smoother than ever before. (We moved dat into its own child process.) 🆕Favicon editor. You can now draw your own favicons for your sites! Thanks @Septimus for this awesome new tool. 🔨A couple small bugfixes.
✨Full release! The changes to 0.8 have stabilized and we are no longer on pre-releases. 🆕The Watchlist. Added the "Watchlist." (Thanks to @Septimus and @sgwilym.) 🆕Default to Dat. HTTP/S sites with Dat alternatives will now automatically redirect. This can be disabled from the settings page, and you will be prompted to go back to the HTTP/S version if you want. (Thanks to @Septimus.) 🆕Spellchecker Added a spell-checker. (Thanks to @Septimus.) 🔨globalFetch. The experimental
globalFetchAPI can now be used on dat:// URLs.
🔨Preview-mode. The "+preview" version of dats now filter out files according to the .datignore. 🔨Favicons. Favicon picker now supports uploading your own images. (Thanks to @Septimus.) 🔨Forking. Forked dats now preserve the
content_security_policyfields of the dat.json.
🔨Files editor Files editor will now stop you from navigating away from unsaved work.
- Many other final bugfixes and UI updates.
- Updated to Electron 3 which includes Chromium 66.
About the Watchlist
Because dat is a peer-to-peer network, sometimes you'll try to browse to a dat which nobody is hosting. When this happens, Beaker will prompt you to add the site to your "watchlist."
Beaker will continue to search for the site. When the site is found, Beaker will let you know.
Two quick fixes!
- Preview mode now correctly opens the preview interface
- Fixed a fatal error that occurs after the loading Beaker for the first time
- Preview mode. You can now toggle a mode where changes to your dat sites are kept locally where you can review them before publishing. This mode also uses a special
+previewversioned URL to show the mode. (We’ll put together lots of help docs on these updates when 0.8.0-final is released.)
- More network stats. The network tab of a dat's source-view now gives you more information about your upload & download bandwidth usage.
- And lots of bugfixes, of course!
About Preview Mode
We made the first 0.8.0 prerelease in March. At that time, we were looking for a better way to develop Dat sites, and we introduced a “workspaces” concept. Thanks to your feedback, we learned pretty quickly that workspaces were not quite right. They were a little too complex and difficult to use.
In prerelease.6, we replaced workspaces with a simple “bidirectional sync” to folders. That gave us a solid starting point: it was very simple to understand and still gave people the ability to build Dat sites outside the browser. However, people still wanted a way to preview their changes before publishing. The automatic sync was just not right. (We’ve also noticed that Linux has trouble watching folders efficiently with the APIs we’re using.)
In this prerelease, we’ve kept the “bidirectional syncing” folders, and we’re introducing “preview mode” on top of it. With preview mode, we finally have all the tools we need: you can set a local folder (or not!) and you can choose to review your changes before publishing.
Preview mode is a lot like the staging area in Beaker 0.7.x, but it has some key differences:
- It’s not automatically enabled for every dat (the staging area was)
- There are no special Web APIs for interacting with it (staging area had .commit(), .revert(), and .diff())
- The “preview” is accessed using a special +preview version tag on the URL. (This is also readable & writable using Web APIs.)
- Any time a change is made to the “live” version of the dat, that change is duplicated into the preview as well, overwriting any files in the preview that might be affected. (See below.)
We hope the preview mode works for everyone! Please send us your feedback. We’ll give a little more time for bugfixes, and then (unless we discovery a fatal flaw in previews) we’ll release 0.8.0 final soon!
Why do writes to the live dat overwrite the preview dat’s files?
One of the common problems we experienced with workspaces and the staging area was that changes to the live dat (by a Web API call for instance) would show in the “changes” interface as a deleted file. That’s because, from the perspective of our diffing algorithm, there’s a file in the live version that’s not in the development version, and so to “publish” the development version you’d need to delete the file.
We felt that, for now, the simplest solution would be to automatically copy changes back from the live version.
- Updated the library UI
- Added "type" to dat.json
- Added a "dat bandwidth limit" setting
- Scroll position is now retained on page refreshes
- Disabled the builtin ad blocker temporarily due to an issue with the upstream module
- New icon! (Still a work in progress
- Replaced Workspaces with Bi-directional syncing folders. Watch this video to learn more. Discussion is here
- New "template chooser" for creating archives
- New library listing
- Rewrote modals to be much snappier
- Added an "inline editor" to the library, plus more tools to create, edit, and manage files
- Updates to the browsing UI around dat:// sites to be more clear
- Added support for DNS TXT records
- Added the ability to set a "donation" link on dat:// sites
experimental.libraryAPI (we still need to document this, you should probably hold off trying it unless you really want to dig)
- Added an analytics ping to help us measure usage (it's opt in, currently in the settings page, default is off)
- Added a JSON renderer
- Added the
content_security_policydirective to dat.json
- Plenty of bugfixes and small tweaks
Fixes some issues and improves the tabs' rendering