Welcome to Fuyeors Leaflet Test Playground!
I am fascinated by the publication mechanics and functional architecture of leaflet.pub. Therefore, my primary mission here is to thoroughly stress-test this platform, exploring the strengths and hidden quirks of its feature design.
1. Where Do Uploaded Images Actually Go?
Let's drop an image here and trace its digital footprint.
When embedding an image, the platform generates this internal API route: /api/atproto_images?did=did:plc:iw7qtwjfcdezkcpxgujxkq7v&cid=bafkreievveyn7r6h52iojjlx5sxrfbkddfgkcda2m2c7w2wp54efmk4oge&v=1
Interesting Discovery: When copying the rich text back into a Markdown editor, it reveals a Supabase storage URL:. This indicates thatleaflet.pubcaches assets on Supabase as well.
Since AT Protocol operates on a decentralized architecture, let's hunt down the authoritative PDS (Personal Data Server) for this user.
Step 1: Locating the PDS via DID Resolution
By querying the PLC directory service at plc.directory/did:plc:iw7qtwjfcdezkcpxgujxkq7v, we can instantly resolve the DID document. The output reveals that the hosting PDS is: leccinum.us-west.host.bsky.network
Step 2: Fetching the Raw Blob Directly from the PDS
Now that we have the PDS endpoint, we can invoke the standard AT Protocol XRPC method com.atproto.sync.getBlob to extract the raw asset. Constructing and visiting the official XRPC URL triggers an immediate file download. Alternatively, the image is also instantly accessible via Bluesky's production CDN.
Conclusion: Images uploaded to leaflet.pub are natively pushed to the Bluesky PDS infrastructure, automatically compressed to around 600KB, and simultaneously mirrored/cached on Supabase for the frontend interface.
2. Testing Other Platform Capabilities...
Embed a bluesky post:
Embed a standard URL (My Leaflet Alias):
Embed a URL with Open Graph:
The URL card styling looks incredibly clean and well-polished!
3. Final Conclusion...
Here is the full architectural breakdown:
- Custom Domain Routing: Vercel Multi-Tenant Platforms
- Media Storage: Bluesky PDS
- Frontend Framework: Next.js (React) + Tailwind CSS
- Editor Engine: Tiptap + Yjs (For seamless rich-text editing & collaboration)
- Database: Supabase
- Open Source Repository: github.com/hyperlink-academy/leaflet
While exploring the interface, I noticed a few minor bugs and UX quirks:
- The Slash / Input Glitch: Starting a paragraph with a forward slash / triggers the block command listener, but if no valid command is selected, the platform completely swallows the text instead of rendering it as plain text.
- Icon-Heavy Interface: The heavy reliance on standalone icons rather than explicit text labels can occasionally cause navigation confusion for first-time users.
Summary: Despite these minor hiccups, leaflet.pub stands out as an exceptionally sleek, fast, and minimalist platform for personal blogging. The integration with decentralized protocols makes it a joy to use.