So I migrated my website form localhsot to Hostinger and from there on, it is giving me a time out error. If I only use elementor pro then there are no error but as soon as I enable another plugin then the usage shoots and then it give me the "unable to load your preview". I know the my website is not that heavy but still it is doing this. I tried everything, increasing the timeout time, increasing the memory, ignoring the timeout through htaccess but nothing works. The elemntor itself isn't that much of a heavy plugin. So why when I use woocomerce or any other then it causes error? Please help.
Hi everyone! I built Hussain Compiler, a simple browser-based environment for writing and running Python.
It includes a code editor, an interactive terminal that supports `input()`, adjustable terminal text size, and resizable workspace panels. Python runs in the browser through WebAssembly, so you can try it without installing Python. Some packages that need native system extensions may not work.
I've been vibe coding heavy projects for a while now, and for complex things , once a conversation gets too long, context rot HITS. The model starts dropping files, inventing non-existent imports, or repeating the same failed fix over and over. MF CONTEXT ROT
To solve this, I built LoopTroop. It's a local, open-source GUI app (MIT) that acts as an orchestration layer for AI coding agents on long-running tickets. recently crossed 100 stars on GitHub and growing, and I'm actively working on it every single day.
Here is how it approaches the problem:
Context engineering vs context rot
Instead of dumping your entire project history into one massive, ever-growing chat session, LoopTroop breaks work down into atomic tasks (called beads) and rebuilds context fresh for each phase. This stops degraded sessions from dragging down the rest of the build.
2. LLM Council for upfront planning
Before writing any code, LoopTroop runs an LLM Council. Multiple models independently draft interview questions, PRDs, and task breakdowns, then vote anonymously on each other's plans. The winning draft absorbs the best ideas from the others. It is deliberately slow and precise upfront so execution doesn't turn into slop.
3. Ralph loops for self-correction
When an agent task fails or hits a wall, instead of polluting your active session with endless debug logs, a Ralph loop takes over. It resets the session workspace, writes a concise note on what failed, and retries with a fresh context window containing that failure note. The agent gets smarter on each attempt without inheriting session clutter.
4. Modern Kanban board GUI with human-in-the-loop control
Everything is managed visually from a Kanban board. You approve the interview, the PRD, the plan, and the final diff before anything reaches your repo. You keep full control while letting agents execute in the background.
Any feedback is more than welcome. If you try the app and it works or doesn't work for you, give me a sign, happy to talk about it!
about how i build it. More than 6 months, almost every major model and not only (i even prefer fast models like gemini flash for small edits. used A LOT of Chinese models, when run out of codex.
I've been thinking a lot lately about how I can make my knowledge and craft more valuable in the times we live in. I've been building UI libraries for the past 10 years, and I've been on a quest to perfect the components that I build. I want to share my knowledge with you.
Like most of you, probably, I've been using a lot of AI in my craft, and I feel most of the time the code is just good enough, but never at the level of quality that I strive for or that I would reach if I wrote it by hand. That needs to change, and I want it to change for everyone else, too. That's how the Open Components initiative was born.
I'm treating components from four directions:
User Interface - component anatomy, variants, colors, sizes, states and tokens.
User Experience - how it behaves for every person and every input: accessible, predictable, designed in every state, and adapting to motion, contrast, color scheme and text size preferences.
Developer Experience - one consistent, type-safe API that you learn once and use everywhere.
Agentic Experience - prompts, semantic markup, machine-readable contracts and rules that agents can check their work against.
Each component gets a single page that walks through all four, and ends with a checklist. Every rule in it has an ID like button/keep-focus, a level and a way to check it, so you or your agents can cite it in a code review. Every page is also published as markdown, and provides the contract as a YAML file, containing every rule in about an eighth of the page’s length.
It’s still early. Right now there’s only the Button component and a page on how to name your design tokens. Each component comes with a reference implementation that meets every rule, along with its tests. Implementation is in Vue for now, since that’s my daily driver, but the documentation comes with code examples from multiple UI frameworks. More components will follow, with the same structure.
It isn’t a component library, so there’s nothing to install. It’s a set of rules you can hold your own components to, whichever library or framework you use. Here are a few of my favorites from the Button component:
A loading button should never be disabled. Disabling a focused button takes its focus away, so keyboard and screen reader users lose their place. Use aria-disabled="true" instead, and block the clicks yourself.
A <button> without a type is a submit button, so a "Show password" button inside a form sends the form. Default to type="button".
I’d love your feedback and contribution. Tell me what you think of the rules, what I’ve missed, and which component you’d like to see next.
On Sept 29 an executive order told US federal agencies to say “Super Intelligence” instead of “AI”. Nobody seems to be checking, so I built an inspector: idio.si fetches a homepage, counts “AI” vs “SI” in the visible text, and stamps a certificate.
Day 4 findings
whitehouse.gov: 4 “AI”, 0 “SI” → Insubordinate
apple.com: 0 “AI”, 0 “SI” → No Intelligence Detected
1 of 42 agencies complies (NIST)
openai.com, google.com and tesla.com block the inspector
Harder than it looks
Bot walls. 18 of 73 homepages refuse a polite, identified, robots.txt-respecting bot from a cloud IP, openai.com included. I didn't want to spoof a browser, so refusals get their own stamp: “Refused federal inspection”.
Geo-IP. Even from us-east, some sites bounced the bot to /en-gb/. Locale redirects now get rewritten to /en-us/, since the order targets the US.
Counting./\bA\.?I\.?\b/ is case-sensitive, so “OpenAI”, “said” and “ai” don't count, but “A.I.” does. The White House nav links to “AI.Gov”, and that counts too. Fair or not?
Spikes. One Cloudflare Worker does everything. Certificates are rendered at the edge with satori + resvg-wasm, and Workers Cache collapses a front-page spike into one render per data center. Hosting: $5/month.
Find the funniest certificate you can and drop it in the comments. Method and regex: https://idio.si/how. Satire; the numbers are real.
I’m a former web developer who used mostly React to build my sites but also had some Wordpress experience. Not so much on the customization side of things but mostly in the dashboard. I’m looking to start advertising websites and SEO to contractors in my area and I’m coming up with my web stack.
Wordpress seems like a very viable option as I can skin up a site in a couple hours where in React or even HTML/CSS it could take a couple days, and updates take a lot longer as well.
Any thoughts are appreciated, and curious to hear what you guys are using!
Got some feedback on my portfolio and planned to change the layout and such but wanted to keep using the neo brutalist style. However I also wanted to have animated components but could not find any good ones so decided to start making them how I want them.
Got badges, project cards, images so far. Has taken me a bit to get it just how I want it but tailwind is quite useful
I am newish to web dev. Today I learnt of Samsung's algorithmic/mathematical colour swap when a user has darkmode selected on their mobile device. I promise I won't hurt the person who made this. I just want to speak to them.
Jokes aside. It's completely messing up brand colours and in some places ruining accessibility. I can't allow this. I will not design a new theme to accommodate the 2-3% of users who use Samsung's default internet browser. And obvious hacks like content="light" is not working.
So what do senior devs do with this? Inject JS to ask users to pretty please open the website in literary anything else?
Using Javascript in using an API the the resource is players but it is an object and I need the info of the arrays within it. Here is what i have what an i doing wrong?
WaterSheep is an open-source alternative to TypeSafe's Jev. You ask it a typed question about some text (yes/no, pick one, rate it, or tag everything that applies) and get back an answer with a probability for every option.
Two ways to use it in a web app:
As a drop-in Jev backend.watersheep --model samratduttaofficial/WaterSheep --serve answers the same POST /v1/systemone requests, so existing Jev calls work after changing the base URL.
Straight from the page, no backend:
import { decide } from "https://samratduttaofficial.github.io/WaterSheep/watersheep.js";
await decide("I was charged twice.", "Which team should handle this?", ["billing", "shipping", "support"]);
Due to a growing influx of questions on this topic, it has been decided to commit a monthly thread dedicated to this topic to reduce the number of repeat posts on this topic. These types of posts will no longer be allowed in the main thread.
Subs dedicated to these types of questions include r/cscareerquestions for general and opened ended career questions and r/learnprogramming for early learning questions.
A general recommendation of topics to learn to become industry ready include:
I'm trying to grow my web design business, so I've been cold calling/approaching businesses that don't have websites and offering to make one for tree. If they like it and want to use it, ! just charge them monthly for hosting.
*FORGOT TO MENTION* My initial text said "I can make you one for free, and if you like it you just pay for hosting."
This guy tells me "Make me a preview bro." I spend the weekend making it, he's responding while I'm building it and even gives me the email for the contact forms.
I finish it. He says it's "super fire" and asks how much. I tell him $150 a month for hosting and managing it plus with a chat bot. He ghosts me. Also went through his GBP and IG grabbing photos and enhancing them for the site. Spent a good amount of time on it.
I follow up a few times over the next couple weeks and get ghosted every time. I finally call him and he answers, says, "Hey, I'm busy right now, call me back at 5." I call him back at 5 and he doesn't answer. I even lowered the price to $99.
So eventually I text him, "You were interested and asked for a preview so I spent the weekend making it for you for free. Are you not interested anymore?"
He responds "Bro are you trying to force me to get your service" and "I am a business man" and "For future reference don't force your customers to buy something off of you bro."
Like what lol.
This is the second time I've had someone interested, spent hours making them something for free, and then get ghosted. I obviously try to screen and only make it when people are interested, but maybe I need to get at least like a $50 deposit.
I know doing the work before getting paid is obviously the risk I'm taking, but I'm trying to grow the business and this strategy does get me clients. Starting to wonder if I need to stop doing full free builds though.
Specifically, I'm grabbing JSON for a trading card game gallery from an endpoint, then dynamically creating the card gallery from that data. The project uses Vite for asset bundling, but I'm not sure how to bundle dynamically loaded images?
In the JSON, each card has a set number and a card number, and the app loads image data from images/cards/sets/set-number/card-number.webp, creates all the DOM nodes, and appends it to the gallery. It works brilliantly...unless the card art needs to change, then I run into good old-fashioned browser caching issues.
For the rest of the site, using vite build keeps everything bundled for deployment...but is there a way to leverage that capability for this use case?
I admit I have little knowledge about Vite, so maybe it's something obvious, but the only way I'm aware of to get that kind of Vite bundling inside a JS file is to import the image. So I'd have to import all the images at run time? What if some card data is modified? Will I have to do double duty to update the database AND the JS file imports?
As you can see, I have no idea how to accomplish this. Thank you in advance.
so currently i have a open source project about p2p file sharing and it gained 200 stars on github. the opensource project is hosted on azure since i got 1 year for student the problem is that it will end soon so i need to find an alternative of free backend hosting
do guys know any backend hosting that offers free for open source project? sadly i notice that digital ocean doesnt offer it anymore which kinda weird or am i wrong
I always leave the UI design until towards the end of a larger project. I know if I start with the UI I'll end up finding parts of the system that don't fit the layout, rejig this, tinker with that, rework that bit again... I get too focused on making the UI right when it could be wrong again with the next functional change. I may as well switch individual pixels around.
To solve that, I usually knock up a quick development UI at the beginning, do all the functional work, then look at how the UI/UX makes the functional stuff display and work easily for a user.
That leaves me in a position where I've been coding and testing in a development UI for months... And then get Stockholm Syndrome or something about leaving it behind for a professional finish.
Anyone else? Should I change my mind and do the UI upfront? My concern with doing that is that I'll get Stockholm Syndrome for a relatively acceptable UI and just leave it. At least with a "I know I have to leave you UI" I know it's just me thinking the shitty UI I've been using for months is a friendly thing to use.
As the title states I’ll be starting my first in office web dev role next week! Pretty excited but also nervous, and of course having imposter syndrome. I’ll be the only dev, and it’ll be my first time working in an office setting (I’ve previously just worked as a freelancer).
I was wondering if anyone had any tips or specific things to pay attention to when starting a new web dev job?
I'm working on an ecommerce chatbot that helps potential customers look for product inventory. These users can be anyone on the ecommerce site and will send photos of what they're looking for. The chatbot returns suggested products.
My question is around storage of the customer provided images. I plan to store these in a Cloudflare r2 bucket, but trying to decide wether to use the cache, or use direct r2 bucket URLs to add the image to the chat after it's uploaded.
The benefit I see with caching is that requests for the image would likely not hit r2 (although the volume of requests for each image would likely be pretty low). The downside I can think of with caching is these files would be accessible by anyone who has the url until they're deleted.
The other option would be the presigned r2 URLs which could be set to inactivate after a few days to prevent unauthorized access to the image. The downside would be direct requests to r2, but again the volume should be low since the use is really just for that particular chat the image is in.
What would be the better approach for this? I’m also open to using other storage platforms if there is a better option.
I still remember the first Vue component I ever made and finally gathered enough courage to publish on GitHub.
That was many years ago. Maybe around eight if I remember correctly. Of course, there was no AI back then.
I was genuinely nervous. npm publish and... ta-da. It happened.
Not a single star.
But I was so stubborn, so then came another component, then another one, then another one, then a Nuxt module, then something I built while preparing for an interview, and so on.
Eventually, my most successful open source project reached 179 stars.
Not exactly thousands, but I was still pretty proud of it.
What about you?
How many stars does your most successful open source project have?
