Repository navigation
Burrow 0.13.0
Changed
- Labelled links need Blygger Studio 0.47. The
[[picker writes labelled links,[[id | label]], which an older studio shows as literal text or a broken link. On an older blyg everything syncs as usual except posts whose text has a labelled link or quote (outside code, generated text included): they wait until the blyg is updated or the labels go. Publishing one offers ⏎ to write the links bare ([[id]]) and publish. Withdraw and pin always go, since they don't send the text. On such a blyg the pickers write the bare form. Burrow says "Your blyg needs updating" once, on connecting or at launch, keeps a status-bar notice with an Update your blyg link, shows the same in About, and a waiting post's pill says why on hover. Burrow reads the version from the blyg'sblyg.jsongenerator. For another server it checks whether search results carry alabel, and when it can't tell, it doesn't hold anything back. The "older than 0.40" limits sheet and its About section are gone, since every blyg that would have seen them now gets this notice. Server requirements. - The
[[and![[pickers write labelled links. A pick writes[[id | label]](a quote,![[id | note]]), studio 0.47's grammar: the label is the link's text on the published page, so editing the words after|renames the link, and a quote's note is only for you. The label is the post's heading, else its title, else a quoted excerpt. Picking a post with no heading labels the link with its title,[[id | Title]], rather than a quoted excerpt (a deliberate difference from the studio). Quote into a thread from Reading writes the labelled form too. The preview renders labels as studio 0.47.0 does. - The
[[and![[pickers lead each row with the post's title again; a link's row adds "links as “…”" when the label differs from the title. - The picker footer says what a pick writes: "⏎ inserts [[… | label]]", "⏎ inserts ![[… | note]] on its own line".
- Hovering "unpublished edits" in the status bar, or the edit mark in Posts, says how to publish (⌘⏎) or discard (⌥⌘Z) them.
- Unpublished edits have their own mark in Posts (
marker.edited): a dot in the theme's edited colour, Δ in Fortress. The published and pinned marks have tooltips. - Fortress's status bar shows your last two weeks of posts as a block-character strip instead of the z-level. Themes naming z-level still load, with a warning.
Added
- Discard changes. A published post with unpublished edits can go back to the version it has published: ⌥⌘Z, Post › Discard Changes…, the toolbar's Discard, or "Discard changes…" on the current version in ⌘Y. A sheet asks first, then "Back to vN as published". The public post doesn't change. The toolbar's Discard button is an eraser.
- Your own posts in Reading and Posts. "Your blyg" is a Reading source: your published posts sit in All, Today and the stream by date, and alone under Your blyg, and they are never unread or counted. A published post in Posts has a row of chips above the text: Reply · new stub (⌥⌘R), Quote into a thread (⌥⌘Q) and Link post · new fragment (⌥⌘L), also in the Post menu. Your own post forks only from ⌘Y, with Fork this pin on a pinned version.
- Windows wording in newer app text. Lineage, the stub bar, the sources pane, Subscriptions, the stream, the notes drawer and About say Windows keys and "this PC" where they said ⌘ or "this Mac".
- Windows: Discard changes has no default key (Ctrl+Alt+Z is AltGr+Z). Use the Post menu or the toolbar.
Fixed
- Fixed a run of spaces in the "still marked unpublished" toast.
This build isn't notarized by Apple. The easiest way to install it is the
one-line Terminal installer in the README, which Gatekeeper doesn't block.
If you download it in a browser, macOS 15 and later say "Burrow" Not
Opened. Try opening it once, then click Open Anyway in System Settings ›
Privacy & Security, or run
xattr -dr com.apple.quarantine /Applications/Burrow.app.
Windows (x64): unzip Burrow-windows-x64.zip anywhere and run
Burrow\blygger.exe. The build isn't code-signed yet, so SmartScreen asks
the first time: choose More info, then Run anyway. It needs the
Microsoft Edge WebView2 Runtime (part of Windows 11). The Windows build
doesn't update itself yet: download new versions from this page.