AT Proto Projects

I had been waiting for decentralized platforms for a long time, and they arrived right when LLMs started getting better at coding. That timing changed a lot for me.

Building simple things on AT Proto pushed me to understand what interoperability actually means. It is not like signing in with Google or Microsoft. You are not just using a platform to sign in in order to share your email and other info. With an Atmosphere account, you are reading, writing, deleting, and updating your data in your own PDS and using same identity and records across different apps.

Every problem along the way pushed me further. Sometimes it caused exhaustion. But I took breaks between projects, and then the problems looked smaller and I started building again.

I mostly build simple clients on top of Bluesky, but one day I want to create a full app too. I launched my blog on AT Protocol as a starting point to see how far things can go. All of this without any prior coding knowledge. I built on ideas, ideas gave me knowledge, and I just kept repeating that process.

These are all vibe-coded projects and are part of my journey with LLMs. I am not a professional developer yet, but I am learning. So if you find any bugs or errors, please let me know.

When I started with Bluesky experiments, I used to build everything using vanilla JS and HTML. But as LLMs and their ability grew, I became familiar with Next.js and started building my projects in it. So recently, when I checked my Google Search Console, I saw that there is traffic to my tools. So I decided to rebuild everything in Next.js, and here I’m.

Projects built on Next JS are not yet open sourced. Because it was built almost entirely with LLM generated code based on my specific requirements. Only the styling and core logic are mine. Most of the JavaScript comes from LLMs, so the codebase is predictably messy. But I’m actively improving my understanding and learning through the process.

Privacy & Security

Again, these are all completely client-side projects. In addition, I haven’t included any kind of analytics or trackers. So you can browse freely. My only repeated suggestion is that if you are using the signed-in features, make sure to delete the app password after use. And remember that only you can make changes to your repository, so be careful what you are doing with it when deleting posts, likes, blocks, mutes, and bookmarks. Make sure to back them up before deleting.

None of your data is stored on my server, because I don’t have a server as of now. Everything happens only in your browser.

While atproto data is public, you should take care to respect the rights, intents, and expectations of others. This goes beyond following copyright law, and includes respecting content deletions and block relationships.