Heyyyyyyyyyy

  • 7 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: August 9th, 2023

help-circle
  • I also have a similar side project planned for a revamp. Successfully made a v1 with grease monkey (vanilla JS) + stylish back in maybe 2016. Super dangerous to keep firefox 56 running only for this front-end. Just need to do the v2 then migrate to latest librewolf.

    I want to redo the whole thing in Vue, client side routing with build step. The problem is that

    • site is not open source
    • no API doc (but I already made my own)
    • required log-in (no sensitive info)
    • some route request must be made from that domain due to CORS

    My goal is not to change the UI but wipe the whole page and start over with custom API call instead. V1 do this by visiting a 404 route to stop unnecessary load and use my own URL param for the API call. For bonus cringe I used local storage for database.

    Ended up having to use userscript, and now I’m kinda stuck with how to mash Vite build and tamper/violent monkey together :(
    Do you have any suggestion or resource I can learn more on this?










  • g6d3np81@kbin.socialtoGames@lemmy.worldStop using Fandom
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    1 year ago

    Regarding SEO, What’s stopping maintainers from vandalizing their own fandom page?

    It would not be difficult to make a bot to update fandom page with a convincing but slightly wrong info, after a few hundred iterations, it’s all useless. Go look at what google recommend and do complete opposite. I’m convinced this will bomb ranking and put whatever wiki they migrated to at the top.








  • Already tried that. No significant improvement over running at uncapped with v-sync (60fps).

    baseline:
    uncapped with v-sync (60fps)
    result: running at 40% usage and 40C temp.

    nvidia cp config:
    capping at 20fps with or without v-sync (running in background)
    result: usage jump up and down predictably between 20% and 50%, no temperature difference.

    Clearly worse than capping it at game engine level since ES2 shows linear and stable drop in GPU usage. I assume this varies greatly on different game engine.