• 15 Posts
  • 1.22K Comments
Joined 2 years ago
cake
Cake day: August 4th, 2023

help-circle
rss

  • I don’t think there’s anything untoward going on with the OP here. I’m not using a VPN and the metadata is in German for me.

    Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

    I could definitely be misunderstanding something, though. I for sure haven’t watched the whole linked video. What little I’ve seen seems legit as far as I’ve been able to tell so far.


  • A few ideas:

    • If it’s a hard drive, listen to see if you keep getting hard drive noises after the freeze.
    • Try SSH’ing in to that box (or otherwise try making a network connection to it.) Just to make sure the system is actually freezing and it’s not just the graphics screwing up and not updating the display while continuing to boot.
    • Delete/uninstall your AMD firmware. Or if you don’t have it installed, install it.
    • If you’re currently booting in EFI mode, try BIOS mode. Or vice versa.
    • Try booting with an incorrect “root” kernel parameter. My thought is maybe if it’s loading a module that’s causing issues, if it can’t get the root FS, it can’t load modules. If it doesn’t have the same issue, that will tell you something. (And if it does, that’ll tell you something too.)
    • Try other distros’s live ISOs to see if you you can isolate anything that makes a difference.








  • Not OP, but I’ve done this to my Switch.

    • Only works if you have a first-run Switch that is susceptible to Fusee-Gelee. Or if there’s a modchip involved, but a) adding a modchip is really fiddly and b) I don’t know how much of the following applies if you have a modchip.
    • There are ways that don’t require modifying a Joycon. There are “jigs” that you can buy or even 3d print if you’ve got access to a printer. Those slide down into the Joycon rail to connect a couple of pins necessary to do the whole homebrew thing. There are also paperclip and tinfoil methods that… aren’t 100% safe.
    • No, the Joycons don’t need to be jailbroken or anything. The modification OP is referring to, if you go that direction, is strictly a hardware mod to connect (electrically) a couple of pins inside the Joycon that connect to pins on the Switch (at the bottom of the “rail”).
    • I’m not sure what’s running on what OP has in the photo there but it looks like either Linux or Android. Either way, it probably isn’t an x86_64 emulator. But one thing you can do with homebrew is to run a (slightly-tweaked) “copy” of the factory-installed Switch OS from the SD card. If you’re doing that, then everything retains full functionality. The dock works fine and the Joycons work exactly the same with one minor caveat: when switching between the main/system and “copy”/“EmuEMMC” OS’s, you’ll need to re-pair.
    • No idea whether x86_64 emulation is an option and if so what kind of performance you could expect.
    • Performance and experience for Switch games is perfect!
    • One risk is bricking (obviously) which is a pretty negligible if you back everything up the way the guides tell you to ahead of time. (In fact, it’s very arguable that homebrewing your Switch actually makes your Switch more resistant to bricking because you have more options with regard to fixing it yourself.)
    • Another risk is getting banned from the e-shop and all online interaction. Basically if Nintendo detects you’re running homebrew (for instance, if your Switch is online and communicating with Nintendo and reports to Nintendo that you have something installed that isn’t officially-lisenced Nintendo software/games) they’ll ban you from all online things. The Switch itself will still work fine for all offline interactions and any games on the device will continue to work as will physical game cartridges. But, as long as you only make modifications to the “copy”/“EmuEMMC” and set up some of the DNS blocking options that prevent your Switch from communicating with Nintendo’s servers (or just never connect to the internet from the EmuEMMC OS), you should be golden.
    • Also, if you have a first-run Switch (that doesn’t require a modchip) there’s very little chance of voiding your warranty. If you need to send your Switch in for service, as long as you don’t send them a modded Joycon, jig, or SD card loaded with homebrew stuff, and as long as you don’t make any mods to the main OS, there’s no way for them to detect that you’ve modded it. The only downside is that if you send in a first-run Switch for service, it’s almost guaranteed they’ll replace the motherboard with one that isn’t hackable without a modchip.
    • Oh, I guess one more risk I should mention. It’s possible your EmuEMMC will get corrupted randomly (at least that happened to me) and you won’t be able to boot into it again without setting it back up from scratch (from a (new or old) backup of the system OS). That will lose you any saved game data on your EmuEMMC. Though that can be mitigated by backing up your save games to the SD card on a regular basis. (I’ve learned my lesson.) That isn’t so much a risk for any games you play on the system OS (which you can boot into at any time trivially.)
    • I don’t have any experience with the Steam Deck, so couldn’t speak to that. I love being able to mod Switch games, back up my saves, install emulators, etc on my Switch.

    If you want to get homebrew on your Switch set up, you can start here. But of course, it only works for the earliest-released Switch runs. And you’ll need a computer or something to send a “payload” to your Switch to get booted into a homebrew environment.

    Good luck!


  • Respect.

    I haven’t quit or tried to, but:

    • I do things while I’ve got YouTube on in the background more than I dedicate my attention to it. Writing code, playing a video game, etc.
    • I almost never log in to YouTube. And I clear my cookies at least daily. So I don’t succumb to “the algorithm” very much. I do use NewPipe on my phone for music and such, but again, no algorithm involved. But generally I go specifically to what I want to watch or search specifically for what I want to watch and watch it. I also turn autoplay off.
    • I have published videos on YouTube, but I’m resolved not to any more. Any more videos I might make in the future, I’ll put on PeerTube.

    I have a short list of creators I follow (but without using things like the bell/subscription feature on YouTube). Short enough that I can keep the list in my head. One of those creators I also support on Patreon.

    I guess all that to say, I do hedge my use of YouTube, but quitting isn’t on my radar any time soon.



  • I wonder if there’s a way to prevent people from even knowing that two different votes came from the same user.

    What I outlined above should prevent anyone from knowing two different votes came from the same user… without specifically trying that user’s id on each. That’s what the salt (the comment/post id) is for.



  • Votes should be anonymous.

    I tend to agree, but the fact is that they aren’t anonymous. This tool just exposes the already-existing fact that Lemmy expressly does not guarantee anonymity for votes. The solution isn’t to not for the poster to not publish this tool. Believe me, such tools already exist in private even if none other than this one are published. Publishing this one only democratizes access to that information. (And not entirely, I don’t think. From what I’m seeing on the page, it looks like it still requires an admin account on an instance. Update: Actually, I’m not sure if it requires an admin account or not. Either way, though.) The solution is (if it’s possible) to make Lemmy itself protect voters’ anonymity.

    The reason why instances know who has up/down voted things (rather than only keeping an anonymized “total” for each post/comment) is so it can prevent double-voting.

    Maybe instead of usernames, the instances could store/trade… salted hashes of the usernames where the salt is the title or unique identifier of the post/comment being voted on? It wouldn’t be perfect, but it would allow the instance to figure out whether the currently-viewing or currently-voting user has already voted while also making it harder for anyone else to get that information. About the only way a tool could tell you exhaustively who had voted if that were how things worked that I can think of off hand is to try every username on Lemmy one-by-one until all the votes were accounted for.

    (Of course, malicious instances could still keep track of usernames or unique user ids who up/downvoted, but only on the instance on which the vote was cast. Also, one downside of this approach would be increased CPU usage. How much? Not sure. It might be trivial. Or maybe not. Dunno.)

    And there may be much better ways to do this. I haven’t really thought about it much. I also haven’t checked whether there is an open ticket asking for improved anonymity for votes already.

    (Also, full disclosure, all of the above was written after only an extremely brief skim of the linked page.)

    (One more edit. Something IHawkMike said led me to realize that the scheme I described above would allow instances to manipulate votes by just inventing hashes. Like, grabbing 512 bits of data from /dev/urandom and giving it to other instances as if it was a hash of a username or user id when, in fact, it’s not a hash of anything. Other instances wouldn’t be able to easily tell that it wasn’t the hash of a valid user id. I haven’t thought how to go about solving that yet. Maybe if it occurs to me, I’ll update this post.)


  • Yeah, what I’ve heard about it has made it sound like the judge is probably broadly sympathetic to the SFC’s arguments, which of course is a good thing. It’s been a bit since I’ve really looked deeply into it, but at least what I’ve heard sounds hopeful.

    I’m probably getting my hopes up too high, but it’d be so great if that case went the SFC’s way. (And stayed that way on appeals or whatever.)

    IANAL, but the fact that what they’re suing for isn’t money but rather for the courts to force Visio to comply with the GPL, that probably means that a settlement is unlikely, and a judgement is going to have much more profound effects on the industry than a settlement would.

    Anyway. That whole case fascinates me. We’ll see how things go. 🤞