• 1 Post
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle





  • Running arr services on a proxmox cluster to download to a device on the same network. I don’t think there would be any problems but wanted to see what changes need to be done.

    I’m essentially doing this with my set up. I have a box running proxmox and a separate networked nas device. There aren’t really any changes, per se, other than pointing the *arr installs at the correct mounts. One thing to make note of, i would make sure that your download, processing, and final locations are all within the same mount point, so that you can take advantage of atomic moves.


  • You’re talking about XMPP, and it was google with google chat that people refer to with it.

    That said, there’s a lot of details that story people throw around about google killing it that lacks some details. Specifically that the premier service that used and developed the standard, jabber, was acquired by cisco like 8 years before google supposedly killed it, which i would argue affected it far harder than google chat did.

    It’s also lacking a lot of modern features that were becoming staple around the time that it was killed; i.e. QoS, assured delivery, read receipts, and a few other things. I still don’t think the protocol supports them.

    Also, the protocol still exists and is used. It’s used by microsoft in skype for business, it’s also the IM protocol for lots of gaming platforms like origin, playstation, the switch (for its push notifications for their online service), League of legends, fortnite, and others. It’s still a reasonably popular standard when it comes to chat programs, though none of them that i’m aware of use the actual federation piece of it to talk to each other.

    While the tactic alluded to does exist (“embrace, extend, extinguish”), i’ve never been necessarily convinced that google “kiled” xmpp, as its been around a long time and continues to be for various reasons. Even with google chat, it was never a ‘front end’ thing many users even thought about, because it’s back end frameworks tech, and it continues to be so in lots of different places today. I’m reasonably sure that the people who get upset about it and proclaim google killed it are basically just upset that it didn’t become the defacto chat standard today, which i would argue almost nothing is the defacto standard anyways, unless you count discord which kinda came out of nowhere like a whirlwind and took over the chat space and has nothing to do with any XMPP drama.

    Ultimately, its up to you (whoever is reading this) to look into the facts of the matter and decide for yourself if that’s what really happened, but keep in mind, the people who usually repeat the anecdote about how google killed it have an agenda to push. I’m personally skeptical, because there’s reasons for google to have dropped it (see mentioned limitations above), and even back then, it wasn’t that outrageously popular. In fact, i would argue its more widely used today than it was back then, but i have no hard numbers on that.


  • I mean, this is still more or less what the fast charging standards do; they’re pouring more power into it faster with higher bandwidth cables and sectioned charging.

    The level 3 fast charger is basically the equivalent of 4 power cords from your wall. Also, adding more and more hardware and things for it will effectively make the electronics more complicated, which means more expensive, difficult to manufacture and repair

    But also, as you scale this up more and more you’ll start running into issues that make it difficult to start pulling more power; energy from the grid isn’t infinite


  • This is already what they do. Dry batteries that are bigger than about your phone are generally comprised a whole lot of battery cells. If you ever take em apart, you’d basically see the cells are made up of what looks like a whole bunch of AA batteries (but larger).

    They do charge “in parallel”, but that’s limited by how much electricity you can feed through into the system as a whole, and doesn’t speed up the process, it just makes them all fill at about the same rate.

    Making the cells swappable is basically what this video is about.




  • I have mediacom as well, but in a larger city of the midwest. They have datacaps here too, and i was paying about $100 for exactly this same plan up until a couple years ago. They started upgrading our speeds/caps because a new fiber company (metronet) is building in the area. Now i’m on 1 gbps down and a 4 TB cap. I still plan to switch to metronet when they finally light up my area, as its cheaper for the same speeds (plus no data caps)


  • Even more frustrating when you realize, and feel free to correct me if I’m wrong, these new “AI” programs and LLMs aren’t really novel in terms of theoretical approach: the real revolution is the amount of computing power and data to throw at them.

    This is 100% true. LLMs, neural networks, markov chains, gradient descent, etc. etc. on down the line is nothing particularly new. They’ve collectively been studied academically for 30+ years. It’s only recently that we’ve been able to throw huge amounts of data, computing capacity, and time to tweak said models to achieve results unthinkable 10-ish years ago.

    There have been efficiencies, breakthroughs, tweaks, and changes over this time too, but that’s just to be expected. But largely its just sheer raw size/scale that’s just been achievable recently.




  • to my understanding, C# is sort of a “second class citizen” on godot; There’s a lot of stuff you can’t quite do or is more clunky than using GDScript. But i also havent used godot enough to really weigh in on that (only a couple of small projects).

    That said, while GDScript is very “python-like”, it is definitely not python. If you want to focus on C#, i would definitely echo the unity sentiment over godot.

    All in all, the best way to learn is to just do it. Go out on youtube and find some tutorials, and just hunker down and try!