• 2 Posts
  • 67 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle


  • We set sail on this new sea because there is new knowledge to be gained, and new bragging rights to be won, and they must be won and used for the progress of all speedrunners. But why, some say, zero A presses? Why choose this as our goal? And they may well ask, why climb the highest mountain? Why, 55 years ago, fly to the Moon? Why does Mohun Bagal play the Delhi Capitals? We choose to do zero A presses. We choose to do zero A presses… We choose to do zero A presses in this decade and do the other things, not because they are easy, but because they are hard; because that goal will serve to organize and measure the best of our energies and skills, because that challenge is one that we are willing to accept, one we are unwilling to postpone, and one we intend to win, and the others, too.



  • All 9k stars, 10k PRs, 400 forks & professional web site are fake?

    Technically, it is entirely possible to find a real existing project, make a carbon copy of the website (there are automated tools to accomplish this), then have a massive amount of bots give 9K stars and make a lot of PRs, issues and forks (bonus points if these are also copies of actual existing issues/PRs) and generate a fake commit history (this should be entirely possible with git), a bunch of releases could be quickly generated too. Though you would probably be able to notice pretty quickly that timestamps don’t match since I don’t think github features like issues can have fake timestamps (unlike git)

    though I don’t think this has ever actually been done, there are services that claim to sell not only stars but issues, pull requests and forks too. Though assuming the service is not just a scam in itself, any cursory look at the contents of the issues etc would probably give away that they are AI generated


  • looks like work on the android client started in 2011 (or at least, that’s when it seemingly started using version control)

    the app was released in 2014

    so it has likely inherited decisions from ~14 years ago, I’d guess there is a several year gap where having a native desktop app was not even a concern

    Also the smartphone landscape was totally different back then, QT’s android support back then was in alpha (or totally nonexistent if the signal project is a bit older than the github repository makes it seem), and the average smartphone had extremely weak processing power and a tiny screen resolution by today’s standards. Making the same gui function on both desktop and mobile was probably a pretty ridiculous proposition.












  • found a few examples of how to do it on a github issue:

    var script = GDScript.new()
    script.source_code = "func say_hello():\n\tprint(\"Hello!\")"
    script.reload()
    var script_instance = script.new()
    script_instance.call("say_hello")
    
    
    var MyClass = load("myclass.gd")
    var instance = MyClass.new()
    assert(instance.get_script() == MyClass)