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/)VI
Posts
0
Comments
533
Joined
2 yr. ago

  • I identify as a cis male but essentially feel the same way. The social trappings of my gender are just that. It has about as much to do with my actual identity as my hair colour does. "Factory default" because I don't care enough to bother.

  • A feminine body, I am happy with, but not female.

    ...they literally said "feminine" and "masculine", not "male" or "female". Specifically using language you say you're okay with, but still prompting this response. What exactly is your problem with what they said?

  • how do we balance that hate speech should have the same footing as voicing concerns around oppression?

    Nowhere in the 1st amendment does it require that all speech have the same footing. It just means that it cannot be illegal at the federal level to say what you want. It carries no stipulations that platforms need to tolerate it being present, or that anyone has to listen to it, or that you can't kick someone out of your home or business for it.

  • There are a few options there.

    As someone else mentioned if you're using IPv6 then it doesn't matter, you're already routing internally even if you're using the public DNS name, no extra work required.

    All the rest are for IPv4.

    If you're not behind CGNAT some routers/gateways are also smart enough with their routing to recognise when they need to route back to their own external IP and will loop back locally instead of making any hops out to the internet. Again, if this is the case for you then no additional work is required other than perhaps running a traceroute to confirm.

    Another option is to add a local DNS entry for the name you're using to resolve to a local IP address instead of your public address. The complexity (or even possibility) of this is going to vary considerably with your setup. If you're running your own local DNS e.g. pihole or similar then it's trivial. This is how mine is set up.

    If all your clients are going to be on PCs (or devices you have more than the typical manufacturer allowed modicum of control over) then you can do something kind of like the previous, just with all your local hosts files.

    If none of the above are options, then you'll unfortunately have to fall back on using a local name/address, which means a slightly different client setup for devices you use exclusively in your home versus ones you might use elsewhere.

  • Traffic for a local Jellyfin server should definitely not be going over the internet. Also any reasonably modern client should be able to direct play most media without transcoding.

    As for my own Jellyfin setup, one TV has an Nvidia shield plugged in and is using the standard Android TV client. The other is a Samsung smart TV onto which I have side-loaded the Jellyfin Tizen app.

  • In the moment at the table, arguably RoC, but that's still not necessarily going to convey well to anyone who wasn't there.

    Also, assuming OP's previous submission is the "player shenanigans" which prompted this then it's my opinion that it wasn't cool at the table, either.

  • A pretty large proportion of "player shenanigans" stories amount to "we ignored the rules and allowed something ridiculous to happen". This is fine if that's what your group wants to do, but can't really be expected to be relatable to the community at large.

    It's similar to the stories about level 5 groups who miraculously defeat an ancient red dragon or whatever. It invariably only happens because of some utterly absurd homebrew/ruling, or the GM just played the dragon as an idiot.

  • Amd fan

    Jump
  • There is analogous functionality for most of it, though it's generally not quite as good across the board.

    FSR is AMD's answer to DLSS, but the quality isn't quite as good. However the implementation is hardware agnostic so everyone can use it, which is pretty nice. Even Nvidia's users with older GPUs like a 1080 who are locked out of using DLSS can still use FSR in supported games. If you have an AMD card then you also get the option in the driver settings of enabling it globally for every game, whether it has support built in or not.

    Ray tracing is present and works just fine, though their performance is about a generation behind. It's perfectly usable if you keep your expectations in line with that though. Especially in well optimized games like DOOM Eternal or light ray tracing like in Guardians of the Galaxy. Fully path traced lighting like in Cyberpunk 2077 is completely off the table though.

    Obviously AMD has hardware video encoders. People like to point out that the visual quality of then is lower than Nvidia's but I always found them perfectly serviceable. AMD's background recording stuff is also built directly into their driver suite, no need to install anything extra.

    While they do have their own GPU-powered microphone noise removal, a la RTX Voice, AMD does lack the full set of tools found in Nvidia Broadcast, e.g. video background removal and whatnot. There is also no equivalent to RTX HDR.

    Finally, if you've an interest in locally running any LLM or diffusion models they're more of a pain to get working well on AMD as the majority of implementations are CUDA based.

  • 8 Minutes

    Jump
  • Would it? What does "stationary" mean when discussing relative velocities? The mirror being stationary and the person firing the photon moving at a constant velocity is literally an indistinguishable scenario from a stationary person firing the photon at a moving mirror.

    If I am moving relative to a mirror when I fire the photon, then the mirror is moving relative to me, and will be in a different relative position by the time the "event" of my firing that photon reaches it.

    Also, the photon isn't moving infinitely fast in my (the firer's) reference frame. It's moving infinitely fast in it's own reference frame.

  • 8 Minutes

    Jump
  • The observable effect is the same either way. If light is infinitely fast and causality propagates at c then it's still going to take (distance to the mirror / c) for the fact that you turned on the light to reach the mirror, and that same amount of time for the fact that the light reflected to propagate back to you.

  • 8 Minutes

    Jump
  • Kind of. The concept of simultaneity breaks down at distances where the speed of light matters. If we base it on what we currently observe and call "now" on the Sun the eight minute old state we currently observe then what does "now" on earth look like from the point of view of the Sun at that same moment? You can't reconcile a single "now" for observers in both locations.

    An alternative take which is also consistent with observable physics is that the speed of light is infinite but it's causality itself that propagates at c.

    Thinking in those terms also makes a number of relativistic effects more intuitive. You need infinite energy to reach the speed of light simply because it's infinitely fast. Time dilates when moving because you're encountering approaching causality earlier than you otherwise would have. Time "stops" for anything traveling at the speed of light because at infinite speed it just experiences literally everything in its line of travel at once and the concept of "after" becomes meaningless, encountering all future oncoming causality in a single instant.

    This was a bit of a tangent but it's something that has fascinated me for a long time.

  • I'm all for more people switching to linux, but a lot of your windows issues sound less like windows issues and more like your specific installation is messed up somehow issues.

    One thing I will mention though is that Windows does have native per-application volume control, you don't need to install EarTrumpet. You can right-click the system tray volume icon and open the mixer, or just search for "volume mixer" in the start menu.