Yeh, the bad decisions I've made... buying domains is def one of them.

Thank you!

:)

Neither, and good eye. dboft ran Photon to start, and when I replaced it with my own front end I carried the favicon over without registering that the hexagon was Photon's mark. That was a mistake, and it's been swapped. The Photon-y feel is real: Photon was the client I replaced, so it set the bar for what mine had to do, and the basics look alike because they're the basics of any Lemmy client: votes, sharing, compact and card views, threaded comments, a tab bar on phones. Beyond that the design is a different one: a three-pane split reader, related posts found by meaning rather than tags, following people, reminders, and every page readable as plain Markdown or JSON. The code is written from scratch; none of Photon's is in it. Credit to Photon either way.

TY TY!

Thanks! Apart from me, the accounts are service actors. I set them up as bot personas for testing, so they posted links, commented and voted. It didn’t feel right, so I switched off their comments and votes and marked every one of them as a bot. But again, the profiles are published as Service actors, which is how I understand that ActivityPub marks automated accounts.

Most of what they did stayed on my instance. A little did federate, because a couple of people elsewhere subscribed to a few of my communities. I’ve since deleted the bot posts in those communities and kept the bots out of them. eek did not mean for that to happen. I'm learning.

They still bring in links from news and science sources, but that should stay on my instance. I built dboft as my own Reddit replacement, and I’m not sure it’s right for everyone or this protocol.

dboft runs on two Rust programs named after weaving. loom is the interface: like the machine that weaves many threads into one cloth, it gathers conversations from dboft and across the fediverse into one readable site. weft is the server underneath: named for the thread a loom carries across, it stores the posts and comments and trades them with other servers over ActivityPub, the fediverse’s open standard. It also speaks Lemmy’s API, so Lemmy apps work with it. To find related posts, loom turns every post and comment into an embedding: a small open model, Qwen3-Embedding-0.6B running on an ordinary CPU, maps the text to 1,024 numbers that capture what it’s about. These are stored in PostgreSQL with pgvector, and an index finds each story’s nearest neighbours in meaning in under a millisecond, even when they share no words. Its just an experiment.