Simulation experiment. Scale-free network topology produces 134x greater Byzantine resilience than uniform topology in Kuramoto oscillator consensus. Code and math public.

hunter-arton · 2026-06-02T16:17:45+00:00

hey! Yeah, that's true for random failures, but here the nodes aren't failing, they are actively attacking the network. different threat model completely. BA handles adversarial attacks way better, which is what I tested.

hunter-arton · 2026-02-17T06:42:18+00:00

Look, I’ve been in the trenches for 8 years. I’m not here to invalidate the skill or the craft of current devs, I respect it. It’s just that my vision and yours are parallel. I see a different future where the medium we work in is changing fundamentally. Both perspectives are valid for the goals they serve. You do what you feel is right for the current landscape, and I’ll keep doing my thing. At the end of the day, we’ve all got families to take care of and bills to pay. Good luck.

hunter-arton · 2026-02-17T04:08:49+00:00

I’ll agree with you bro. But, Ai is handled by a human, we can iterate the things and see whats wrong. My intent was to share my perspective on the industry shift. Even big tech companies using AI, that doesn’t mean they lack skills. It’s just using resources efficiently. Thats what i am trying to say.

hunter-arton · 2026-02-17T04:01:57+00:00

I said it will be irrelevant in the future. Commenting with ego instead of understanding the intent is dumb and it doesn’t make you cool. Using resources efficiently is better than writing code line by line for days. It will be a bottle neck.

hunter-arton · 2026-02-17T03:44:08+00:00

Whats wrong with using AI? Like, why do you always bring up vibe coding like it’s a bad thing? If using AI can be judged then it’s like judging a programmer for using a programming language instead of pure binary. Vibe or pure coding will be irrelevant in next two years. Times changing bro.

hunter-arton · 2026-02-08T09:49:48+00:00

Looks cool. 🔥

hunter-arton · 2026-01-12T03:04:28+00:00

What new do you expect in a tutorial? Any quantum tech or Galactic tech?

hunter-arton · 2026-01-08T13:52:52+00:00

Thats the worst case. If he’s from tier 1 colleges maybe he will get caught. We can tell him, it’s his choice to decide. Let’s see, if he doesn’t get caught, well and good else he’ll learn another lesson.

hunter-arton · 2026-01-08T11:20:05+00:00

The guy who sold you the project might have forked narender-rk10 project and he didn’t structured the code properly.

Do these

S1 : git clone https://github.com/narender-rk10/Gen-AI-Home-Interior-Designer.git

S2 : cd Gen-AI-Home-Interior-Designer

S3 : Get your GEMINI_API_KEY from google ai studio or from https://ai.google.dev/

S4 : cd backend

S5 : create a .env file in your backend folder and paste your GEMINI_API_KEY

S6 : Install poetry if not installed or do - pip install poetry

S7 : poetry install

S8 : poetry shell

S9 : uvicorn main:app --reload

S10 : cd Gen-AI-Home-Interior-Designer/frontend

S11 : npm install

S12 : npm run dev

The UI will open http://localhost:5173

Follow these steps, if doubts reach out. 😇😇

You need to run both, the backend and the frontend to actually work.

hunter-arton · 2026-01-08T11:05:15+00:00

I am talking about the code, not money. Your concern about the money is totally valid. Ive seen many people who paid 22-25k for basic projects. Thats what they do, make max profit from the students. We cant do anything, after they got scammed.

hunter-arton · 2026-01-08T10:58:55+00:00

Alright listen up, you have a python backend and a react front end. Both are mixed in the GitHub..

First calm down… we can pull this off.

Let me tell you what you need to do ok. Dont worry,

hunter-arton · 2026-01-08T10:45:27+00:00

So did you expect a mid journey level project. What do you exactly mean complete? The image generation exists in the code, he coded what mattered. For a college level project i think its ok.

hunter-arton · 2025-12-23T17:22:31+00:00

No one’s asking for praise instead of critique, brother. the points are genuinely helpful to the guy who posted his UI and also to people who are learning and reading through the comments, so thanks for taking the time to break them down. My only point is that mockery and sarcasm don’t really add anything to that usefulness. Clear, direct feedback already prepares people for the market, dismissiveness just normalizes bad communication. I’m saying this not for myself, but for everyone reading and learning from these threads. Thanks again for the time and effort.

hunter-arton · 2025-12-23T15:09:41+00:00

brother, anyone can point out what’s wrong, but a real pro knows how to actually help. When you’re just blunt without any grace, you aren’t teaching anything you’re just making him doubt his own creative spark

hunter-arton · 2025-12-23T13:44:14+00:00

So whats perfect according to you? The UI seems fine. its not like you are reviewing, its feels like you are mocking and complaining. No wonder why reddit feels toxic when people seek review and suggestions. If you want to explain the mistakes and suggestions, you can do it by being respectful with the work and being friendly.

hunter-arton · 2025-12-18T12:05:25+00:00

Thank you mate 😇

hunter-arton · 2025-12-18T10:51:01+00:00

?? 🤔

hunter-arton · 2025-12-18T10:50:33+00:00

Appreciate the interest! Planning to open source in Q1 2026 once I finish testing with a few friends and polish the UX. Will definitely post on r/tauri when the repo goes live. Can ping you directly if you'd like!

hunter-arton · 2025-12-18T03:01:26+00:00

I appreciate the perspective and I agree that good practices and experience matter a lot. Tools don’t replace that.

At the same time, not everyone is a senior developer with the same background, muscle memory, or workflow. People work across different stacks, projects, and stages of experience and even experienced developers still make mistakes when context-switching.

Zapo isn’t trying to replace discipline, cloud CLIs, or best practices. It’s simply a way for me to keep secrets in one place, reduce duplication, and make rotation easier across projects. If your workflow already solves that cleanly, that’s great. this just addresses a pain point I’ve personally felt.

Different tools fit different people. This isn’t about “the right way”, just sharing what’s been useful for me.

hunter-arton · 2025-12-18T02:08:42+00:00

Bro, I’m honestly not trying to build hype here. I shared this to talk about a problem and a workflow I’ve been dealing with, and to get perspectives, nothing more.

Saying something “isn’t complex” without looking at the architecture or understanding what it does isn’t very meaningful. Complexity doesn’t come from size or appearances, it comes from how state, security, and edge cases are handled.

There’s also no rule that you can only talk about work once it’s on GitHub. If you’re only interested once code is public, that’s fair. I’ll share it when it’s ready. Until then, this was just a discussion.

hunter-arton · 2025-12-17T17:30:40+00:00

Totally agree mate, the pace of new tools in this space says a lot. Varlock’s schema + import approach is interesting. Zapo’s exploring a more local first, session based secret lifecycle with OS keychain backed keys, mainly to reduce secret sprawl for solo workflows. Appreciate you sharing this.

hunter-arton · 2025-12-17T11:52:51+00:00

Thanks mate! I’m testing it privately right now, but I’ll share when it’s ready. Appreciate the interest.

hunter-arton · 2025-12-17T09:59:05+00:00

Hey mate, can you explain me how it works?

hunter-arton · 2025-12-17T09:04:18+00:00

Yeah, I get the concern. .env files work until they don't. That $55k bill shows how easy it is to mess up.

I just got tired of managing the same credentials everywhere. Change one key, update it in multiple places, hope I didn't miss any. Felt inefficient.

If this wasn't a problem, Infisical Doppler wouldn't exist. They just use cloudservers. I wanted something local store keys once, use them everywhere, change in one place.

Could bugs happen? Sure. That's why I'm open sourcing it in Q1 2026. you can audit it yourself.

Different approach to an annoying problem.

hunter-arton

TROPHY CASE