244 karma · joined July 31, 2012
[0] https://stackingthebricks.com/one-weird-trick-to-raising-you...
I did spend quite a bit of time on your site, linked sites, and webarchive. The files on your site did not work out of the box for me. I did eventually get a combination of kernel and configuration that kind of worked, but I think the CompactFlash card was too big. It stalled out on hard drive interrupts.
I took eight years but I also got married, worked full time, and started a company before I finished. By the time I graduated, the CS department had started taking a much firmer stance on timelines, with a desire for most students to graduate within six years or sooner.
> It’s a slightly unusual implementation in that the surface of the game is, in effect, spherical – i.e. the edges are effectively a feature of the projection of the surface but left joins to right, top to bottom and so on.
I believe that is a torus, and not at all an unusual implementation choice for the Game of Life.
If I change it to just check the first character for the file separator, as I understand FasterPath does, then of course it is faster:
Warming up --------------------------------------
original 4.109k i/100ms
faster 110.202k i/100ms
Calculating -------------------------------------
original 42.645k (± 3.7%) i/s - 213.668k in 5.017595s
faster 2.643M (± 4.4%) i/s - 13.224M in 5.013294s
Comparison:
faster: 2643274.6 i/s
original: 42644.5 i/s - 61.98x slower
My implementation: class Pathname
def f_relative?
@path[0] != File::SEPARATOR
end
end
[1] https://github.com/ruby/ruby/blob/68ebbbfebe5b666cf76ab41f1e...Edit: Also, "Howdaddyisdoing" is an anagram for "Why did I add goons" which seemed very suggestive.
1. Attacker knows victim's phone number and attempts login
2. Attacker intercepts SMS as it is sent to victim
3. Attacker completes their login process with the SMS code
This is rare for bug bounty rewards. All the programs I am aware of only reward the first reporter.
> By refusing to coordinate with the new submitter, the new submitter does not know if the vulnerability will ever be fixed and is reasonably justified in using public disclosure.
That's kind of what I'm pointing out here. We are missing information about what Facebook actually said and when it was said. The "we already know about it" response could mean "we know about it and are working on fixing it" or it could mean "we know about it and we don't care". In the former case, it is not responsible to publicly disclose the issue until it is fixed. In the later, it is.
A separate scenario is if the company is taking a long time to fix the issue. This is obviously subjective, but in my opinion it is understandable for a reporter to publicly disclose a long-standing issue in an attempt to force the company to act.