Florian Lohse113 downloadsPublish to your own Blygger Studio, and read, quote and reply to other blygs, on desktop and mobile.
Write in your vault, publish to your Blygger blyg from iPhone/iPad or desktop. Short fragments and long threads that quote other people's items go to your own Blygger Studio; the plugin checks what will change before anything leaves your vault.
You need your own Blygger Studio. This plugin is a client: it sends your notes to a Studio that you own and have signed in to (see What you need). It does not work without one, and it cannot create one for you. The reader is experimental, see Known gaps.

![[photo.png]], ![[photo.png|a red door]] or
). They are uploaded to your Studio when you publish, kept with the item, and shown in the post.
PNG, JPEG, GIF, WebP and SVG, up to 5 MB each. The image has to be inside the same vault folder as the note's route (or a
folder below it): one from elsewhere in the vault is refused, and never read. Anything else that cannot be sent is also refused
before anything is sent, with the reason. Nothing is copied or renamed in your vault.What you send from Obsidian is published by your Studio as a page of your blyg. Items have no titles of their own: the large heading is the name of your blyg, the same above every item. On the left a fragment, on the right a thread that quotes a neighbour's item (the quote carries the author's name and the version it was taken from; only the top of the thread is shown):
| A fragment | A thread that quotes a neighbour |
|---|---|
![]() |
![]() |
Read the blygs you follow in the reader (experimental): the newest posts as cards, with what is unread, what answers you and how long each takes to read:

Open a post to read it as text. Reply starts a new thread that quotes it (or just the passage you selected), and Next takes you on:

Before anything is sent, a window shows what readers will see and what changes:

Quote another blyg by searching its items (or pasting an address):

Paste an address, or an item's id, to find exactly one item. The reader's "Copy id" gives [[id | "…"]]; paste all of it or the id alone. While the Studio looks it up, a "Looking up…" line with a spinner shows and the list below is greyed and cannot be chosen from; then the one item is there. An id finds your own items and items of blygs your Studio is subscribed to; for any other blyg, paste the item's address.


![]() |
![]() |
|---|
A thread that quotes a neighbour's fragment. The panel shows the quote under From other blygs:

Settings for a Studio-only setup need just the Studio address and a token:

Obsidian's file over app idea is that what you write should outlive any one app: plain files you own, readable with anything. This plugin tries to keep that true while you publish:
blyg_… keys).What this does not mean: the Studio, not your vault, is the authority for published items. Ids are permanent, versions only go up, and withdrawing an item leaves an end note and never deletes its address. The plugin's settings and its cache of the blygs you follow live in the plugin's own storage, not in your notes.
You do not need a GitHub account or a static site. (An older mode that commits to a GitHub-hosted site still exists in the code for early users and is hidden when you only use a Studio.)
blyg.If it does not show up in the list yet (a new release can take up to a day to appear), or if you want a test build, use the
install helper BRAT: install “Obsidian42 - BRAT” from the community list, open the command palette → BRAT: Plugins: Add a
beta plugin for testing, and add the repository florianlohse/blyg-obsidian, version Latest. Do not enable the BRAT
copy and the community copy together.
owner:read, owner:draft and owner:publish; owner:manage is for changing hoppers, dismissing mentions and asking your Studio to
look for new posts, and reading:state for read marks in the reader. Copy it (it is shown once).blyg-studio); paste the token as its value. Keychain entries stay on one device: repeat on each
phone and tablet.https://blyg.example.com; fill Studio mount
only if your Studio lives below a path such as /blyg) and choose the keychain entry in Studio token. The Setup
check row at the top of the settings lists what is still missing; it asks only for these two.blyg/ are
sent to the Studio (change the folder under Routes → Vault folder, or Add route for more). Tick Drafts
only on a route for a first try: its notes become private drafts and are never published.GitHub settings and the folder “Kind” stay hidden unless you switch on Website (GitHub) → Publish to a GitHub-hosted site. That box holds what essays, pages and other plain files need: the repository, the production branch and the GitHub token. The box Advanced, shown below it, holds only the older way of running a blyg from a GitHub repository (the preview channel, “Blyg address”, the items folder). Switching the switch off hides both without deleting anything. The commands that move an old GitHub-site item into the Studio (Studio: repost this note, Studio: list reposted items) are offered only then.

The plugin makes requests only through Obsidian's requestUrl, to these hosts:
| Host | What goes there | Credential |
|---|---|---|
| Your Studio (the address you set) | Your note's text and metadata when you send it, the image files the note embeds (only when you publish), and reads of your items, hoppers and followed blygs' items for the panel and pickers. | The Studio token, in a header. Never in a URL. |
| The Studio's public pages (same host) | The public manifest, read to find your blyg's address. | None. |
| The reader's requests to your Studio (same host) | The list of posts you read and your mentions, a look at the Studio's change counters every 30 seconds while the reader is open (and every three seconds during a Refresh), the read marks you set, a request that your Studio look for new posts (only when you press Refresh), and the look-up of an item when you tap a quote's source. | The Studio token, in a header. |
| A blyg's own server (only for what you open in the reader) | A post's image, when you tap it (or always, if you chose “Always load”), and the page itself if you tap “Browser” (that opens your browser, not the plugin). Image requests carry no token and no cookies, so that blyg's server can see that someone read the post. | None. |
api.github.com |
Only if you use the older GitHub mode. Not used in Studio-only setups. | A GitHub token, only to this host. |
Nothing else: no analytics, no telemetry, no third-party servers. Text from other blygs is shown only after being sanitised and is kept in the plugin's own storage, never written into your vault.
Only notes in your route folders, and the images they embed from the same folders, are ever sent, and only when you tap. Obsidian comments (%%…%%) and block ids are
stripped from the published text.
owner:read, owner:draft, owner:publish; owner:manage
is optional (hoppers, dismissing a mention in the reader, and asking your Studio to look for new posts in the reader). reading:state is optional too: without
it the reader works, but marking a post read or unread is refused (and says so). For the reader, make the token with every permission.|300 after a name is ignored), no HEIC conversion (convert
a camera photo first), and no way yet to bring a Studio item's images back into a note (a pulled or imported item keeps the
Studio's image addresses, which show as web images).Resizing images; OAuth sign-in instead of the monthly token; automatic checks for new Studio items; a public address setting for Studios behind a proxy.
Publishing needs an explicit tap and shows a preview. If something cannot be checked as safe (broken YAML, over a size cap, ambiguous ids, a link to a private note), the send is refused before any network call. Published ids are permanent: withdrawing an item leaves an end note and never deletes the address.
Open an issue on this repository. Please leave tokens out of anything you paste; the plugin's messages never contain one.
Pull requests are not accepted for now: this repository is a published copy of the plugin's source, and code changes are made elsewhere. If you have a fix or an idea, describe it in an issue.
MIT — see LICENSE. Credits: protocol by Venkatesh Rao and contributors (blygger/blygger-spec, MIT); ideas and
patterns from brndnpink/blyg-publisher (MIT), blygger/blygger-studio (MIT), aneeshsathe/blygger-desktop ("Burrow")
and QuickAdd's keychain handling (chhoumann/quickadd, MIT).
Thanks to Burrow. Burrow, the macOS studio and reader by Aneesh Sathe (aneeshsathe/blygger-desktop), paved the way for this plugin's reader and
for how it keeps up with your Studio. Its release 0.21 ("Sync reads less from the blyg") showed how to read little: look at the Studio's change counters
first and read the reading list only when something moved, never in a tight loop; a safety-net full read that backs off while it finds nothing; stepping
back when the Studio answers with an error; pages of the largest size; and asking the blygs to be checked only on request. Its bracket-grammar test vectors
(MIT) are replayed in this plugin's tests, and its notes on how a reader should read (a stream, an unread dot rather than a count) were a reference for the reader's design.