• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2024

help-circle


  • Just wanted to add a couple of things: the game is Street Fighter 3rd Strike, where you can die due to chip damage. What this means is that even if you block special moves (like Justin’s Chun-li did) they still do damage, the aforementioned chip damage.

    So Daigo Umehara, the Ken player, had no option other than parry or he would lose the game and Justin Wong, the Chun-li player, would advance to grand finals. Parrying in 3rd Strike is done by inputting forward as opposed to blocking which is done by inputting back. More specifically you have to press forward in a 10 frame window. Since 60 frames equal a second, you have a window of 1/6th of a second to input it and you also cannot hold forward, otherwise you won’t be able to use parry for the next 23 frames.

    So if Daigo had held forward to parry the remaining hits of Chun-li’s attack, he’d die from chip damage (I think). What he did instead was manually parrying every single hit of the attack AND he also parried the attack in the air, which is even harder to do because in the air the frame window is halved (so you have a 5 frame window, or 0,5/6th of a second if my math doesn’t fail me), which doubles the difficulty.

    And just to add to this: Daigo had actually done it in a match before but it wasn’t recorded. Also, the number 37 was chosen at random to make it seem as if there were a lot more hype moments like this. Also also Justin Wong, aside from being one of the best fighting game players of all time, has always been (as far as I know) a cool sport about this, even encouraging people online to do the Daigo parry whenever he plays 3rd Strike just so players (the ones who know how to do it at least) can sort of be a Daigo for a moment.

    If you want to know more, I suggest this video: https://yewtu.be/watch?v=36m-teYaQmE

    P.S.: Daigo would go on to lose in the grand finals. But nobody cares about that, to be honest. I don’t even know who won it.



  • No phone apps that I know of for Koha. I think it works fine on any mobile browser, though. If you know HTML, CSS, or even JavaScript you can do a ton of cool stuff on your library’s catalogue. As for FOLIO, no idea, but I don’t think any exist.

    There is VideLibri but it doesn’t add any functionality you don’t already have when accessing the online catalogue of any library on your browser, so I don’t think it’s worth it. Something like the Web Opac App, which let’s you browse a ton of libraries’ catalogues in one app would be a more interesting solution. Unfortunately, it’s stopped being maintained a while ago and went closed-source, from what I can gather.


  • Hi! In the library I work, we use Koha, which is probably the most well-known open-source library management system. This comes with the advantage of having a big community and having a lot of answers to questions you’ll probably have, albeit the documentation is kind of all over the place. Just a heads-up, though: it only runs on Linux so, whoever is going to do the implementation must familiarize themselves with it if they haven’t done so already. It’s not a flawless system by any means but as far as open-source goes, it’s the best and most mature.

    There are a few demo servers you can try on their website: https://koha-community.org/demo/

    The other open-source library management system I know of is FOLIO (their repo) but I haven’t tried it or read much about it. I only know it’s way younger than Koha (created 10 years ago, I think) and that EBSCO is one of its vendors. It may use newer technology but I honestly don’t know. You can also try a demo server if you go to their wiki.

    Hope it helped. If you have any questions, let me know :).