Diseased Open Source Software Community - it's about ethics in Code of Conducts

[Legalize Asbestos]

We already see constant fake bug reports

If you want to sperg out, I am here to listen. Why and how are people submitting fake bug reports? To bamboozle their competitors?

 

[Maldavius Figtree]

If you want to sperg out, I am here to listen. Why and how are people submitting fake bug reports? To bamboozle their competitors?

It's mostly shitskins asking chatgpt to find exploits in open source software and submitting whatever random noise results to bug bounty programs in the hopes of gibsmedat. It's like the Pearl Harbor of infosec, but with human stool instead of Japanese planes.

e.g. read here: https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-for-intelligence/

 

[Rancid Xylitol]

> Jeet corner cutting might accidentally lead to Microsoft products becoming FOSS through non-copyrightability
We really do live in the most blessed timeline.

With the amount of money MS gives to our brave and fearless overlords, the probability of this happening is about %0. Microsoft would send a few people to "educate" congress about their software and things would be OK dokey.

 

[Kola]

NO MORE BROTHER WARS

 

[Dual X99]

There is a lot of on-going drama and censorship over removing restrictions of the OP_RETURN command in the Bitcoin blockchain.
It all started in this Github thread [Archive]
An OP_RETURN is a command in a single Bitcoin transaction to store 80 bytes of arbitrary data that does not contribute to any transaction data. So, it can be used to store 40 ASCII characters like a memo on a check.
But, some people want to remove the limit so that you could store longer text messages or raw JPEG data.
Before to store an image on the blockchain, users would make a transaction with a 100 outputs with addresses to inaccessible wallets. When the addresses of the wallets are combined, converted to hex, you can stitch together the bytes for the image. But, the blockchain can only process 1 MB every 10 minutes. So, encouraging people to store large amounts of data in a seamless way can plug up the mempool and prevent people from making normal transactions at a reasonable price.

Now, the Github issue thread is closed even to senior members and I cannot even hit the thumbs up or down buttons on my account. If the tension is high enough, it could start another hard fork of Bitcoin over a novelty operation code that most bitcoin users will never see. Article covering twitter drama [Archive]

 

[Itchy Hemorrhoids]

But, some people want to remove the limit so that you could store longer text messages or raw JPEG data.

Didn’t some people put some pizza on the blockchain by doing this a few years back?

 

[YoRHa No. 2 Type B]

NO MORE BROTHER WARS

https://web.archive.org/web/20200401220835/https://knome.org/

Imagine if Knome wasn't just an April Fools joke.

 

[Dual X99]

Didn’t some people put some pizza on the blockchain by doing this a few years back?

Yes, the previous method for uploading images was much more hacky and relied on sending multiple transactions to wallets and parsing together the wallet data. It's like if someone were to send you the text messages:
Hi, how are you? 7e1a
Hi, how are you? 1a8b
Hi, how are you? f167
Then you take all of the hex bits afterwards and combine them. I don't think this sparked too many legal issues because you have to transform the data using unofficial methods that are not a part of the Bitcoin algorithm.

But after removing OP_RETURN limits, posting CP would be much easier since it would be a continuous stream of data that wouldn't have to be parsed together at all. If you see this example some blockchain explorers already automatically render OP_RETURN hex data into ASCII text. So, there might actually be legal issues because then you could just copy and paste the hex using a common tool to convert it to an image. But I don't know enough about the internal limits of each transaction to know the largest amount of data you can send in a single output.

I do not know how the legal system would react to a grainy 70 KB image of raw data being stored on thousands of nodes across the world.

 

[Itchy Hemorrhoids]

I do not know how the legal system would react to a grainy 70 KB image of raw data being stored on thousands of nodes across the world.

Hopefully with total crypto death

 

[Cuckoman]

Cuckomans law:
"Any technology will evolve to the point where trannies will use it to store CP".

 

[306h4Ge5eJUJ]

Bitcoin is a great technology in the hands of utter imbeciles who are physically incapable of learning and should just be euthanized for their own good. Every time I look at the Bitcoin space, it's like I'm back in 2013.

Didn’t some people put some pizza on the blockchain by doing this a few years back?

I think it was just a link to CP due to the heavy size restrictions. People have in fact called Obama a nigger on it though.

 

[Dual X99]

I think it was just a link to CP due to the heavy size restrictions.

I did a bit of research out of curiosity and apparently you can get up to a 4MB image. The witness data size is adjusted at a rate of 25% and bits are converted to virtual bits. So, the 4MB is stored as 1MvB in one block.
On this transaction
https://mempool.space/tx/4af9047d8b4b6ffffaa5c74ee36d0506a6741ba6fc6b39fe20e4e08df799cf99
If you go to "Inputs & outputs" > Details > "Show all" you can see the raw hex.

It's a funny transaction because it literally took up the entire block and pretty much paused the entire BTC network for 10 mins.
https://mempool.space/block/000000000000000000029edfc5e26ae20e0dd792491fd310a4d74d7102cdd587

They used Ordinals to encode/decode the data and the image can be viewed here. Apparently Ordinals had issues with CP so they took it down bad images from their site, but it's open source so if you wanted to download the blockchain and run the code yourself you can view any unmoderated image you want.

So, the blockchain is already fucked and filled with the raw hex of CP. The OP_RETURN data does not get the witness data discount so the Ordinals method is actually preferred even without OP_RETURN limits. At least that means that the courts don't care and Bitcoin can live a bit longer.

 

[Don Yagon]

At least that means that the courts don't care and Bitcoin can live a bit longer.

CP has been weaponized by feds for as long as Internet stopped hogging your phone line (e.g. see what happens to any altchan whose jannies leave their post for as little as to take a piss). I won't be surprised it was planted as some sort of failsafe in case Bitcoin becomes any sort of threat for mainstream banking system. Yet most people treat it as a fancy casino and store their money on custodial wallets, so I guess node operators can sleep soundly.

 

[Rancid Xylitol]

in case Bitcoin becomes any sort of threat for mainstream banking system

Bitcoin processes about 0.01% of the transactions handled by the global banking system, yet consumes over 50% as much electricity, making it roughly 4,500 times more energy-intensive per transaction. The banks worry about Bitcoin about as much as the average person worries about a meteorite impact. It's just not a danger.

Additionally, there's the inability to reverse transactions or control fraud. This is something really bad for the average person, because if they mess up, they are used to calling the bank's customer service. There ain't no one on the planet that can reverse a BTC transaction (unless you convince 51% of the current operators). Bitcoin will stay around forever as a store of value, but it will never, ever, ever replace Visa, Mastercard, or your local branch.

 

[One Angry Computer]

Bitcoin processes about 0.01% of the transactions handled by the global banking system, yet consumes over 50% as much electricity, making it roughly 4,500 times more energy-intensive per transaction. The banks worry about Bitcoin about as much as the average person worries about a meteorite impact. It's just not a danger.

Additionally, there's the inability to reverse transactions or control fraud. This is something really bad for the average person, because if they mess up, they are used to calling the bank's customer service. There ain't no one on the planet that can reverse a BTC transaction (unless you convince 51% of the current operators). Bitcoin will stay around forever as a store of value, but it will never, ever, ever replace Visa, Mastercard, or your local branch.

Huh, so if P=NP (in which the foundation of cryptography is assumed to be false) is resolved to be true, then Bitcoin will become much cheaper to operate and it will replace kikebanks...

Nah, we're better off with a Proof of Stake crypto system with an upper wallet size limit, rather than to force PCs sweat like body positive models just to buy mods for GTA San Andreas on Telegram.

 

[Billow Riley]

Bitcoin processes about 0.01% of the transactions handled by the global banking system, yet consumes over 50% as much electricity, making it roughly 4,500 times more energy-intensive per transaction.

Where are you getting these numbers?

 

[Ed Special]

with an upper wallet size limit

He said as if wealth hoarders and degenerate gamblers won't just make multiple wallets

 

[One Angry Computer]

He said as if wealth hoarders and degenerate gamblers won't just make multiple wallets

Call me an blind and foolish optimistic, but I believe that a limit of one million dollars per wallet is high enough for the average person, and a nightmare to handle for the hoarders and legal gamblers (stock traders). Sure, you could have a huge fortune, but to have dozens, if not hundreds of different wallets, each with it's own password or key, it becomes a liability to manage.

 

[SIMON THE PIEMAN]

Sure, you could have a huge fortune, but to have dozens, if not hundreds of different wallets, each with it's own password or key, it becomes a liability to manage.

This sounds like a problem that is easily solved by introducing a decentralized database system that is managed by thousands of independent parties (to avoid relying on one central authority). The parties that participate in this system could be rewarded with some sort of points for performing "work" to incentivize them to join this sort of scheme. The "work" would rely on some sort of a cryptographic proof that would also have the benefit of making the system much more resilient against tampering. I think I'd call this "proof of work" or something like that.

 

[The Real Slim Shady]

If you want to sperg out, I am here to listen. Why and how are people submitting fake bug reports? To bamboozle their competitors?

I think they either want to get noticed, become a famous white hat hacker who saved the planet earth or are just clueless and want to "help". In any case, waste of bandwidth and contributor time.

Just last week Daniel Stenberg changed the submission template for cURL bug reports because morons started submitting AI generated shit like "cURL can write outside working directory" (if you pass it a path with "../", perfectly valid use case) and "curl can use overridden CAs" which is also a normal feature of everything that uses TLS. They indeed can lead to privilege escalation if you are fucking stupid and don't sanitize user inputs.

archive / original

These reports are not necessarily AI, but there are cases like this too:

original / archive
report / archive