News for hackers. Stuff that matters.

koil

Re:NPM debug and chalk packages compromised on Monday September 08, 2025 @02:30PM (#45171987)
As OC mentioned elsewhere, it was a targeted TOTP proxy attack.
I like the way target does it. No scale, no obnoxious cameras, they just have a limited amount of self checkouts and usually have security visibly posted near them.

I have yet to witness somebody not scanning things and stealing them from there, the only “success” I’ve seen is sprinting out a fire door.

Even worse is when a product has a bad barcode and the employee at the self checkout tells you to go across the store and find a different one instead of just fucking doing their job.

… no, I don’t hold a grudge, why do you ask?

I live right by Portland and have visited the three stores that are closing there. Every target in this area is hit hard by theft because there are many unhoused people who need things, or addicted people who need things to sell, and word got out that target wasn’t going to let their security people touch anybody.

The three stores closing here are some of the hardest to drive to, so it’s no surprise to me that the average payment size would be smaller and result in way slimmer margins there.

This is also following all Walmarts in town closing, likely for theft as well, Nikes employee store downtown closing due to theft and employee unsafety, and countless local businesses packing up shop and moving to other areas or shutting their doors.

It’s a shame but it’s so common in the area that the news didn’t surprise me in the slightest.

Re:Custom Minecraft Classic client written from scratch in C on Monday September 18, 2023 @08:20AM (#37555168)
The version on classic.Minecraft.net was deemed written from scratch to vaguely replicate classic last I heard. There were physics quirks, block textures, and entire blocks that weren’t ever in any version of classic, but were in that release.
Re:Custom Minecraft Classic client written from scratch in C on Friday September 15, 2023 @11:32PM (#37531803)
1 because the target version didn’t have any survival features, 2 because mojang absolutely would not appreciate it.
Re:Custom Minecraft Classic client written from scratch in C on Friday September 15, 2023 @11:31PM (#37531797)
I don’t think the provided webclient uses webasm, it’s just transpiled to js. It can be transpiled to webasm but there’s no benefit right now (and worse performance iirc)
Re:Custom Minecraft Classic client written from scratch in C on Friday September 15, 2023 @11:30PM (#37531788)
The author of the client just likes writing it. The owner of the website just likes running it too. Both have decent day jobs that cover the costs easily, so that’s nice.

I know the website owner has actually talked mojang’s legal team down from trying to take classicube down- the lack of modern Minecraft features essentially differentiates it from their product, assumedly it makes it much harder to sue for.

Re:Custom Minecraft Classic client written from scratch in C on Friday September 15, 2023 @11:28PM (#37531774)
It actually already almost fully works on all of those but the Xbox! Several players play on the Wii, GameCube, and 3ds. Most servers don’t work (due to ram and processing limitations) but they’re totally functional and mostly-stable.
Re:Custom Minecraft Classic client written from scratch in C on Friday September 15, 2023 @11:27PM (#37531767)
Fwiw re: lack of survival- mojang has tried (and backed off) to take down cc under the assumption it had crafting/survival. The lack of survival aspects is the only reason it’s still around.

That, and classic v .30 doesn’t have any survival features

Re:What Reddit Got Wrong on Wednesday June 14, 2023 @02:47PM (#36330691)
The Apollo dev agrees! Free api is not sustainable. It’s the proposed price that’s killing all major third party apps, and most minor ones, and Reddit has not only insisted that they won’t budge, but have even gone on to attack the Apollo dev directly while also stating in public that they do not offer analytics about an apps api usage nor will they help app developers (partners!) identify inefficiencies in their api usage- just tell them (publicly, with no warning) that their app is inefficient.