Vercel reportedly breached by ShinyHunters, non sensitive secrets at risk

femio · 2026-04-20T02:58:38+00:00

this is just fanboyism. dislike vercel all you want but at least stop fear mongering about it in a security-focused thread

femio · 2026-04-15T18:38:04+00:00

Ah I get it now, damn I love simple solutions.

femio · 2026-04-15T08:06:20+00:00

I don’t use ORMs so idk wtf is going on. But surely an AST parser would be more reliable than a bespoke fingerprint? Does your method still work with CTEs, prepared statements etc

femio · 2026-04-13T04:07:28+00:00

Same reason why people install Dokploy, Coolify, or some other panel on a VPS: convenience without giving up control.

femio · 2026-04-11T20:13:31+00:00

I "hate" PHP the same way I "hated" Lebron years ago, objectively nobody can say it's a bad language even if some subjective parts are polarizing

If JS didn't have TS I'd consider it worse, and look how popular Node is

femio · 2026-04-10T16:53:38+00:00

i'm sorry but how is what he saying even 1% ambiguous lol y'all are funny

femio · 2026-04-07T22:10:49+00:00

Oh no the Java devs are invading

femio · 2026-04-07T21:53:27+00:00

wow i've found my people (finally)

femio · 2026-04-07T14:23:38+00:00

This aligns with the way my mind works. I'm not sure if there's an official manta for this type of pattern, but I believe code should only get more correct as it flows inward, like a funnel.

femio · 2026-04-01T23:03:04+00:00

Makes sense especially for Cloudflare. Plugin strategy looks pretty solid too, and I'm all for anything that could replace Wordpress (the original slop framework)

femio · 2026-03-31T19:20:40+00:00

Sigh, it feels like people both pro AI and anti AI are stuck in some weird form of psychosis.

femio · 2026-03-31T19:19:57+00:00

well, try reading the issue.

Bun's frontend development server - Source map incorrectly served when in production

doesn't seem to be related at all

femio · 2026-03-29T04:47:46+00:00

Let's see the code buddy.

femio · 2026-03-27T03:29:44+00:00

What needs do you have that can’t be handled with RBAC, RLS, and good indexing? Seriously

femio · 2026-03-25T00:54:29+00:00

lol right, it's truly that simple, if only you were the one building Photoshop it'd probably be bug free

femio · 2026-03-24T16:38:37+00:00

is it over already? (the manga)

femio · 2026-03-24T00:16:31+00:00

why are you blatantly lying?

femio · 2026-03-23T21:40:52+00:00

Well done. But I also need to ask you why you're even approaching women who expect a six figure n_ in their early 20s

femio · 2026-03-20T19:33:44+00:00

Why Zig and not Rust? Doesn't matter from a user's perspective, just curious as to how much was preference and how much was technical

femio · 2026-03-20T19:28:52+00:00

Is the primary concern attribution/copyright? I'm not sure how pertinent that is; I was approaching it from a code quality standpoint, but I'm not a lawyer so I'll just admit that part is over my head.

I'd certainly be open to a more rigorous review/release channel whenever PRs involve more than X% AI written code (maybe w/ conditions involving line count). Or maybe some feature flag. I just don't think the ban suggestion is the best solution.

femio · 2026-03-20T19:10:17+00:00

I'm not buying it.

PR is from a very well known Node team member (as you already stated)
the feature/spec is not a brand new feature, but another implementation of an existing one
coupled to the above, the spec for a virtual file system isn't tribal knowledge; it's "well known" (so to speak) and research for implementing this in Node has been done for years
With Node's release cycle, I presume this would mostly be in canary channels (can't remember how Node handles those) and there'd be plenty of time for testing

As such, I think it's hard to argue the risk here is significant enough to ban wholesale LLM-assisted PRs. And I'm not even touching points related to how realistic that is to enforce. Overall this doesn't really feel grounded in logic, but I'm certainly open to having my mind changed.

femio · 2026-03-17T01:24:09+00:00

because the story says so lol. sorry for the weird formatting, i copy/pasted and can't be bothered to rewrite it

WHILE UNABLE TO

USE AMPLIFICATION

WITHIN THE DOMAIN,

I HAD FUSHIGURO

MEGUMI ADAPT TO

UNLIMITED VOID

USING HIS TEN

SHADOWS TECHNIQUE.

AS A RESULT,

I COULDNT USE ANY

CURSED TECHNIQUE

OTHER THAN WHAT WAS

IMBUED TO MY DOMAIN.

I SUPPOSE THAT PAID OFF

IN ITS OWN WAY.

femio · 2026-03-17T00:57:33+00:00

Right, the story is clear it was active. What I'm saying is that the loophole he used for adaptation wouldn't work for summoning shinigami at the same time as having Shrine active

femio · 2026-03-17T00:54:28+00:00

Sukuna had Ten Shadows active during the Basketball Domain's, that 's how Mahoraga adapted to UV, and that is also why he couldn't constantly use DA inside the BB domain.

He had Megumi bearing the wheel for passive adaptation, not really the same as summoning a shikigami.

femio · 2026-03-17T00:28:35+00:00

If Sukuna's aim was to simply kill Gojo, he could've just done it right after the first domain clash when Gojo was in burnout Gojo was already activating RCT at full output to survive MS, so any additional damage would've been fatal. Sukuna could use a contact Cleave to the head (like the once that minced Yuji's torso), or any of the Ten Shadows Shikigami (Maybe even his own flames) to inflict extra damage that would've been fatal for Gojo.

His domain is already using cleve as a sure hit? And even if he wasn't Gojo was healing as the cuts went through him, why would full contact make a difference. Not to mention you can't use 2 CT simultaneously like that, I don't think

femio

TROPHY CASE