Post by @sailor_sega_saturn@awful.systems

2026-11-05 05:37 UTC

Clearly written by someone who spends more time chatting with chatbots than talking to actual people. The bulk of the argument is that he asked the chatbots when AI was gonna foom and they told him “In a few years I guess my man”. The “reading progress” widget bugged out for me and got stuck at 92%, it also links to a page that doesn’t exist. Still curious? We’ve answered 50+ more questions. […] Showing 22 of 22 questions I was promised 50+ FAQ questions :( Anyway I stumbled across the arbitration clause so I’d better stop looking at the website in case I ever have to sue this guy for any reason!

Replies (2)

@lurker@awful.systems 2026-11-05 05:57

Yeah a lot of the text pinged my ‘this was AI generated’ brain

Open ##5484628
@lagrangeinterpolator@awful.systems 2026-11-05 05:58

Vibe coded websites really are the epitome of AI: there’s tons of flashy stuff that looks impressive at first glance, but shit starts breaking down with the slightest breeze. The reading progress widget was working perfectly for me at first, but then I clicked around a bit (the “see what’s coming” link in that widget straight up leads to a 404) and then it got stuck at 88% for me. The slider in the “Timeline Explorer” is also extremely laggy for me, with an update taking 1-2 seconds. There’s also some UI elements that don’t make sense, like the four options in the bar above the “Countdown to AGI Achievement” box are duplicated in the “AGI scenarios” sidebar on the right side immediately below. Also some buttons break occasionally and I need to refresh to fix them. Even though my own work does not involve any coding, I have seen a vibe coded project secondhand from someone who wanted to use it because they thought it would save time. It is very impressive at the start, since it can just pump out tons of features very quickly. But then disillusionment sets in as the project turns into a game of whack-a-mole where you yell at the AI to fix an issue and then two more pop up. And no way in hell are you fixing things yourself, because the codebase is an unreadable pile of spaghetti.

Open ##5484629