I've been working on a highly customizable multiplatform fediverse client, similar to bridging technologies that exist currently but a bit more seamless and robust, and focused on the indieweb vibe and personal customization overall. Excited to get it out there for testing, but I am really enjoying what I have so far. #interop #atproto #activitypub #retro #indieweb
Discussion
Loading...
@lovingisliving open source? are *you* writing it or vibe coding it?
@liaizon yes it's going to be open source, and yes I am using AI for its development. Which is not to say that I don't know the difference between a did:web or a did:plc, or that I did not spend a lot of time thinking about and planning out the architecture. I just have used AI to expedite the coding process and assist in finding different libraries/resources.
@lovingisliving thanks for the answer! I am not entirely opposed to using vibecoded software, but have been seeing a ton of new fediverse clients and servers and tools being released recently that are vibecoded and have really basic misunderstandings of how everything works and fits together, so it feels like the most pressing question to ask when I see a new piece of software released these days
@liaizon totally understandable! I have worked on the architecture first and foremost, and made sure it is consistent and coherent. Working with AI is definitely a challenge, and I've spent quite a lot of time undoing dumb mistakes, so you are certainly not wrong to have the suspicions.
@lovingisliving I was playing with https://mackinac.social yesterday, it is also a dual protocol client thats doing some interesting things and being made with a heavy scoop of AI