Bitcoin Forum
May 05, 2024, 06:16:09 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Scam Accusations / Re: BetCoin.ag closed account and stole around 1 BTC on: October 31, 2020, 12:46:32 AM
Let me pull out an extreme for you.. If someone murders your SO in cold blood and you watch it happening, will you happily answer any questions the murderer has for you? If you say yes that will be quite silly.

That's a very poor analogy, bordering on irresponsible. Consider this analogy instead: "A landlord (Betcoin) believes that someone broke the posted rules of the apartment complex they manage, and know that the culprit had a grey Honda Civic with license plate XYZ (the bitcoin address) playing Wu-Tang (his bet choices). When Jimin Jibao pulls up to the apartment complex in the same vehicle playing Ghostface's Fishscale album, the landlord takes away Jimin's keys (account access). Jimin still has furniture and personal effects in his apartment, but does not know their value (current account balance)."

Based on that:

1) Can you see the difference in implied knowledge between your analogy (You watch it happening) and what Betcoin has publicly admitted (We know that Jimin and KILLYMNE used the same address and made similar bets)?
 
2) In the apartment analogy, do you believe that the landlord should refuse to answer any questions from a tenant whose property they currently hold? Can you see how the phrasing choice of "a murder" might be emotionally loaded in a way that "a property dispute" isn't?

You might find this nitpicky, but for someone representing Betcoin even marginally, you need to. Any professional relationship with them - especially a monetary one - means you should be holding yourself to a higher standard than regular posters to avoid any perception of dishonesty. In this case, I think you failed, champ.
2  Other / Meta / Re: Report plagiarism (copy/paste) here. Mods: please give temp or permban as needed on: May 24, 2020, 01:33:18 AM
A obvious Lauda alt, makes a valiant first post defending Lauda

stfu, Lauda

Did you even read the post? I gave examples of Lauda's posts having two grammatical "voices" - one unique to Lauda (with common ESL errors), and one shared by the alleged plagiarized content (with noticeably better use of punctuation, except for where Lauda is substituting in their own words, or "word-spinning").

I mentioned it backing up Kalemder's post:
Copy and paste a post. Then change it a little bit. Perform originalization. I'm sorry, but this is also idea theft. In fact, this is a worse crime. Honest people refer to the source.

Other posts are already completely copy-paste.

and Suchmoon's:
Having busted many word spinners I can assure you that plagiarism is not just "copying and pasting stuff". Why do you keep doing this? There is no point arguing that plagiarism didn't occur. It did. Mods will decide the rest. Should you find yourself in a similar situation you would want the same thing, not mob justice.

I fail to see in what universe this would be called "defending" Lauda. Either you're skimming (in which case, why even comment?) or you have reading comprehension issues that need to be sorted out.

Yikes!
3  Other / Meta / Re: Report plagiarism (copy/paste) here. Mods: please give temp or permban as needed on: May 23, 2020, 07:06:46 AM
Something that I find interesting in this situation is that there's a noticeable difference in grammatical errors between the alleged plagiarized content and the added "word-spun" filler - equivalent to the difference between a well-read-but-not-native English speaker and a native English speaker. These inconsistencies are sometimes clear even in the same quote. It adds credence to Kalemder and Suchmoon's comments regarding "word-spinning".

Bold emphasis is mine, red remains from previous posts in order to indicate alleged plagiarized content.




Incorrect comma usage:

Actually if SHA gets broken the problem will be on a much larger scale where Bitcoin will be irrelevant (unless globally adopted). A lot of things use SHA, for example banks.

What I'm trying to say is:
For SHA256, it effectively becomes SHA128 to a Quantum computer. Now the question remains, can a Quantum search for SHA128 faster than a classical computer search through SHA256?
With out current technology and for the near future, we still can't build a real Quantum computer that can even begin to tackle this problem, let alone solve it.


This is a noticeable change in comma proficiency mid-post. Non-native speakers often struggle with comma usage following introductory phrases: "Actually", used as an introductory phrase, is always followed by a comma.

The comma usage in "A lot of things use SHA, for example banks." reinforces this difference. A comma is (incorrectly) used to indicate an upcoming example, where a colon would be more appropriate. "A lot of things use SHA: for example, banks." would be grammatically correct but still clunky. "A lot of things use SHA: banks, for example." would be appropriate.

Compare this to AzN1337c0d3r's mirrored content, where we see much more consistent comma usage in the same situation:

For SHA256, it effectively becomes SHA128 to a Quantum computer. Now the question remains, can a Quantum search for SHA128 faster than a classical computer search through SHA256?
With our current technology and for the foreseeable future, we still cannot build a Quantum computer that can yet begin to tackle this problem, let alone solve it
in a time within our lifespan. Thus SHA256 is considered "secure enough" for now.



I see no information about 128 bit keys being broken. Any information found on stackexchange has no guarantee to be correct. It confirms what I said. SHA can't be reversed; it has to be brute forced.
It clearly indicated that quantum computers are more powerful than the computers of today, which is logical. There is no information on there internet about this. You're talking out of a hat.
Yes 128 bit security is 18446744073709551616 times faster to bruteforce than 256 bit. This doesn't mean that it is vulnerable when used.
It's obvious that people are commenting without proper knowledge in quantum related technology. The computers are not nowhere near ready to do any complicated jobs.
The main challenge in a Qcomputer is to make sure that the qubits are entangled (if you're familiar with Schrödinger’s cat you will know what I'm talking about; look that up). The computer must stay in this state (for the cat - it can't be simultaneously dead or alive) long enough to perform calculations and get results. The ones that we have can keep the state for miliseconds or maybe a couple of seconds. That's not long enough to do something useful. To break encryption these computers must have 500-2000qubits. Existing quantum computers operate with 14 qubits at maximum.
I have not forgotten about D-wave though. The company D-Wave claims that it has produced a 512 qubit Qcomputer. That is not a real quantum computer because it uses quantum annealing effect and can't demonstrate full properties of one. It is basically set to do a few specific tasks and represents no danger to encryption.
To summarize: You're wrong. Existing implementations have not shown that they can beat 128bit encryption. They aren't even close. That's the current situation. I'm not saying that in 5 years we won't have better technology. We might operate with 1400 qubits or be stuck at 140. Nobody really knows.

I've included two more examples of comma usage from above to reinforce that this does not appear to be a one-off mistake. "Yes 128 bit security is 18446744073709551616 times faster" and "To break encryption these computers must have 500-2000qubits." are both examples where the following clause needs to be indicated with a comma. Interestingly, the second example there is written correctly in the alleged source material:


To break cryptosystems, computers must have 500-2000 qubits (depending on the algorithm and key length), but existing quantum computers operate with 14 qubits at maximum.

I'm beating a dead horse here, but "I have not forgotten about D-wave though." should have a comma between "D-wave" and "though". Otherwise, an adverb will be confused for a conjunction with no follow-up (and thereby no function. Hah!)




Extraneous text:

Exactly how is spreading FUD related to retardation?
Fear, uncertainty and doubt (FUD) = is generally a strategic attempt to influence perception by disseminating negative and dubious or false information.
FUD (Fear, Uncertainty, Doubt) is generally a strategic attempt to influence perception by disseminating negative and dubious or false information.

One thing taught to all students in a second language program is "Read your sentence out loud." This is a common error when inserting symbols: incorrectly applied, you make existing text redundant. In this case, Lauda's version out loud would sound like "Fear, uncertainty, and doubt - FUD - equals is generally a strategic attempt...", while the alleged source material would be grammatically correct. To me, this is the most damning evidence of text edited post facto by someone with a different reading/writing level.




Again - these are mistakes you would expect to see consistently made. A fluctuation in the grasp of English grammar should not be seen mid-post, and definitely should not be clearly separated between the black text unique to Lauda and the red text of the alleged source material. I invite others to criticize as needed.

To be clear, I have no vested interest in whether anyone is banned or not. I have some opinions about what I consider to be flaws in Lauda's judgment (I don't believe that a word like "pajeet" can be separated from its intentionally-racist 4chan origins), but I find them largely irrelevant to this topic or the decision at hand.

inb4 "nice first post", "hop on your main acct", etc. The rules of language don't change based on your activity level. I've been a lurker for years, and a cursory mod search would show I'm not on TOR, not using a VPN, and have sent PMs to board members regarding similar topics.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!