Compare changes

Choose any two refs to compare.

+2 -1
content.config.ts
···
})
),
tags: z.array(z.string()),
-
published: z.boolean().optional()
+
published: z.boolean().optional(),
+
bskyCid: z.string().optional()
})
})
)
+5 -4
.zed/settings.json
···
"language_servers": ["deno", "..."],
"languages": {
"Vue.js": {
-
"language_servers": ["deno", "..."]
+
"formatter": { "language_server": { "name": "biome" } },
+
"language_servers": ["!deno", "biome", "..."]
},
"JavaScript": {
"formatter": { "language_server": { "name": "biome" } },
-
"language_servers": ["deno", "..."]
+
"language_servers": ["!deno", "..."]
},
"TypeScript": {
"formatter": { "language_server": { "name": "biome" } },
-
"language_servers": ["deno", "..."]
+
"language_servers": ["!deno", "..."]
},
"TSX": {
"formatter": { "language_server": { "name": "biome" } },
-
"language_servers": ["deno", "..."]
+
"language_servers": ["!deno", "..."]
},
"JSON": { "formatter": { "language_server": { "name": "biome" } } },
"JSONC": { "formatter": { "language_server": { "name": "biome" } } },
+1
blog.config.ts
···
site: "https://finxol.io",
title: "finxol's blog",
author: "finxol",
+
authorDid: "did:plc:hpmpe3pzpdtxbmvhlwrevhju",
meta: [
{
name: "description",
+2
globals.ts
···
sharingProviders: SharingProvider[];
title: string;
author: string;
+
authorDid: `did:plc:${string}`;
meta: {
name: string;
content: string;
···
: { bluesky: true, clipboard: true, native: true },
title: config.title ?? "My Blog",
author: config.author ?? "finxol",
+
authorDid: config.authorDid,
meta: config.meta ?? [
{ name: "description", content: "My blog description" }
],
+4 -1
tsconfig.json
···
{
// https://nuxt.com/docs/guide/concepts/typescript
-
"extends": "./.nuxt/tsconfig.json"
+
"extends": "./.nuxt/tsconfig.json",
+
"compilerOptions": {
+
"types": ["@atcute/bluesky"]
+
}
}
+2 -2
deno.jsonc
···
{
"deploy": {
-
"org": "finxol",
-
"app": "blogging"
+
"org": "finxol",
+
"app": "blogging"
}
}
+1 -1
app/components/ShareActions.vue
···
<template>
<aside
-
class="print:hidden flex flex-row justify-center items-center gap-4 mt-24 md:w-[80%] mx-auto"
+
class="print:hidden flex flex-row justify-center items-center gap-4 mt-16 md:w-[80%] mx-auto"
>
<div class="h-1 bg-stone-200 dark:bg-stone-700 grow" />
<div class="whitespace-nowrap px-4 flex flex-row items-center gap-4">
+1
content/posts/blog-template.md
···
tags:
- open source
published: true
+
bskyCid: 3lqatrbwkjk2a
---
Are you enjoying this blog?
+1
content/posts/embracing-atproto-pt-1-hosting-pds.md
···
- atproto
- self-hosting
published: true
+
bskyCid: 3lxwbhjz4l22i
---
The [Atmosphere Protocol](https://atproto.com/), or atproto for short, is the protocol behind the Bluesky social network.
+1
content/posts/extending-openauth.md
···
- auth
- open source
published: true
+
bskyCid: 3llnnj4z2xs2u
---
I'm currently building [Karr](https://karr.mobi/?utm_source=finxol-blog&utm_content=openauth-post), an open-source federated carpool platformโ€”it's still very early days, not much there yet.
+1 -1
app/pages/posts/[...slug].vue
···
<BskyComments v-if="post.bskyCid" :cid="post.bskyCid" />
<template #fallback>
-
<h1 class="text-xl font-bold text-stone-600">Loading comments...</h1>
+
<h1 class="md:w-[80%] mx-auto mt-16 text-xl font-bold text-stone-600">Loading comments...</h1>
</template>
</Suspense>
+103 -26
README.md
···
-
# Nuxt Minimal Starter
+
# finxol blog
-
Look at the [Nuxt documentation](https://nuxt.com/docs/getting-started/introduction) to learn more.
+
This is the repo for finxol's blog.
-
## Setup
+
All posts are in `content/`.
+
Configuration is in `blog.config.ts`.
-
Make sure to install dependencies:
+
## Technology stack
-
```bash
-
# pnpm
-
pnpm install
-
```
+
- Nuxt v4
+
- Nuxt Content
+
- TailwindCSS
+
- Deno (Deploy EA)
-
## Development Server
+
## Bluesky integration
-
Start the development server on `http://localhost:3000`:
+
Tracking PR: [#1](https://tangled.org/finxol.io/blog/pulls/1/)
-
```bash
-
# pnpm
-
pnpm dev
-
```
+
Comments on this blog are directly integrated with Bluesky, the atproto-based micro-blogging social network.
-
## Production
+
This integration relies on the `@atcute/` library collection for interaction with Bluesky/atproto.
-
Build the application for production:
+
The idea was originally inspired from [natalie's blog](https://natalie.sh/posts/bluesky-comments/).
+
Although I ended up using mostly the same tools and strategies, I didn't follow her post to build it here.
-
```bash
-
# pnpm
-
pnpm build
-
```
+
### How it works in practice
-
Locally preview production build:
+
The author of the blog writes a post and publishes it.
+
They can then post about it on Bluesky, find the post id, and add it to the `bskyCid` field in the post frontmatter.
+
Any Bluesky post below the one identified will now be displayed at the bottom of the blog post, allowing for integrated conversation about the post.
-
```bash
-
# pnpm
-
pnpm preview
-
```
+
### How it works technically
+
+
The [AT Protocol](https://atproto.com/) is an open internet protocol for social applications.
+
All the data is decentralised and public ([for now](https://pfrazee.leaflet.pub/3lzhui2zbxk2b)).
+
This openness allows us to reuse and build things based on that data very easily, in a built-in way, without hacky workarounds.
+
+
This integration works in several parts:
+
+
#### `app/util/atproto.ts`
+
+
Contains the utility functions for retrieving all replies to a post, and extracting a post id from an atproto uri.
+
+
Uses `@atcute/client` to fetch using the `app.bsky.feed.getPostThread` RPC on the Bluesky public API.
+
Everything is strongly typed, although fetch errors are handled as `post not found` to make handling simpler in the Vue component.
+
+
#### `blog.config.ts`
+
+
The author DID is set blog-wide in the config file through `authorDid`, as it is primarily intended as a personal blog.
+
If need be, I can always move the DID parameter to the post frontmatter, allowing for guest authors or secondary accounts too.
+
+
#### `content.config.ts`
+
+
Since the Bluesky post CID needs to be set for each blog post independently,
+
I added a `bskyCid` field in the post frontmatter.
+
+
#### `app/components/BskyComments.vue`
+
+
This is the core component to display the replies.
+
+
The component simply fetches the replies by calling `getBskyReplies`, passing in the post CID passed as prop,
+
and displays the content using the `BskyPost` component.
+
+
The reply, like, repost, and bookmark counts of the original Bluesky post are also displayed.
+
+
+
#### `app/components/BskyPost.vue`
-
Check out the [deployment documentation](https://nuxt.com/docs/getting-started/deployment) for more information.
+
This component displays the post author, their avatar, the post content, and its stats beautifully.
+
+
Replies to replies are indented accordingly to visually thread replies together, using `BskyPost` recursively,
+
with a `MAX_DEPTH` to set a limit to the number of replies to show.
+
+
+
#### `app/pages/posts/[...slug].vue`
+
+
The actual post page only had some minor adjustments to integrate the `BskyComments` component,
+
using a `Suspense` boundary with a fallback to avoid blocking the rendering of the actual content.
+
+
#### Others
+
+
Some other files saw modifications, to adapt to this integration addition, allowing for visual consistency.
+
+
### Advantages of the approach
+
+
Since this blog is built with Nuxt, everything is SSRed.
+
This makes the Bluesky integration a wonderful progressive enhancement.
+
The comments will still display and show up as intended if the client has Javascript disabled,
+
without blocking rendering of the actual content through the use of a `Suspense` boundary.
+
+
Using Bluesky as a comment platform allows me to integrate conversations about my posts directly alongside them,
+
without bearing the load of moderation and user accounts.
+
+
### Limitations
+
+
As briefly mentioned, fetch errors are normalised to `#notFoundPost`,
+
this could be refined for better reporting in the UI.
+
+
This integration also only handles plain text content.
+
All embedded and rich media is effectively ignored for now.
+
+
## Install locally
+
+
```sh
+
# Install dependencies
+
pnpm i
+
+
# Run the development server
+
deno task dev
+
+
# Build for production
+
deno task build
+
+
# Deploy to Deno Deploy EA. Add `--prod` to deploy to production
+
deno deploy
+
```
+1
package.json
···
"@atcute/bluesky": "^3.2.10",
"@atcute/client": "^4.0.5",
"@atcute/lexicons": "^1.2.4",
+
"@iconify-json/bx": "^1.2.2",
"@nuxt/content": "^3.8.0",
"@nuxt/icon": "1.11.0",
"@nuxtjs/tailwindcss": "^6.14.0",
+10
pnpm-lock.yaml
···
'@atcute/lexicons':
specifier: ^1.2.4
version: 1.2.4
+
'@iconify-json/bx':
+
specifier: ^1.2.2
+
version: 1.2.2
'@nuxt/content':
specifier: ^3.8.0
version: 3.8.0(@libsql/client@0.15.15)(better-sqlite3@12.4.1)(magicast@0.5.1)
···
'@iconify-json/ant-design@1.2.5':
resolution: {integrity: sha512-SYxhrx1AFq2MBcXk77AERYz2mPhLQes1F0vtvG64+dJZWyge9studXo7MiR8PPeLjRjZdWRrReRbxiwdRMf70Q==}
+
'@iconify-json/bx@1.2.2':
+
resolution: {integrity: sha512-hZVx6LMEkYckScdRdUuQWcmv8Lm2au6Cnf799TLoR6YgiAfFvaJ4M5ElwcnExvCu8ntsS7jW89r0W5LwBAfZXQ==}
+
'@iconify-json/ri@1.2.6':
resolution: {integrity: sha512-tGXRmXtb8oFu8DNg9MsS1pywKFgs9QZ4U6LBzUamBHaw3ePSiPd7ouE64gzHzfEcR16hgVaXoUa+XxD3BB0XOg==}
···
dependencies:
'@iconify/types': 2.0.0
+
'@iconify-json/bx@1.2.2':
+
dependencies:
+
'@iconify/types': 2.0.0
+
'@iconify-json/ri@1.2.6':
dependencies:
'@iconify/types': 2.0.0