https://www.tweeks.io/ "refused to connect", sayeth Chrome. Serious question to Tweekers: What is your site built with that an HN traffic bump instantly melts it?
uh oh... We do have a bunch of gifs + images on the page that are poorly optimized, but that shouldn't matter at this scale. I haven't been able to see "refused to connect" on my end. Still happening for you?
Yes, but the problem was me — apologies for the low-value post. I have NextDNS configured to block newly-registered domains, and this is the first time I've seen it in action. Best of luck with the launch!
Oh that's good to hear! You admittedly gave me a small heart attack just a few minutes after posting (and all the logs on my end looked healthy). The phantom crashes/failures are the scariest. But glad we seem to be holding up so far
Their page itself looks classic v0/ai generated, that yellow/orange warning box, plus the general shadows/borders screams LLM slop etc. Is it too hard these days to spend 30 minutes to think about UI/user experience?
I actually like the idea, not sure about monetization.
It also requires access to all the data?? And it's not even open source.
> I actually like the idea, not sure about monetization.
To be fair, we're not sure about monetization either :) We just had a lot of fun building it and have enjoyed seeing what people make with it.
> It also requires access to all the data??
Think of us like Tampermonkey/some other userscript manager. The scripts you run have to go through our script engine. That means that any data/permission your script needs access to, our script needs access to. We do try to make the scripting transparent. If you're familiar with the Greasemonkey API, we show you which permissions a given script requests (e.g. here https://www.tweeks.io/share/script/d856f07a2cb843c5bfa1b455, requires GM_addStyle)
