• 1 Post
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • It’s interesting how this scene was constructed. The blacksmiths and their table never appear outside except when guiding the one lost blacksmith back home. The old man is usually sleeping in the bar mumbling about his lost son (flute boy) until the pre-credits end sequence where they are reunited in the forest. The text boxes normally have a transparent background, but here it’s a darkened floor tile from Sahasrahla’s hut.


  • The most convenient userscript for me is this one that automatically likes YouTube videos. It’s configurable to be able to: like the video after a specified watch percentage, ignore already disliked videos, only like videos from subscribed channels, and ignore livestreams. I like it enough that I’ve made a few pull requests to fix it when YouTube changes their UI.

    When I have the time, I work on an in-progress local version to implement a few new features including: (1) Support for the YouTube shorts UI. (2) An option for a notification/toast to appear when the video has been liked. (3) An option to check the watch percentage continuously (mutation observer) instead of a user-defined poll rate which sometimes misses liking very short videos in playlists. Eventually I’d like to port something like this as a YouTube ReVanced patch.












  • I thought decompiling with Ghidra was okay too, I may have just misunderstood the wiki article when I double checked post-commenting and crossed out my comment. I’m not entirely sure what comprises “proprietary techniques”. But I’m pretty sure that documentation needs to be provided in order to keep it on the legal side. Hopefully this project can come back and recieve continued support ala similar decomp projects.


  • I think the binary they distributed still included the art and sound assets; the users didn’t have to provide their own. And “clean-room” design is more than just providing source code. You need to provide a “paper trial” / commit history and documentation of how the final code was derived from the original code. My mistake, clean room is when you recreate the project without reading the original/compiled code at all. Specifications are written based on observed behaviors of the original user-facing program and new code is written according to that.


  • Maybe I’m wrong, but wasn’t there a way to release this while avoiding the issue of copyright? My understanding is that publishing “clean-room” reverse engineered code is legal. The graphics and sound can’t be redistributed, but you can distribute a tool to rip those assests from a ROM and let the users provide a ROM they own. This is what Ship of Harkinian does no?



  • BleakBluets@lemmy.worldtoAsklemmy@lemmy.mlWhats your such opinion
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    9 months ago

    I was stubborn about this for so long, and I’m still not entirely sure I understand it, but here is a perspective that made me doubt my belief.

    Imagine the Monty Hall Problem, but with 100 doors and only one grand prize. You pick one; it obviously has a 1/100 chance of being a grand prize. Then Monty reveals 98 doors without grand prizes in them such that the only doors left are the one you chose and one that Monty left unopened. Monty obviously arranged for one of those two doors to have the grand prize behind it. The “choice to switch” is really just a second round of the game, but with a 1/2 chance of winning (wrong, your odds change only if you “participate” in round two).

    If you stick with your door, you are relying on your initial 1/100 chance of winning. If you switch, you are getting the 1/2 odds of the “second round”.

    Apparently with three doors, switching gives you a 2/3 chance of winning, but I don’t understand the math of how to get that answer and I wouldn’t be able to calculate the odds of the 100 door version. I just know intuitivey that switching is better.