this post was submitted on 27 Feb 2024
36 points (100.0% liked)

Buttcoin

397 readers
17 users here now

Buttcoin is the future of online butts. Buttcoin is a peer-to-peer butt. Peer-to-peer means that no central authority issues new butts or tracks butts.

A community for hurling ordure at cryptocurrency/blockchain dweebs of all sorts. We are only here for debate as long as it amuses us. Meme stocks are also on topic.

founded 11 months ago
MODERATORS
 

cross-posted from: https://lemmy.dbzer0.com/post/15238521

Yet another "brilliant" scheme from a cryptobro. Naturally this caused a gold-rush for scammers who outsourced random people via the gig economy to open PRs for this yml file (example)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 9 months ago (9 children)

it’ll be fucking wild when my industry invents the ability to learn from its mistakes

[–] [email protected] 5 points 9 months ago (6 children)

also, of course it’s a bunch of yaml package recipes with wacky! comments barely wrapping the shell scripts actually doing the work, all of which are dumped into a way too fucking big recipes directory and shat into git, cause no this fucker didn’t learn a damn thing from last time

also, this rant in the recipe file:

FIXME proper system for re-using pre-built binaries we must require the vendor to provide signatures against a published public key. If they don’t then really we should build ourselves or warn the user about the fact. The thing is, we trust the sources implicitly currently because signing is so rare. The only way wide spread signing will occur is via our protocol.

I’m guessing protocol here refers to the tea bullshit that’s being hoisted on our global open source ecosystem. the part I’m missing is: fucking what? why? there aren’t any hashes at all in the recipe file which is how Nix and most other package managers worth a damn verify sources. Nix doesn’t even differentiate between source code and pre-built binaries for this — Nix just knows the expected hash for the file and if it pulls an archive of binaries, you just tell it to skip the build step as part of the package definition. pkgx doesn’t even have the immutable bits that make using pre-built stuff mildly harder on a Nix system

[–] [email protected] 5 points 9 months ago (4 children)

The only way wide spread signing will occur is via our protocol.

Sure, it's not like there's a whole protocol standard that you can use for signed provenance of binaries which you could incorporate and help promote to make the OSS ecosystem better and more secure.

Nah, look, I solved package management using only my grit and impressively large IQ.

I hate the energy of That Guy that barges into the room and shouts "I solved X!" without researching for 5 minutes what all the people that were actually hard at work solving X came up with, what hurdles they identified, and which paths were already explored.

And it's always fucking tech guys.

[–] [email protected] 4 points 9 months ago

I hate the energy of That Guy that barges into the room and shouts “I solved X!” without researching for 5 minutes what all the people that were actually hard at work solving X came up with, what hurdles they identified, and which paths were already explored.

Reminds me of the time I was at Barnes & Noble and this lady comes in with her little boy (4-6 maybe?) and they head for the children's section. At the entry to the children's section she tells him to go find a book, and they separate. He walks a step to the first display in the center of the entry area, grabs something, and shouts "Momma I found a BOOK."

load more comments (3 replies)
load more comments (4 replies)
load more comments (6 replies)