Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GE
Posts
1
Comments
1,003
Joined
2 yr. ago

  • YES.

    And not just the cloud, but internet connectivity and automatic updates on local machines, too. There are basically a hundred "arbitrary code execution" mechanisms built into every production machine.

    If it doesn't truly need to be online, it probably shouldn't be. Figure out another way to install security patches. If it's offline, you won't need to worry about them half as much anyway.

  • If you can accept the possibility of making contact, you should be able to accept the possibility of a hit. The difference between a hit and a foul is, like, centimeters or milliseconds. Why do you think a difference of that size is literally impossible?

    We're taking about a chance, so it's fair to ignore the worst-case scenario and consider the best-case scenario. Forget about 100mph heat; that's the exception even in pro play. And we're not going for consistency, so you can forget about reaction time. Feel free to start swinging way earlier than a real pro would. Close your eyes and pray to your deity of choice. There's a chance.

    A pitcher does not respond to small-scale movements of the hitter once the wind-up begins, so this is not a 100% head-to-head skill issue. There is plenty of time for a reasonably-athletic layman to get the bat through the strike zone in a time frame that overlaps with the range of probability of a pitch. Not with any consistency, because that would require precise reaction and control that are not possible without a ton of experience. But again, we're not talking about consistency. We're talking about a single stroke of luck. A single hit is within the realm of luck. Skill simply tightens up that probability distribution in your favor.

    As for football, yeah, I concede your point. The the kind of play I'm describing happens every season, but you're absolutely right that a layman wouldn't actually be able to get in position to make that catch in the first place. My scenario was assuming a miracle position for a good runner to take off, which puts it outside the range of a single stroke of luck. My bad.

  • That’s because golf and pool aren’t head-to-head sports (per se); the other golfer(s) or pool player can’t interfere with your ball as you hit it.

    Excellent point! That's also basically the scenario I mentioned with football and baseball. In football, you'd need to have a clear shot and be a good runner (like in Forrest Gump). Unlikely, but within the realm of possibility for an athletic non-football-player. In baseball, once the ball is in the air it's anyone's game. Anyone who can swing a bat has a chance to get a lucky hit. Not a good chance, but a chance. Especially a professional athlete from a different sport. I mean, we kind of saw that when Michael Jordan played baseball. He had a very respectable batting average...for a basketball player. :)

    If you put me in the majors, I'd bet I could manage a .001 batting average!

  • “Some people who don’t play table tennis actually think they have a chance to win a single point,” said Anders Lind, 25, of Denmark, the No. 62-ranked player in the world. “It’s cute. But it’s not true.”

    The idea isn't crazy, depending on what sport you have as a frame of reference.

    I mean, I'd have a chance to win a single hole against a pro golfer with a lucky shot. I'd have a chance to score a single hit against a major-league pitcher. I'd have a decent chance to at least sink a single ball against a professional pool player. I'd surely capture a few pieces in a game of chess against Magnus Carlsen (though not any he didn't intend to lose, so bad example). I might even be able to Forrest-Gump my way to a touchdown against a pro football team if someone sent me a perfect pass.

    Of course I'd have no chance to win an entire game in any of those cases, but in many sports, a competent amateur has a chance to at least get a point against a pro.

    That said, I've seen pro table tennis and I know for sure I'm not getting a point unless they are struck by well-timed lightning. We are not playing the same game. It'd be like going to a motorcycle rally with my bicycle.

  • Permanently Deleted

    Jump
  • a novel technique they call "oracle trilateration."

    Novel? This is basic geometry. If you can get the distance of a user from multiple locations, then it's trivial to get their exact location.

  • Both.

    The good: CUDA is required for maximum performance and compatibility with machine learning (ML) frameworks and applications. It is a legitimate reason to choose Nvidia, and if you have an Nvidia card you will want to make sure you have CUDA acceleration working for any compatible ML workloads.

    The bad: Getting CUDA to actually install and run correctly is a giant pain in the ass for anything but the absolute most basic use case. You will likely need to maintain multiple framework versions, because new ones are not backwards-compatible. You'll need to source custom versions of Python modules compiled against specific versions of CUDA, which opens a whole new circle of Dependency Hell. And you know how everyone and their dog publishes shit with Docker now? Yeah, have fun with that.

    That said, AMD's equivalent (ROCm) is just as bad, and AMD is lagging about a full generation behind Nvidia in terms of ML performance.

    The easy way is to just use OpenCL. But that's not going to give you the best performance, and it's not going to be compatible with everything out there.

  • Mozilla says they use a third-party OHTTP intermediary. In the blog post linked above, they name Fastly as their partner. So it's not as bad as Mozilla + Mozilla-wearing-funny-glasses.

    Personally, I still think this is the wrong approach to privacy, even though I've used Fakespot on my own many times over the years. Largely because I don't think any of this needs to be built into a web browser.

    I would prefer my web browser to minimize information leakage by default, to the greatest degree that it can while still remaining useful as a web browser. Mozilla keeps adding bloat to Firefox, and bloat always comes at a cost. I'd much prefer these to be browser extensions that people can download if they want them, rather than built in by default. The baseline Firefox should be lean. Less "stuff" = smaller attack surface. Simplicity is best.

    I mean, the Fakespot browser extension has existed for a long time, and I've never seriously considered installing it. I'd much rather just take an extra three seconds to load their web site and paste in a URL than have it constantly monitoring my activity and doing god-knows-what with it. That way I have better knowledge and control of what is happening with my data. Even if I trust their intentions, I don't implicitly trust their competence (all software has bugs) and I don't trust that they will never go rogue in the future.

    And also, I just don't find this claim all that compelling in principle:

    By processing the data jointly across two independent parties, they ensure neither party holds the information required to reveal sensitive information about someone.

    I mean...sure. That's fair. Buuuuuut handing half the data to your "partner" doesn't give me a whole lot of confidence. Especially since literally nobody reads all of the privacy policies they are subject to. See:

    https://www.theatlantic.com/technology/archive/2012/03/reading-the-privacy-policies-you-encounter-in-a-year-would-take-76-work-days/253851/

    https://www.npr.org/sections/alltechconsidered/2012/04/19/150905465/to-read-all-those-web-privacy-policies-just-take-a-month-off-work

    https://www.techradar.com/computing/cyber-security/you-need-a-whole-workweek-every-month-to-read-privacy-policiesand-thats-bad-news

    Minimizing privacy policies should be a high-priority goal for any organization that claims to value privacy.

    Furthermore, how many additional parties have access (legally or otherwise) to both Mozilla and Fastly? 🤷

  • Backing up / in it's entirety might cause issues since there will be a lot of special files and crossed mount points. You should probably exclude /proc and any system folders from the backup. See: https://github.com/bit-team/backintime/blob/dev/FAQ.md#does-back-in-time-support-full-system-backups

    Since you're planning to start with a clean Nobara install, you can probably exclude those during the restore step. Just be careful not to restore files that are in active use by the running system.

    Have you tested restoring from your backup? Can you do it from the liveUSB?

  • Worth noting that GrapheneOS is not rooted by default. So it does satisfy that requirement.

    But yeah, I don't think you can do this on stock Android without root. Not sure how it works on other non-rooted ROMs like LineageOS.

  • Looking over the Fastfox.js config, it looks like most settings fall into one of three categories:

    1. Subjective appearance of speed or responsiveness (perhaps at the expense of objectively-measurable load times)
    2. Experimental options that don't apply to all hardware or OSes (e.g. GPU acceleration)
    3. Settings that optimize performance at the expense of memory, CPU, or network usage (e.g. cache sizes and connection limits)

    I don't see anything that makes me think Mozilla's defaults are unreasonable. It's not like Mozilla is leaving performance on the table, but rather that they chose a different compromise here and there, and use highly-compatible defaults. That said, it does seem like there is room for individual users to improve on the defaults — particularly if they have fast internet connections and lots of RAM.

    For example:

    // [NOTE] Lowering the interval will increase responsiveness
    // but also increase the total load time.
    user_pref("content.notify.interval", 100000); // (.10s); default=120000 (.12s)

    This seems very much like a judgment call and I guess Firefox's defaults would actually have better objective load times and better benchmark scores. That doesn't mean it's objectively better, but it seems reasonable, at least.

    // PREF: GPU-accelerated Canvas2D
    // Use gpu-canvas instead of to skia-canvas.
    // [WARNING] May cause issues on some Windows machines using integrated GPUs [2] [3]

    // [NOTE] Higher values will use more memory.

    Again, the defaults seem to make sense. Perhaps Mozilla could add an optimization wizard to detect appropriate settings for your hardware, and let the user select options like "maximize speed" vs "maximize memory efficiency". These are not one-size-fits-all settings.

    Fastfox also disables a lot of prefetching options, which...seems counter to the goal of improving speed. Not really sure what to make of that.