I'm just going to say that it should be implied by the style guide
We can watch any PRs for the wrong kind (plus, Python will not accept mixed in a single file, so they should at least be testing their code before committing)
But seriously, get a great text editor. Are you using Notepad still?
@Ethan is it okay that I am creating so many issues? If you don't want one, you should let me know. I just want to make the project better
And if someone doesn't know what to do, they can look at an open issue
Most of the stuff I'm doing now is bugfixes and stability improvements (I doubt that you would object to those :P), but let me know if you don't want a feature or something.
There was some merge issue when I ran git pull, and the test.py file had a bunch of the wierd characters in it that github inserted. So I edited those characters out.
> Yes, the website. Docs are often done in GitHub pages because it can render Markdown. It's looks nicer vs. doesn't require a pull request to edit. Personally, I like pages better, but I don't know what we want.
This seems like a hash collision but that shouldn't happen
> However, you should be aware of how ridiculously unlikely this scenario is. The SHA-1 digest is 20 bytes or 160 bits. The number of randomly hashed objects needed to ensure a 50% probability of a single collision is about 2^80 (the formula for determining collision probability is p = (n(n-1)/2) * (1/2^160)). 2^80 is 1.2 x 10^24 or 1 million billion billion. That’s 1,200 times the number of grains of sand on the earth.
> Here’s an example to give you an idea of what it would take to get a SHA-1 collision. If all 6.5 billion humans on Earth were programming, and every second, each one was producing code that was the equivalent of the entire Linux kernel history (1 million Git objects) and pushing it into one enormous Git repository, it would take 5 years until that repository contained enough objects to have a 50% probability of a single SHA-1 object collision.
> A higher probability exists that every member of your programming team will be attacked and killed by wolves in unrelated incidents on the same night.
Yesterday one of my team's checkins corrupted our github repo. On github, they were showing this error:
$ git fsck
error: sha1 mismatch 87859f196ec9266badac7b2b03e3397e398cdb18
error: 87859f196ec9266badac7b2b03e3397e398cdb18: object corrupt or missing
missing blob 87859f196ec9266badac7b2b03e33...
A birthday attack is a type of cryptographic attack that exploits the mathematics behind the birthday problem in probability theory. This attack can be used to abuse communication between two or more parties. The attack depends on the higher likelihood of collisions found between random attack attempts and a fixed degree of permutations (pigeonholes).
== Understanding the problem ==
As an example, consider the scenario in which a teacher with a class of 30 students asks for everybody's birthday, to determine whether any two students have the same birthday (corresponding to a hash collision as...
We shall report this to the reporters 2nd Monitor.
> Hello all. We'd love support for Cactus. We just hit 20 unique visitors, and we're working really hard on it. We have a website, subreddit, and a chat room. Thank you for the support!
That's what I posted in TSM ^^
Hey, I've made the subreddit un-private, so that users can post in it now.
> Sure. Can you please run the PR past me to make sure that all of the binding code isn't broken by this? It's easier just for me to check than for me to explain