Find me at:

@Da_Boom@linuxrocks.online

https://daboom.neocities.org/ (all links and other socials I cannot remember and don’t use)

https://twitch.tv/da_boom232 (I stream here)

https://twitter.com/DaBoom_ (“go live” notifications only)

  • 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Yes it was, but in some ways Nintendo still succeeded In what I believe is their goal - to scatter the developers.

    By shutting down Yuzu, they fragmented everyone into forking their own copies and competing to become the next Yuzu.

    What’s more of a threat to them? One emulator with thousands of contributors, or 1000 emulators with 2-5 contributors each?

    The best thing about open source is the pooling of developers and resources. While forking is neither a good nor a bad thing, it does tend to break up the developer pool.

    It could take anywhere from months to years if at all for everyone to finally settle on a single fork and get back to the level of developer pool that originally existed - then if that happens, Nintendo can come along and do it all over again, at least untill they don’t see the value in continuing.




  • It may have also been the fact that they linked to instruction on how to rip prod.keys and system firmwares. Also their instructions on enabling running copyrighted ROMs - despite the fact that Ripping game ROMs and firmware is not (unfortunately arguably, due to licencing models and jurisdiction - you will own nothing and like it.) illegal so long as it’s for personal use.

    They should’ve advertised it primarily as a testing and homebrew platform, and made sure not to make too much mention of the fact it can be used to play backups. Then they can at least play the ignorance card with more confidence.

    Even then though, multi-billion yen company Nintendo probably would still pull this shit and drag, drag, drag the lawsuit out for forever and a day- draining lawyers fees of money. That being the case, settling is unfortunately the only option.















  • Mid roll ads are fine if the video was made with midrolls in mind that the midrolls actually happened at the times the maker of the video has set them up to happen.

    Sure they are selective about which videos have ads, but not when the ads come on.

    YouTube, with no adblocker or premium subscription has basically become an interrupting cow, making noise at the most innapropriate time and then you have to wat-MOOOOOOOOOO-ch the ad, then you rewind 10 seconds to get your cont-MOOOOOOOOOO-text back. There needs to be a legal limit to the number of midrolls you can stuff in a short space of time.

    I'd rather watch a series of multiple consecutive midroll ads placed at a prespecified time than a random number of ads scattered at completely random intervals, Ruining the flow and mood of the video.

    Its frustrating af.



  • If you are willing to switch to Pipewire, try EasyEffects, it might work better as it’s based off of pulse effects, but for Pipewire, it’s actually developed by the original Devs of pulse effects - in fact the original pulse effects repo is now the easy effects repo, the old pulse effects hasn’t actually been updated for an entire year now, so you might notice it working less and less well.

    To me, Pipewire is the best option for audio on Linux at the moment, it combines the power and low latency of JACK with the ease of use, and multiple device capability of PulseAudio, it really is a great project and is pretty much rock solid at this point in time. It might also fix your issues with pulseeffects/EasyEffects not recognising your microphone.

    Honestly, I still don’t use flatpaks for specific things - namely OBS, as I have a Blackmagic capture card, and the flatpak version of OBS won’t support it due to how the BMD driver is required to be installed. Sure it’s good for a lot of things, but sometimes the other options are better for your purposes. I still use the AUR Tytan652 version.