• 0 Posts
  • 206 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • Yeah, N64 speedrunners even went as far as replacing their aging analog sticks with machined steel sticks. Because as the console ages, so do the controllers. And stick drift became a major problem for speed runners who used genuine consoles. There was even a case where an aging controller led to the discovery of a new glitch, when a speedrunner’s NES controller had gotten so old that it allowed him to press button combos that wouldn’t have been possible with a new controller. And that button combo allowed him to perform glitches that would have been otherwise impossible on a console.

    The larger issue is accessibility. If speed running requires a genuine console, it severely limits the number of people who can afford to participate. There would be a big financial barrier just to buy the console and game(s), and since no new consoles are being made it will inevitably lead to the death of speedruns as consoles die out and nobody can continue playing.

    One of the original goals of emulation was data preservation, since it quickly became evident that game companies wouldn’t bother preserving their own games. And as consoles age, that will only become more and more important. I personally have backups of all of my legitimately purchased Nintendo games. But that’s only because I enjoy data hoarding and have a NAS that can actually store all of it. Not everyone has that luxury, and it means that (again) there will be a big financial barrier to anyone wanting to be able to play the games that they legally purchased and have the right to play.


  • They’re probably talking about the BMG rootkit from the early 2000’s. Basically, when you inserted a Sony CD into your computer, it would automatically and silently install a rootkit on your PC, which introduced a backdoor on your PC that was being actively exploited. It was also notoriously difficult to remove, as it would reinstall itself even if you deleted every visible trace of it (and improperly installing it could disable access to your CD drive entirely.)

    Then when shit hit the fan and Sony was making headlines for it, they released a “fix” for it. The fix didn’t actually remove the rootkit, and simply hid files with specific names (the rootkit files) from the users. This only introduced another vulnerability, where hackers could just name any virus the same as the rootkit, and it would automatically be hidden.

    It led to several very large lawsuits and state investigations. Sony was raked over the coals by multiple state attorneys general, and the FTC even published warnings urging consumers not to buy Sony CDs.

    All in the name of DRM. The rootkit was initially meant to stop you from ripping and copying the CD. Oh, and the rootkit contained sections of improperly credited open source code. So Sony stole from OSS programmers while claiming that they were trying to prevent IP theft.



  • You don’t need to run it on a pi. In fact, I’d actually argue against it; A pi will be underpowered if you’re ever needing to transcode anything. Transcoding is what Plex/Jellyfin does if your watching device can’t natively play the video. Maybe you have a 4k video, but you’re playing it on a 1080p screen. That video will need to be transcoded from 4k into 1080p for the screen to be able to display it. Or maybe the file is encoded using ACC (a fairly recent encoding method) which isn’t widely supported by older devices. This often happens with things like smart TVs (which often don’t support modern encoding and need to be transcoded even if the resolution is correct.)

    Basically, if you’re 100% positive that every device you’re watching it on will never need transcoding, then a pi is acceptable. But for anything else, I’d recommend a small PC instead. You can even use an old PC if you have one laying around.

    Or if you want to use a new machine, maybe something like an HP Elitedesk. They’re basically what you see in every single cubicle in every single office building. They’re extremely popular in corporate settings, which means there are a ton of used/refurbished systems available for cheap, because IT destroys the drives and sends the rest to refurb when they upgrade their fleet of PCs. So for the refurb you’re basically just paying the cost of an SSD they added in (to replace the one IT pulled out), plus whatever labor is associated with dusting it out and checking the connections to make sure they all work. You can pick up a modern one for like $250 on Amazon (or your preferred electronics store).

    Worth noting that the elitedesk generations are marked by a G-number, so google the model (like an EliteDesk G9, G7, etc) to see what kind of processor it has; Avoid anything with an intel 13th or 14th generation CPU, (they have major reliability issues) and check with Plex/Jellyfin’s CPU requirements list to see if it supports hardware accelerated transcoding. For Intel chips, look for QuickSync support.

    For storage, I’d recommend running a NAS with however many hard drives you can afford, and one that has extra ports for future expandability. Some NAS systems support Plex and/or Jellyfin directly, but the requirements for full support are tricky and you’ll almost always have better luck just running a dedicated PC for Plex. Then for playing, one of two things will happen. Either the device is capable of directly playing the file, or it will need to be transcoded. If it’s directly playing, the plex server basically just points the player to the NAS, and the player handles the rest. If it’s transcoding, the PC will access the NAS, then stream it to the player.

    As for deciding on Plex vs Jellyfin, that’s really a matter of personal preference. If you’re using Plex, I’d highly suggest a PlexPass sub/lifetime purchase; Wait until Black Friday, because they historically do a (~25% off) discount on their lifetime pass. Plex is definitely easier to set up, especially if you plan on streaming outside of your LAN.

    Jellyfin currently struggles from a lack of native app support; Lots of smart TVs don’t have a native Jellyfin app, for instance. But some people have issues and complaints (many of them justified!) with Plex, so if the FOSS sounds appealing, then consider Jellyfin instead. Jellyfin is also rapidly being developed, and many people expect it to have feature parity with Plex within a few years.

    And if you’re having trouble deciding, you can actually set up both (they can run in tandem on the same machine) and then see which one you prefer.

    And the nice part about using a mini PC is that you can also use it for more than just Plex/Jellyfin. I have the *arr suite running on mine, alongside a Factorio server, a Palworld server, and a few other things.



  • That’s more on the OS than the text protocol. The protocol doesn’t just hold a text in the ether until it’s time for delivery. A scheduled text is you telling the phone “hey, wait to send this message until it’s time.” Then your phone sends it at the proper time.

    iOS still doesn’t have built in text scheduling. There are workarounds, (like using the Shortcuts app to build a “send this text” automation that runs at a specific time), but that’s not the same thing as native support.


  • It’s more about the lack of iMessage features. Things like editing, unsend, text effects, etc are absent in regular texts. If everyone is on iMessage, everyone can use those enhanced features. They’re apparently pretty popular in group chats, but even a single android user will drag the entire conversation into regular text messages instead. So lots of iPhone users (especially the younger gen Z and alpha) started complaining whenever someone had an android, or even outright bullying them for it.

    And for android users, texting with an iPhone user is a horrible experience; Images are horribly compressed, videos are severely limited in file size and compressed, group texts need to be opened as an attachment to be read, etc… All because iOS refused to use the more modern RCS texting protocols.


  • There is also the hilariously misguided belief that good coders do not produce bugs so there’s no need for debugging.

    Yeah, fuck this specifically. I’d rather have a good troubleshooter. I work in live events; I don’t care if an audio technician can run a concert and have it sounding wonderful under ideal conditions. I care if they can salvage a concert after the entire fucking rig stops working 5 minutes before the show starts. I judge techs almost solely on their ability to troubleshoot.

    Anyone can run a system that is already built, but a truly good technician can identify where a problem is and work to fix it. I’ve seen too many “good” technicians freeze up and panic at the first sign of trouble, which really just tells me they’re not as good as they say. When you have a show starting in 10 minutes and you have no audio, you can’t waste time with panic.



  • Now we just need a way to use that shelf with the same account so I don’t get booted from my steam deck games just because I left something running on my PC and vice versa.

    AFAIK, this is also a licensing issue. When Steam was launching, game publishers were concerned that people would simply share an account. So part of Steam’s licensing agreement is that the same account can’t have games (even different games) running on two machines at the same time. It’s specifically to prevent account sharing, because people would just share an account with their friends; Booting them out of their game every time their buddy boots something up is a pretty effective countermeasure.


  • The “same game at the same time” part is a licensing issue. It won’t ever be “solved” because it would get Steam into legal trouble to do so, just like the Internet Archive recently FAFO’ed. In order for two people to play the same game at the same time, you need to own two licenses for said game.

    But it does solve the issue of multiple people using the same library at the same time. Now your family members don’t get booted off of Skyrim just because you launched Persona. It basically combines your libraries, so any of you can choose any of the listed games to play at any time. Just like having a physical shelf full of CD cases.


  • It’s the latter. And even worse, they couldn’t claim ignorance or accident, because they were previously using the former system. They had a system set up which only allowed a certain number of licenses to be in use at any one time. When someone checked out an ebook, it was unavailable to anyone else. This is standard practice for libraries.

    Then IA intentionally went out of their way to disable this licensing system, and allowed unlimited downloads. It was the worst of both worlds, because it meant they were violating copyright and they took active steps to remove those copyright protections. They couldn’t go “sorry we didn’t know” and get off with some finger waggling and a “don’t do it again”, because they had gone out of their way to intentionally disable the licensing system. They knew exactly what they were doing. Instead, the courts threw the book at IA, because it was an open-and-shut case of blatant and intentional copyright violation.



  • At least on iOS, it takes it a step farther and tells you specifically when an app is accessing your location, microphone, camera, etc… It even delineates when it’s in the foreground or background. For instance, if I check my weather app, I get this symbol in the upper corner:

    The circled arrow means it is actively accessing my location. And if I close the app, it gives me this instead:

    The uncircled arrow means my location was accessed in the foreground recently. And if it happens entirely in the background, (like maybe Google has accessed my location to check travel time for an upcoming calendar event,) then the arrow will be an outline instead of being filled in.

    The same basic rules apply for camera and mic access. If it accesses my mic, I get an orange dot. If it accesses my camera, I get a green dot.



  • That’s because they’ve been pushing the iPad as a sort of Mac Lite, but they can’t do that unless you can plug peripherals or a thumb drive into it. You can 100% plug a USB-C laptop dock into an iPad, and it’ll work. You can even use a mouse with it if you really want to.

    But they wanted to keep Lightning around as long as possible, because they made a commission on every single lighting cable that was sold; Companies had to license the rights to use the connector, and had to pay Apple for every one they used. That’s why Lightning cables were always a few bucks more expensive than a comparable USB-C cable. That extra few bucks was going straight into Apple’s pocket. It was a huge source of passive income for the company, which they were reluctant to let go of.