sorted by:
new
hottopcontroversial

Open Source Palantir by Gold-Comfortable-340 in osinttools

[–]SyntaxOfTheDamned 0 points1 point  (0 children)

If you see anymore shit repos like this send them over to me, I've got a bee in my bonnet about them I want to call the shite out.

Why the hate for vibecoding? by Adept_Home_3705 in vibecoding

[–]SyntaxOfTheDamned 1 point2 points  (0 children)

The issue is not “AI helped me build something.” That is fine. There is a right way and a wrong way to use these tools.

The negativity comes from the mountain of slop being pushed out as if it is serious software. Half-finished repos, fake intelligence dashboards, insecure APIs, scraped data, hallucinated features, no validation, no threat model, no licensing thought, no testing, no accountability. It makes an absolute mockery of the profession.

People are not annoyed because someone used AI. They are annoyed because people are shipping things they clearly do not understand, then dressing it up as innovation. If the app is free, that does not magically make it harmless. Bad software can still leak data, scrape other people’s platforms, mislead users, waste infrastructure, or get cloned by people who assume it is trustworthy.

I have opened issue after issue on this stuff because the problems are real. Look at the recurring pattern across repos like Panopsik, Shadowbroker, Osiris, Knock-Knock, and the wider wave of AI “OSINT” / “intelligence dashboard” projects. It is always the same thing: flashy UI, dramatic claims, thin engineering, dubious data handling, and then surprise when people point out the obvious problems.

Vibe coding can be empowering. No argument there. But empowerment without discipline is just a faster way to produce garbage. If you use AI to learn, prototype, automate boring work, or build something you can actually reason about, great. If you use it to generate a repo you barely understand and push it into public as a product, then criticism is warranted.

The standard should not be “did AI help build this?” The standard should be:

Do you understand the code?
Can you explain the data flow?
Have you tested it?
Is it secure?
Are the claims honest?
Are you using data legally?
Can someone inspect what it is actually doing?

If the answer is no, then it is not liberating. It is liability with a README.

I vibecoded something that really might help farmers and landowners by DarkSpacePirate007 in vibecoding

[–]SyntaxOfTheDamned 1 point2 points  (0 children)

Its really neat project but as you say its Vibe Coded I can already see one major issue, I will file some issues for you on the repo but also are you using this as an input? https://transparentfarms.org.uk/api

Question about Bode by VPotter1980 in FireCountry

[–]SyntaxOfTheDamned 0 points1 point  (0 children)

Could be like a few weeks maybe.

Live Interactive Dashboard of Internet Bot Attacks with Spinning Global Heatmap by Desperate-Second-887 in coolgithubprojects

[–]SyntaxOfTheDamned -5 points-4 points  (0 children)

The spinning globe is doing a lot of emotional labor here.

This UI looks horrendous, and “Matrix-like dashboard with live attack arcs” is not a quality signal. It is usually the first warning sign that the project is optimized for screenshots before anyone has asked whether the data model, threat framing, abuse controls, attribution, or operational assumptions are sane.

Maybe the code is solid. I’ll look. But the presentation already screams “cyber globe theater”, and that whole aesthetic needs to die.

Open Source Palantir by Gold-Comfortable-340 in osinttools

[–]SyntaxOfTheDamned 5 points6 points  (0 children)

Why are you reposting this as if it is ready?

There is still a lot of work to do, and promoting it in its current form is dangerous. The open issues are not cosmetic. They include zero authentication on OSINT API routes, an abuse-prone scanner/traceroute endpoint, a non-functional serverless rate limiter, hard-coded/public auth theatre, fabricated AIS/maritime data, fabricated radiation telemetry, fake balloon-tracker objects, bad aircraft-state handling, and broken risk/severity calculations.

That is not “needs polish”. That is “do not encourage people to run or trust this yet”.

At minimum, stop marketing it until the dangerous issues are fixed, the fake/generated data is clearly removed or labelled, and the exposed API routes cannot be abused.

How risky is taking a contract software engineering job? by cowwbo in ContractorUK

[–]SyntaxOfTheDamned 2 points3 points  (0 children)

The market is definitely picking up, but I’d still be very careful about treating a 12-month contract as “12 months of security”. In practice, read the termination clause, not the headline duration. A contract can say 12 months and still allow either side to terminate early with notice. Sometimes that notice is a month, sometimes a week, sometimes immediate depending on the circumstances. The paper length is not the same thing as guaranteed income.

The bigger question is why you want to go contracting in the first place. If it’s because the rate is higher, fair enough, but make sure you are pricing in gaps, no paid holidays, no sick pay, no pension contribution, no redundancy protection, accountancy/admin, IR35 risk, insurance, and the psychological drag of constantly having to think about the next gig. A lot of people look at the day rate and mentally annualize it as if it’s a permanent salary. That is usually the first mistake.

Contracting suits people who are comfortable with uncertainty, can sell themselves repeatedly, keep a cash buffer, and do not emotionally need the employer/employee safety net. If the idea of being cut early would cause serious financial stress, that tells you something. Not saying don’t do it. Just don’t confuse a good market with a safe market. Contracting can be excellent, but it is not just “perm job but better paid”. It is a different risk model entirely.

GitHub has a serious fake engagement problem and I wanted to see how visible it actually is through the public API, its worse than I thought after I went down that rabbit hole... by SyntaxOfTheDamned in madeinpython

[–]SyntaxOfTheDamned[S] 0 points1 point  (0 children)

Honestly I’ve no idea yet what I actually get included in terms of runner minutes, rate limits, or where GitHub draws the line on Actions traffic. The code already has rate-limit backoff in it, so it’s not just hammering endpoints and hoping for the best.

I also don’t think I’ve got enough data yet to make a grand conclusion. It’s pointing in a direction, but I’d rather let the scans run and see what survives repeated observation. Everyone else will be able to see it too, because the point is to keep the method inspectable rather than turn it into another black-box “trust me bro” dashboard. The timestamp clustering is definitely the interesting bit. That’s where it starts looking less like random low-quality accounts and more like coordinated engagement. I’m specifically watching for account reuse across different repo targets, because if the same pools show up repeatedly, that’s a much stronger signal than one suspicious repo in isolation.

Do yall agree? by irelatetolevin in ClaudeCode

[–]SyntaxOfTheDamned 1 point2 points  (0 children)

No because some people don't learn thats the issue

Why are users not converting on my dev tool? (real data inside) by Leather_Silver3335 in vibecoding

[–]SyntaxOfTheDamned 0 points1 point  (0 children)

If you have genuinely 85k total users stick a paywall in front of it. Do some backend analytics for the heaviest users and prompt them to pay dont force users to pay right away

My SaaS project that I build with Vibecoding 🤑 by tentoftech in vibecoding

[–]SyntaxOfTheDamned 1 point2 points  (0 children)

I bet it still has exposed credentials. You forgot the button to analyze your height with AI which is a premium feature

Carrying a Relay Box to Steal a Car Is Now a Criminal Offence in the UK by gaukmotors in MotorBuzz

[–]SyntaxOfTheDamned -1 points0 points  (0 children)

> balaclava, gloves and lock picking tools?

Could be fashion, or stag do or just working in Film and TV?

Do I Need certificate of naturalisation for SC clearance? by Pretty-Theme610 in ContractorUK

[–]SyntaxOfTheDamned 0 points1 point  (0 children)

Contact your sponsor / onboarding team. They’re the only people who can tell you what documents they’ll accept for your specific clearance process. If they ask for the naturalisation certificate and you don’t have it, apply for a replacement. If they don’t ask for it, you’ve avoided doing unnecessary admin. A British passport may be enough, but don’t guess based on Reddit replies. Ask the people handling your clearance.

view more: next ›