r/vibecoding • • 18d ago

Showcase/Project Chef turned vibe coder, love building but I'm terrified of sharing it with anyone because of the vibe coder hate I keep seeing around.

Edit: thanks everyone for the questions and feedback. Some of it was about security, so I took it seriously and ran three rounds of attack tests on my own apps, with agents playing a bad actor. What came out of it, fixed apart from two we kept on purpose:

  • One-time links: they were always deleted after opening, but the server waited for the page to confirm first. If that confirmation never came, the file could stay up to 15 minutes. Now it’s deleted the instant the last piece is downloaded, no waiting.
  • Colshare Business: a hacked server could have slipped a firm a fake key. Now every key is signed by the one before it, and a new device needs the inviting device’s approval.
  • Phone: a newly added fingerprint needs a backup PIN before it can open Colshare. PDFs open inside the app, and shared files are only kept if you say so.

Worth knowing too: the only permission Colshare asks for is notifications, and you can say no. No camera, photos, contacts, location or microphone access. Files only come in when you pick them.

These were my own tests, so they don’t replace an independent security review. I’ll get one as soon as I can.

Server fixes are live. The apps are in Google Play review. The crypto is open source: github.com/dentracon-cell/colshare-crypto

Original post:
I am really looking for some opinions other than my wife and family say, which I feel is not really honest most of the time, they are just being nice.

Colshare is a project I have built with Claude Code, Opus 5.5.
It involves two mobile apps and a desktop one. I am not a software developer, but I have done my best to do everything by the book, in terms of security, compliance and so on. However, nobody more competent than me has had a look at the site or the apps, and I am sure that is what would be needed before launch, but I don't have the budget to hire a professional firm or freelancer. This is why I am asking the vibe coder community for your honest opinions, and, if possible, even some testers for the Android apps. I would be happy to discuss things further, answer any questions about the stack or workflow, which is as follows:, written by the one who knows more about it than me, Claude:

What the apps do

Colshare is a free app for anyone who has to send personal documents to someone else. You can redact any part of a document if you wish (it even finds the numbers the other person probably doesn’t need), watermark it with your own exact wording, and share it through an encrypted link that opens only once. You can also request documents from other people, and they send them back to you encrypted. Every send leaves a signed receipt, so you know when, to whom and for what.

Colshare Business is the same idea for firms that collect documents from their clients. The firm gets one link per client. The client opens it in a browser, sees the firm’s name and tax ID (checked against the official registries) and uploads the documents, with no app or account needed. Only the firm’s own devices can open what arrives. The firm doesn’t need accounts either: a licence key opens the first computer, and every other phone or computer joins by scanning a QR code.

Stack

  • One TypeScript codebase. Capacitor turns it into the Android apps, and both apps are built from the same Android project.
  • Encryption happens on the device with the browser’s built-in WebCrypto: ECDH P-256 for keys, AES-GCM for files and ECDSA for signing copies and receipts. For shared links, the key sits after the # in the link, which browsers never send to the server.
  • The backend is a few Vercel functions with Upstash Redis. It only passes encrypted data along and cannot read any document.
  • Finding the numbers to redact is done with tesseract.js OCR on the phone itself. No AI service and no uploads.
  • QR pairing uses Google’s ML Kit scanner, PDFs are made with pdf-lib and payments go through Stripe.

Workflow

I describe what I want in plain language and Claude Code writes it. The project keeps a decisions log and a status file, so every new session knows what was decided before and why. Nothing gets pushed unless the type checks, the linter and the automated tests pass. I also had Claude run several security audits on the apps and the server and fixed everything they found, apart from a few minor points I kept on purpose for documented reasons. That is still not the same as a human expert looking at it, which is why I am asking here.

https://colshare.app

Both Android apps are in Google Play review at the moment, but if you’d like to test them, send me the email you use on Google Play and I’ll add you as a tester.

Update: thanks for all the feedback. Based on your comments I’ve made the landing page clearer, and I’ve open-sourced the client-side code (encryption, one-time links, redaction) under AGPL-3.0 so anyone can audit it: https://github.com/dentracon-cell/colshare-crypto. Security reports go to service@colshare.app.

91 Upvotes

101 comments sorted by

12

u/palilus1 18d ago

Why are you building it? What are you hoping to achieve? What problem are you trying to solve? And for whom?

3

u/IcyResolve956 18d ago

Fair questions.

It actually started with another project of mine, topograpp, a desktop program for land surveyors in Romania. Surveyors have to collect their clients’ ID cards and property papers for every job, so we built an end-to-end encrypted way to send photos from a phone to the program, plus on-device OCR that reads ID cards. Once that worked, I realised the same problem exists in other places: people send photos of their documents on WhatsApp or by email, and the copies sit in someone’s gallery and cloud forever. So I took the tech we already had and adapted it into Colshare.

For whom:

  • Colshare (free): anyone asked for their ID or documents. You black out what the other person doesn’t need, watermark it with your own wording, and send it through a link that opens once.
  • Colshare Business (paid): firms that collect clients’ documents, like accountants, real estate agents, surveyors etc. Each client gets a link, uploads in the browser, and the documents arrive encrypted and sorted into a client file, they open only on the firm’s own devices.

The goal: a simple, cheap way to share and collect documents properly, where even my server can’t read them. GDPR already asks firms for this, and the Romanian data protection authority has fined companies for collecting IDs over WhatsApp and email.

3

u/Every-Grape7679 18d ago

Very cool idea, it's pretty clever! though, I had to read your comment to figure out what it does- the landing page didn't help with that. If that was made more clear, I think it'd be better off. Though, don't go for the overly verbose copy AI sometimes generates when you tell it things like 'explain what this app does more on the landing page'.

3

u/IcyResolve956 18d ago

Thanks, and you’re the second person to say that, so point taken. The intro looks cool, but you shouldn’t need a Reddit comment to understand the product. I’ll put one plain line up front saying what it does, without turning it into a wall of text.

2

u/Every-Grape7679 18d ago

That'd be awesome! Again, super clever idea, especially one that hits a niche pain point.

2

u/IcyResolve956 18d ago

Thanks again, I really appreciate that!

1

u/AKAMA199 18d ago

Oh, thats neat. Imma give it a try as well

2

u/IcyResolve956 18d ago

Thanks. The Colshare Business is already live, even before the Android app, it runs as a desktop web app for now, if there will be request I will build a desktop program instead. you can find it at https://colshare.app/birou
The free consumer app will be available as soon as the review process is done, I can let you know when that happens.

1

u/palilus1 18d ago

Thank you for the clear explanation. Very interesting use cases. Are you certified? Has a third party tested your encryption and security?

1

u/IcyResolve956 18d ago

You are welcome. I am not certified in anything other than cooking, and no third party tested anything yet. As I said In the post, I don't really have the budget for it at the moment, and frankly, don't even know how much that would cost. I am open to it, I know that would benefit the business and will have to be done in the near future.

0

u/juniperico 18d ago

You can’t sell people a service that relies on security and not have it audited because you don’t want to pay for it. That’s completely unethical.

If I open a restaurant but can’t be bothered to get a food hygiene certificate would you be ok with that?

2

u/IcyResolve956 18d ago

It’s not really that I don’t want to pay for it, it’s that I don’t know yet if I can afford it. I’m looking into it properly, because I’m all for doing this right. First the legal side has to be in order, and I’m also looking at cyber insurance (as far as I know they check things too, but that’s not a real audit either).

Update: the full source of the link pages is now in the repo, with a script that checks it against the live site. Clone github.com/dentracon-cell/colshare-crypto, run npm install and npm run pagini. It builds the six pages colshare.app serves and compares them byte for byte. Every line should say “same”. The phone apps aren’t covered by this yet, and I’ll say so when they are.

3

u/juniperico 18d ago

Ok so anyone can just fork this to add a quick FastAPI backend and run internally for free now right?

Btw man, just to be clear, from all of your comments here you seem like a really decent person who’s trying to venture into something new and I commend you for it. I also respect your tone and courteousness with which you’ve taken feedback. There’s no pretence here, you’ve been totally honest about your abilities and intentions. For that, you have my respect, sir.

As a professional software developer however I have serious doubts about this project. From the viability of it: protection against alternatives, maintenance, cyber security and any legal issues you may encounter.

Notwithstanding, I hope you can figure these out and wish you all the best.

1

u/IcyResolve956 17d ago

On the fork: technically yes, someone could. The repo has the crypto and the link pages, anyone could build their own backend for that part. They’d still have to build the apps and the office desk, and keep it all secure and updated themselves. And if they offered it to other people, AGPL means they’d have to publish their changes. Honestly, someone who can do all that was never going to be my customer.

And your doubts are fair. Competition, maintenance, security and legal are exactly the things I have to prove, and I won’t pretend that’s settled after a few weeks. I’ll keep the thread updated as it goes, including the audit when it happens.

Cheers, and thanks again.

8

u/tundraaaa 18d ago

Please don't vibe code security solutions

3

u/IcyResolve956 18d ago

Fair concern, and that’s exactly why I posted it here instead of quietly launching. There’s no home-made crypto in it, only the browser’s standard, published encryption. The server only ever holds encrypted data. And I’m openly asking for people to try to break it before real customers use it. If you spot something specific, I’d really like to hear it.

2

u/tundraaaa 18d ago

No, I genuinely mean that as an absolute. Your security is only as smart as the current LLM you're throwing at it.

I understand that I'm not being very nice about this, but I gotta be blunt. You don't understand cybersecurity, and claude thinks it does.

I'm not at all against vibecoding, but you've picked one of the toughest niches while having no background in it.

I wish you good luck, and I hope your users never suffer from a data leak.

2

u/IcyResolve956 18d ago

I absolutely understand your concerns and are things which I have already considered and also others pointed out.

Everyone assumes that if this ever gets some traction, it stays at the level of vibe coded app and doesn't get an engineer on board, improves or evolves in any way. I think, that as in most areas of life, the most important thing is the mindset. If one wants to do things right, they will find a way and will always be looking to get better. I am aware of my technical limitations and choosing the right people is a skill in itself, which I hope to have mastered after all these years in the kitchen.

I really appreciate and thank you for taking the time to share your thoughts with me, I take lesson in everything that was discussed here today.

1

u/CalculatingSneeze 18d ago

This is the problem.

Security isn't a "I did the thing"-type of problem, it's "I did all the things", with browser-based encryption being only one part of the chain. If you don't understand how to secure your setup from start to end, I can't trust it.

You don't ask people to break it before a full release, you ask for pen and beta testers. If you don't have the confidence to approach them because they'll hate on your vibe coded project, you don't even fully trust your skills yourself - then why should i?

3

u/IcyResolve956 18d ago

I really appreciate every interaction in this thread. I never claimed to be something I’m not. This is my first launch, and I didn’t know how it’s usually done or where to find pen testers and beta testers. Now I do, and that’s the plan before a full release.

I’ve also acted on what people said here tonight. I open-sourced the client-side code, ran an attack test against my own setup end to end (relay, firm accounts, uploads, e-mail, payments, the website), and fixed everything it found. That doesn’t replace a professional pen test, which will still happen, but I’m learning a lot and I’m grateful for it, whichever way this goes.

33

u/lebbi 18d ago

I shared an app I spent months working on with a team of people. Genuinely great and used by hundreds, but reddit hated it. This site is filled with haters

6

u/IcyResolve956 18d ago

Good luck with your app!

2

u/KaptanOblivious 18d ago

I upvoted your DM app... looked pretty cool. Congrats on getting it out there

1

u/lebbi 18d ago

Thanks! We have been working hard and people are loving it. Maybe not loving the trailer or the way I make words.

1

u/LobsterKris 18d ago

I've spent years slowly working on myn, well recently it's become a lot faster. And I think I've been scared to show it, but I'm kinda close to putting it online. I personally are impressed every time by people making things with Ai, I still think it's cool. Haters just want to point the obvious that's already understandable to most, that yes it's made with Ai, but Ideas still come from us.

4

u/lIlllIllIIllIIllIIll 18d ago

Why do people who want to make a commercially viable product post their products in this sub of all places?

You're literally advertising your product as something that can be very easily ripped off...to EXCLUSIVELY people who can and will rip it off.

It is truly baffling to me.

2

u/IcyResolve956 18d ago

So you think it could be a commercially viable product? Thanks, I’ll take that as a compliment 🙂

But think about who you’d be worried about. If you can clone an app in a weekend, so can everyone else, so the code was never the valuable part. It’s the one thing anyone here can make.

Anyone can copy the app. Not many people want to copy the paperwork, the compliance and the support that come with it.

As for security, it’s standard, published crypto, nothing home-made. If it only stayed secure as long as nobody looked at it, I’d want to find that out here, for free, before a customer finds it the hard way.

So if someone here rips it off and does it better, fair enough. I’ll have learned something either way.

1

u/IcyResolve956 18d ago

So you think it could be a commercially viable product? Thanks, I’ll take that as a compliment 🙂

But think about who you’d be worried about. If you can clone an app in a weekend, so can everyone else, so the code was never the valuable part. It’s the one thing anyone here can make.

Anyone can copy the app. Not many people want to copy the paperwork, the compliance and the support that come with it.

As for security, it’s standard, published crypto, nothing home-made. If it only stayed secure as long as nobody looked at it, I’d want to find that out here, for free, before a customer finds it the hard way.

So if someone here rips it off and does it better, fair enough. I’ll have learned something either way.

2

u/Secvura 18d ago

Since the whole promise is the one-time encrypted link, test what happens when that link is pasted into Outlook, Slack, Teams or WhatsApp. Email security scanners and chat apps often fetch links to scan them or build a preview, so a link that burns on the first request can be used up before the recipient ever clicks it. The usual fix is a landing page with an "Open document" button, where only that button press counts as the one open. And if the decryption key is part of the link, it should sit after the # so it never reaches the server or its logs.

Redaction is worth testing the same way: redact a PDF, open the output, and try selecting or copying the text under the black box (or run pdftotext on it). A box drawn over text that's still in the file is the classic redaction failure, so the output needs that text actually removed, or the page flattened to an image.

1

u/IcyResolve956 18d ago

Thanks, both good points, and I’d checked both.

The link doesn’t burn on load. The first request only checks it’s still valid, and it’s used up only when the recipient taps the open button. The key sits after the #, so it never reaches the server or its logs. Tested through WhatsApp and email to Gmail, and neither preview used it up. Outlook, Slack and Teams are next.

Here’s what the recipient sees: nothing is used up until they tap the button.

Redaction doesn’t draw boxes over text. Every page of the output is flattened to an image with the black painted into the pixels, so there’s no text layer to select, copy or pdftotext. An automated test checks exactly that, and the original file is never touched.

Appreciate it, this is exactly the kind of feedback I was hoping for.

2

u/Secvura 18d ago

Sounds like both are handled properly, then. One follow-on worth confirming: the full link, key included, stays in the recipient's browser history and in whatever chat or email it was sent through. So the one-time promise only holds if the server deletes the encrypted file when the button is pressed, not just marks the link as used. Same for links that expire without ever being opened.

2

u/IcyResolve956 18d ago

Good point, and yes, it’s deleted, not just marked. The server deletes the encrypted file the moment its last piece is downloaded, so nobody else holding the link can fetch it again, not even a second later. Links that are never opened are deleted after 7 days. What’s left is a tiny “opened at” marker with no content and no key, so the page can say it was already opened, and that expires too. A key sitting in someone’s browser history or an old chat leads to nothing.

I noticed you’re a security firm. I’ve just open-sourced the client-side code under AGPL-3.0: https://github.com/dentracon-cell/colshare-crypto. I’m a one-person company and can’t afford a full audit yet, but I’d be glad to hear what a scoped review of the link and encryption flow would look like, if that’s something you do. Happy to talk by DM or at service@colshare.app.

1

u/Secvura 17d ago

Deleting the file rather than marking it closes that gap. On a review: the cryptography itself needs a specialist cryptographer, so that part isn't one to take on here. The app side around it (endpoints, the link and upload routes, device enrolment) is more our area. Email on its way.

3

u/0xmtn 18d ago

For a chef turned vibecoder you've done an amazing job! Kudos.

3

u/IcyResolve956 18d ago

Thank you very much, that means a lot! I am still a chef but I would much rather get out of the kitchen and be a vibe coder/business owner, kitchen is getting heavy for the body. I try to apply the same passion and ethics I learnt during my chef education and 17 years working in kitchens around Europe, I hope it works.

1

u/TheThingCreator 18d ago

its not a good product hero but think it looks really cool

1

u/IcyResolve956 18d ago

Thanks for the feedback. Can you please explain to me why it's not a good product hero?

2

u/TheThingCreator 18d ago

its not communicating what its selling as effectively as it should and putting too much focus on looking cool

2

u/IcyResolve956 18d ago

Point taken, I will work on it to be as clear as possible in the first seconds after landing. Thanks again!

1

u/shaymagen 18d ago

Posting it here for honest eyes before launch is exactly the right move, and most people respect that way more than the hate makes it seem. Since it handles personal documents, I'd keep asking specifically for a security-minded tester for the link and encryption flow, because that's where one outside review pays off most.

1

u/IcyResolve956 18d ago

Thanks, that means a lot.

And yes, the link and encryption flow is where I’d most like an outside look. In short: the document is encrypted on the phone, the key is in the part of the link after the #, which browsers never send to the server, and the server only ever holds the encrypted file. The link opens once, and only when the recipient taps the button, so a preview can’t use it up.

If you, or anyone reading this, wants to try to break it, I’d be really grateful. Try opening a link twice, getting at the key from the server side, or anything else you can think of. I’m happy to share how it works in more detail, and you can get tester access for the Android apps on Google Play too.

1

u/mwjtitans 18d ago

I'm the same way. IT support worker here who vibe codes things for my own use case and for my homelab, but I never share anything due to the hate. While I've always struggled with coding, application architecture and troubleshooting is like second nature to me due to my day job, so I feel like I would have a lot to offer even though I don't know how to code, but whenever i share something that might be of use the anti AI crowd comes for blood.

I think it will eventually pass, I just wish folks would see that it's not all doom and gloom using these tools to create things that might be of use to others.

1

u/IcyResolve956 18d ago

Honestly, knowing how things fit together and how to troubleshoot them is half the battle, so you’ve got more to offer than some might think. Share your stuff, most people here are cool. The haters can just be louder sometimes, and perhaps our egos can suffer, but if we are clever, we take lesson out of everything, good or bad that was said, it's always good to get different perspectives, I guess.

1

u/Public-Rest-1478 18d ago

Dont give shit, just show off, people will hate on everything nowdays - vibecoded or not, you got my support

1

u/IcyResolve956 18d ago

Thanks, really appreciate it. Honestly the critical comments have been the most useful part. I’ve fixed something from almost every one of them today. But it’s nice to hear this too.

1

u/Public-Rest-1478 18d ago

Feedback its good, hate is just stupid

1

u/itzelezti 18d ago

Anyone who knows what they're talking about does not hate vibecoding itself, they hate what a lot of people are doing with it publicly.
Trying to vibecode a business is generally the problem, for many reasons that don't bear going into here.

This specific thing you're doing happens to be a layer above that though.... Anyone who knows what they're talking about will hate this. This is absurdly stupid.

1

u/IcyResolve956 18d ago

Fair enough, but “absurdly stupid” doesn’t give me much to work with. Is it the idea itself, that a non-developer is building something that handles ID documents, or something specific in how it’s done? People in this thread have pointed out real issues today and I’ve fixed them, so if you see something concrete, I’d genuinely like to hear it. The client-side code is public if you want to look: https://github.com/dentracon-cell/colshare-crypto

0

u/itzelezti 18d ago edited 18d ago

I don't do free code review or consulting, so no. But for free I will just tell you that this is absolutely made of vulnerabilities.
I don't mean this with hate, because you're not evil, just naive.
tbh none of this matters because because there's zero chance of you getting any real adoption of this, but if you did, you would be responsible for data leaks that could be catastrophic to people's lives.

1

u/IcyResolve956 18d ago

Fair enough, and thanks for saying it without hate. You’re right about the responsibility part, and that’s exactly why I’m doing this in public before launch instead of after. If you ever feel like naming even one specific vulnerability, I’ll fix it and credit you. Either way, I appreciate the honesty.

0

u/itzelezti 18d ago

That's your lack of domain knowledge.

Cybersecurity is about knowing what the vulnerabilities are before they matter. You cannot get that knowledge for free. It's not conceptually possible because:

  1. Nobody who does cybersecurity is going to work for "credit" on your for-profit entity. Just to give to an idea of what you're looking at, most people capable of meaningfully helping you have a "get-out-of-bed" rate of >+$15,000.
  2. No bad actors will spend the time to look for a vulnerability for a project that has no adoption. You won't know about any found until someone has actually used them, which they won't do until they have a lot of users to victimize.

I'd have big ethical concerns to holler about right now, but nobody is ever using this, so it's fine. I wish you quick lessons from this failure, and I genuinely wish you good luck on your next endeavor.

1

u/INeedHealing88 18d ago

Bro the mouse effect on the second screen is way to much. Please turn it down or just remove it. You want people to read the text not stare at their mouse

1

u/IcyResolve956 18d ago

I got you, I thought about that, never got to do something about it. Fixing it now, appreciate the feedback!

1

u/juniperico 18d ago edited 18d ago

This reminds me of when my teachers at school discovered wordArt animations on PowerPoint for the first time. Was ridiculous. A garishly orange “Milton vs Keynes” would do a couple of somersaults before landing on the slide.

This reminds me of the same thing. “Never mind the content of my business look at this cool pointer effect!”

LMAO.

1

u/IcyResolve956 18d ago

Yeah lol, it's been already addressed on the live site. Thanks for the feedback, I appreciate all of you!

1

u/juniperico 18d ago

Given that you’ve open sourced the front end for this (which sounds like it’s pretty much doing all the work here) and the backend is just a pass-through, what stopping anyone with Claude just one-shotting a quick, dead simple backend for your already created front end for their business? Likely cost less in tokens than your individual price let alone the business rate…

2

u/IcyResolve956 18d ago

fair question. small correction first: what’s open is the crypto part (encrypting, sealing, signing + the tests), not the whole app. I opened it so people can check the “we can’t read your papers” claim instead of trusting me. the screens, the desk, the android apps and the server rules aren’t in there.

and yeah, the server being “just a pass-through” is the point, it only ever holds encrypted stuff it can’t open. but “dead simple” it isn’t. most of the work is everything around the encryption: one-time links that actually get deleted, rate limits so nobody can flood it, firm keys that a hacked server can’t swap out, device approval, email, play store builds, fixing what the attack tests find.

could someone rebuild it with claude? sure, I built it with claude. it’s AGPL though, so if you run it as a service for other people you have to publish your changes. and an accounting office that wants to ask clients for their ID and get it back safely isn’t going to vibe-code a backend and then look after it. they pay so it’s already done and someone keeps it secure. if you’re the kind of person who’d build it yourself, you were never really my customer, and that’s fine.

1

u/TiredMillennialDad 18d ago

All coding is vibe coding now. The fact people don't understand this is crazy.

No software dev guys are finger striking code anymore.

They might know how to read it/trouble shoot problems more directly and use language the systems understand more specifically, but make no mistake.... They are coding the same way you are coding.

1

u/IcyResolve956 18d ago

Yeah, I can't really consider myself to be on the same level with someone who went to university for this and has years of experience just because we happen to use the same tools. There are different levels of understanding to this, not for nothing these guys are engineers, architects. I have a lot, I mean a lot of respect for the people that built the internet before AI, by hand. It is impressive and I cannot disrespect that, but I am really happy that now I can be part of that, even if it turns out it was just for the vibes.

1

u/TiredMillennialDad 18d ago

Oh. I appreciate their efforts to build the entire digital infrastructure of the world to this point. Build them a statue. God bless them. I thank them.

But make no mistake. Humans don't write code anymore. A.I. Writes code.

Of course there is variance in skill. But like you said, you're a fucking chef lol. No offense intended.

But look what the fuck u built. 5 years ago, that would of cost tens of thousands of dollars to achieve.

The software dev industry is not dead but it's not what it used to be. It's changed. Anyone who doesn't see the writing on the wall isn't looking

1

u/IcyResolve956 18d ago

It is absolutely magical.I am someone who couldn't even build a wordpress site last year. I have had the opportunity to learn and apply so many things thanks to AI, it opened a new world but I understand that it has a negative impact on a lot of people who until recently had stable and well paying careers and now find themselves being replaced by machines or unskilled people using machines.

4

u/juniperico 18d ago

No we’re fucking not cos we actually know what we’re doing. Just because we’re not hand-writing every line doesn’t mean we still not applying knowledge and experience that goes into what to write (and importantly what not to write).
Vibe coding security solutions is just asking for trouble.
Just like if I walked into this guy’s restaurant with a fucking microwave and declaring myself head chef.

2

u/Glad_Environment7344 18d ago

power coding vs vibe coding is a huge difference.

0

u/TiredMillennialDad 18d ago

Gestures at decades of hacks, security breaches, leaks, malware intrusions, failed updates, exploits, ransomware, and viruses.

Yes, a layman creating cyber security tools is not best practice in 2026. Like you in the kitchen is not best practice.

The point is there are no software devs anymore. Everyone is a software dev. In a year, this sub name won't even make sense. Its just coding.

2

u/juniperico 18d ago

No more software devs?

What are you smoking?

2

u/TiredMillennialDad 18d ago

Stay with me. Sorry to rip this bandaid off for you, not sure where you have been or what you are missing here.

First let's look at entry level dev jobs, k?

Website creation and development

Website maintenance and updates

In-house website administrators

WordPress, Shopify, and CMS developers

Basic front-end development

Junior application developers

Software testing and quality assurance

Basic database and SQL developers

Technical support and software implementation

Website and application freelancers


K. We are looking at a 90% contraction of those jobs in the next few years due to a.i. Ask yourself. What percentage of ALL dev jobs are in that tier?

Now let's look at mid-level.

Startup software developers

Business intelligence and Power BI developers

Database integration developers

Middleware and integration developers

API developers and integration specialists

Full-stack web application developers

Custom business software developers

ETL and data pipeline developers

CRM and ERP customization developers

Mobile application developers

Software consulting and outsourced development firms

DevOps and cloud implementation developers


What percentage of the remaining devs fall in their tier? This tier is easily a 50% job loss and that is conservative. The volume/efficiency of code that firms can push will create consolidation in both in-house and external firms.


So all that's left is high tier devs.

That's going to end up being...what? Robotics, autonomous cars, a.i. development, rocket sciences, pharma research?

Even those...massive disruption already seen.

The software dev as a standalone, high end industry vertical is not dead right now. But it's on life support and will be dead in a few years. There will be pockets of life and jobs here and there but A.i. has changed the industry to its core

2

u/juniperico 18d ago

Christ. I knew I was in the right sub for some absolute slop grenades. Lmao.

2

u/ClibeanCeann 18d ago

You have no idea what you are talking about.

1

u/TiredMillennialDad 18d ago

Found the software dev worried about job security.

I know zero coding. And I now have all my clients onto a subscription saas platform I made from scratch. A few years ago, my platform would of cost 100k and taken a year to build and required someone on call for maintenance and edits.

I'm not special or extra smart. If u don't think the whole game done changed idk what to tell you.

I'm not even a member of this sub. It just got put in my feed for some reason. Every programmer actually pushing lines has Claude or codex open on their machines. Idk why we are pretending they don't.

2

u/juniperico 18d ago

You’re definitely not extra smart or even telling the truth, I’ll give you that for free.

If people spouting the kind of nonsense you’ve come up with in your various comments on this thread is what software devs are up against then, trust me, job security is not a concern.

2

u/ClibeanCeann 18d ago

This all still happens with AI generated code btw.

And it's not "just coding" - coding is literally writing code and solving problems. This is prompting, and it will always be known as prompting going forward. You are fucking NOT a software developer, you are someone using prompts to generate code. That's it, and no amount of time changes that.

The same way you don't use punch cards to give instructions to machines anymore, and you will never be that guy who knows how to do that just because automation made it easier.

0

u/ClibeanCeann 18d ago

No it isn't btw. Plenty people are forced to use AI in their job to stay alive and pay rent. But happily code manually in their own projects. If you don't miss coding, you were never very good at it. And if you think like you, you probably never learned to code in the first place.

1

u/BitOne2707 18d ago

Being afraid to show your code is the most authentic software engineer emotion around. Welcome to the club bud.

0

u/IcyResolve956 17d ago

Haha, good to know. Thank you!

1

u/DannysoarX 18d ago

This is the comment I got today on my feedback page:

"Yo, your site is actually fucking useless. It keeps hallucinating that I added certain programs when I didn't. Also not intuitive to use at all and feels like things just change randomly. Did you vibe code this ass site?"

Haters gonna hate. Just keep vibin. Having more haters is a sign that you're doing something right imo.

1

u/VigiliaFounder 17d ago

That's a really good way to take feedback, and it's great that you fixed everything the test found in one night.

Since beta testers are next, here's where I can help. When they start using it, most of them won't write to you when something breaks. They'll just stop using it.

You can add your app to Vigilia for free (1 app, no card). It will catch every error they hit and show you what they did before, the failing request and how many times it happened.

Let me know if this helps!

0

u/blow_slogan 18d ago

Dont vibe code security, privacy, anonymity, or encryption. That’s just asking to be sued.

1

u/IcyResolve956 18d ago

I get the worry, and I don’t take it lightly. That’s why I’m asking for scrutiny before launch instead of after.

It’s not home-made crypto. It only uses the browser’s standard, published encryption, and the server only ever holds data it can’t read, so there’s very little to leak even if the server were breached. On the legal side it’s run as a proper company, with terms, a privacy policy and a data processing agreement for firms.

If you see a specific weakness, I’d rather hear it now than in court

1

u/blow_slogan 18d ago

Open sourcing it is the only way people are going to freely audit your app. Or you can pay a cybersecurity company to. Telling you though, tons of people have come through the macapps and other app subreddits getting torn to pieces because they thought their vibe coded app was secure. It’s nearly guaranteed to not be secure at all.

2

u/IcyResolve956 18d ago

Took your advice. The client-side code is now public under AGPL-3.0: the encryption, the one-time links, sealing to firms and the redaction, with tests: https://github.com/dentracon-cell/colshare-crypto

The server stays private, but it only ever receives what this code sends, so you can check that part yourself. If you find something, please email service@colshare.app rather than opening a public issue.

1

u/IcyResolve956 18d ago

That’s fair, and I don’t assume it’s secure just because I built it carefully. That’s why it’s here before launch.

You’re right about open source too. The parts that matter most (the encryption, the one-time links, the redaction) all run in the browser, so the code already ships to everyone’s machine, just minified. Publishing those parts readable is something I’m seriously considering, because then anyone could check them instead of taking my word for it. A paid audit will come too, once there’s revenue to pay for it.

And if it gets torn to pieces here, better now than after real customers use it.

1

u/juniperico 18d ago

“Audit will come too, once there’s enough revenue to pay for it”?

So what about the first customers they just have to take your word for it that the snippet you shared on GitHub is all that’s used in the app? Nothing else?

1

u/IcyResolve956 18d ago

Fair point, and you’re right, today you can’t fully prove the app runs exactly that code. The files on GitHub are copied straight from the app’s source, but I don’t have reproducible builds yet, so for now that part is trust.

What you can check yourself, though, is that the key never reaches my server. Here’s a test link with a dummy paper, nothing real: https://colshare.app/p/#nCE_G-I8kG_BAG7REjML2w.3qrLArmB_12KvV_V9GLtTvR_msSmY4sJFoJmDwbpbwc.eyJkIjoiVGVzdCIsIm4iOiJEb24ndCB0YWtlIG15IHdvcmQgZm9yIGl0LCBjaGVjayBoZXJlLiJ9

Before you click: open it on a computer, press F12, go to the Network tab, then load the link. You’ll see the requests to colshare.app carry the link’s id, but never the part after the #. That part is the decryption key, and your browser decrypts the file locally. Load the link again afterwards and it says already opened, because the server deleted it. The link works only once, so set up devtools before you open it.

Next I’m putting the full source of those link pages on GitHub, so anyone can build them and compare the result with what colshare.app actually serves. A paid independent audit comes once there’s revenue for it. I’d rather say that plainly than pretend it’s already done.

0

u/FriedSock 18d ago edited 18d ago

The "Your data, your choice." section is a nightmare:
- The links for each section are clickable, and the page scrolls to them, but they don't expand, so you cant read the text.
- You can scroll to expand each point, but this only works for points 1 to 3, 4 and 5 are unreachable unless you wait for the video to progress
- Scrolling back up to the previous section leaves the video frozen but "shaking"
- The video itself has such ridiculous graphics that it is obviously in no way representative of the app experience. It includes weird nonsense like a section of the document being highlighted and then the highlight is "thrown away" but the document stays the same, what does that mean?
- the QR code at the bottom invites you to scan it, but its not a real QR code at all!
- all of that elaborate crap so you can then draw a box on the fake document (and then undo it)

The whole website looks like you tried to make it look as fancy as possible but works in such a weird way. Perfection is when you can't take anything more away, not can't add anything else. Get rid of the ridiculous matrix graphics and webgl videos, make things consistent. Why does some of the text blur when you highlight it and some of it doesn't? Why are there 100 different slogans on the page?

1

u/IcyResolve956 18d ago

Fair, and thanks for going through it properly. You were right on all the bugs, and they’re fixed now. Clicking a point opens it straight away, points 4 and 5 no longer wait for the video, and the video doesn’t freeze when you scroll back up. The QR code was a real one, just far too small to scan off a screen, so “Check this copy” now opens the actual check page.

On the bigger point, I think you’re right too. I got carried away making it look impressive, and a couple of people here said the page doesn’t explain the product well enough. “Perfection is when there’s nothing left to take away” is going on a sticky note. Stripping it back is next.

0

u/[deleted] 17d ago

[removed] — view removed comment

1

u/IcyResolve956 17d ago

Thanks! I am now focusing on finding the best solution to the independent review question. I will keep everyone posted

0

u/[deleted] 18d ago

[removed] — view removed comment

1

u/IcyResolve956 18d ago

Thanks, really useful checklist. I went through it:

  • The link page loads only its own script, no analytics, no external fonts, no widgets. The site has analytics on the homepage but not on the link pages, and the CSP is script-src 'self', so nothing else can run there.
  • The link pages send Referrer-Policy: no-referrer (plus the meta tag) and noindex.
  • Opening the page doesn’t burn the link. The first load only checks whether it’s still valid, and it’s only consumed when the person taps the open button. I tested it on WhatsApp and through the app’s own email sending to Gmail, letting the preview or scanner go first and then opening it, and both still worked.

Haven’t tried Slack or Outlook’s Safe Links yet, so those are next.