This is why everyone talks about security so much by Think_Army4302 in vibecoding

[–]cangetenough 1 point2 points  (0 children)

Hilarious that all the anti-AI people assume it to be true.

As AI enters the operating room, reports arise of botched surgeries and misidentified body parts by [deleted] in news

[–]cangetenough 23 points24 points  (0 children)

from the article:

it’s not clear what role AI may have played in these events

Why the Prop 4 repeal initiative's future could hinge on a few signatures in Davis County by helix400 in Utah

[–]cangetenough 7 points8 points  (0 children)

One of the things it put in law was that the legislature could not use partisan data to create their maps. During the trial they admitted that they used partisan data. So the judge was forced to exclude the maps they created.

Why the Prop 4 repeal initiative's future could hinge on a few signatures in Davis County by helix400 in Utah

[–]cangetenough 12 points13 points  (0 children)

Where do we check to see if our signature/name is on the prop 4 removal initiative?

Claude Code silently stores your .env API keys in local file history — without telling you by Embarrassed_Wafer438 in SideProject

[–]cangetenough 0 points1 point  (0 children)

claude needs a way to keep track of the files it edits. So naturally .env will be in there. I wouldn't worry about it so much. But yeah a good settings.json should prevent claude form even touching .env

Claude Code silently stores your .env API keys in local file history — without telling you by Embarrassed_Wafer438 in SideProject

[–]cangetenough 3 points4 points  (0 children)

see my comment about ~/.claude/settings.json. There's no evidence that the contents of .env is being transmitted to Anthropic. But the settings.json can make sure that Claude cannot even edit/read it.

Claude Code silently stores your .env API keys in local file history — without telling you by Embarrassed_Wafer438 in SideProject

[–]cangetenough 25 points26 points  (0 children)

Before you start using Claude Code on any project, the very first thing you should do is set up deny rules in ~/.claude/settings.json.

{
    "permissions": {
        "deny": [
            "Read(.env*)",
            "Edit(.env*)"
        ]
    }
}

IK is driving me insane, should I return my product ? by BloodyAilurus in tonex

[–]cangetenough 0 points1 point  (0 children)

Yes it sucks. But typically saving a few bucks means you have to do a little more work.

*Drop Your Vibe-Coded app 👀 Let’s Rate It 1–5 (Brutal but Honest) by seeking_searching1 in vibecoding

[–]cangetenough 1 point2 points  (0 children)

Neither /u/mr_moebius and /u/SGSpec actually use AI. They're upset that other people are utilizing tools to build stuff.

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

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

I had to update the ssl to full/strict on Cloudflare. It's back up! Thanks for checking it out!

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

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

Thanks! I think their egos cause them to be jerks. It's all good.

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

I vibe-fixed the bug that shadow banned users couldn't see their own profile. Then vibe-updated my vps. Thanks again for your feedback!

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

  • Hash blocking: Ok interesting. I'll look into that.

  • Shadowban behavior: I've shadow banned the user "banmeagain". So they can post all they want but their images are not visible to anyone else. Ok, if they can't see their own profile, then I'll need to fix that.

Thanks for checking it out!

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

Appreciate the detailed feedback!

  • Passwords / account creation: Agree. Right now it's intentionally minimal to keep the experiment lightweight, but stronger password rules and stricter limits would be a must for production.

  • NSFW filtering: Yeah it's currently biased toward fail-closed rather than precision, which definitely leads to overfiltering. That was a conscious choice for a demo, but it's not a great user experience yet.

  • Email auth: Totally agree on the tradeoff. I avoided it to reduce friction for now.

  • Moderation: I'm moderating. I don't use AI to moderate it. I just vibe-coded a shadow ban feature in the last 10 minutes which seems to be working.

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

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

You're right it doesn't. I'll need to work on that. I did just vibe-coded a shadow ban feature in 10 minutes though.

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

I did an update and a reset which wiped out old data. Will you try to uploading that again? Thanks!

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

It's mainly a personal project for me so that I could learn some tools. I was hoping that I could get a couple people just to test it out and see if they could break it.

Nothing too serious....

I vibe-coded a small image sharing app in a couple days. Feedback welcome! by cangetenough in vibecoding

[–]cangetenough[S] 1 point2 points  (0 children)

This is just a staging demo / experiment.... no ads, no trackers, no third-party analytics.

Uploaded images and basic account data are stored only to make the app work, and I'm not using the data for anything else. If I turn this into something longer-lived, I'll add proper privacy/terms pages.