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/)SC
Posts
11
Comments
1,437
Joined
1 yr. ago

  • This is great: I just used it to stand up a VM for people to use to access a retro BBS that only has a 16-bit client that just doesn't run on any Windows from the last 20 years.

    It's a little undocumented and what's there is somewhat confusing (or it's entirely possible I'm just stupid), but it does exactly what it says on the tin.

  • Oh I fully understand and appreciate your position. I'm pro open-source-everything, but I made the pragmatic choice in this case because, well, years of fiddling with cheap printers made me realize that I really am not into this for the fiddling but more the end product, and if nothing else, the Bambu printers are really good at damn near being appliances.

    Hell, my 2d printers are more of a pain to keep working than this thing is, heh.

  • Honestly, I don't think there are any creality printers that "just work".

    I know you threw Bambu out as an option, but man, I love my P1P. The thing just prints with no drama, fuss, or headaches.

    Print 24/7 for a week? 100% success rate.

    Don't print for 3 months? Printer levels the bed and immediately makes a successful print.

    Yes, closed source bad, and propritary bad, and cloud bad, but in terms of pushing a button and a thing gets printed without even thinking about having to fuck with it? Pretty much unbeatable. (Or, at least, light years ahead of any of the other printers I've ever had.) It's so good and reliable I don't even sit there watching the first layer to make sure it's going to print successfully because of course it is.

  • Saw this on Reddit yesterday and been using it.

    Other than the lack of PIP support on Android, it's certainly a step up on the web wrapper app approach in terms of performance and not doing funky shit I didn't entirely expect.

    The downloading option actually works extremely well and does what it says it does.

  • Because wow subscribers keep paying no matter what Blizzard does?

    I mean, why offer anyone anything if they're going to pay you regardless.

    A F2P gatcha game is a little less sticky, so the maintenance compensation are part compensation and part marketing: it's another reason for you to come back and play more.

  • Cool; a lot of people are very concerned about power usage and thus it's probably the most important thing to know making a recommendation.

    If you don't care, then you're on a reasonable path. I ditched all my server-grade stuff a while ago for a single desktop build becase, well, I got tired of screaming computers, but your choice in server is decent at the price.

    I would say, though, if you have NO experience in server hardware, expect to run into a bunch of oddities inherent in server platforms - they're simliar but not exactly the same as what you'd find in consumer hardware in terms of hardware support but if all you want is computer + lots of drives + network access, then it's probably not going to end up with any stupid things that break what you're trying to do.

  • This is shockingly stupid. SMT has been a thing on x86 long enough for it to be able to buy it's own alcohol and yet somehow the windows scheduler STILL can't fucking deal with it?

    I'm not a kernel-level developer or anything but I mean, at some point you have to wonder how fucking trash windows kernel internals are that this problem keeps happening over and over and over and.....

  • Unless there's something wonky with your virsh configuration, no.

    This is a shitty explanation and if anyone would like to explain it better feel free, but the bridge interface acts as sorta like a network switch that can forward packets as well as be used for an interface, if configured.

    What that means is, essentially, your VMs will be attaching their ethernet devices to a "switch" that then routes the packets out to the local LAN as if it were, well, a nic plugged into a switch.

    virsh shouldn't assign an in-use MAC, as it generates a random one (and I have no idea what you'd have to do to make them not do that) so everything should... just work.

  • No, because the bridge interface becomes the primary interface as far as Linux is concerned.

    You'd just use dhcp to assign an IP to br0 instead of the physical ethernet device, though for a server a static IP is probably a better choice (so that it doesn't bounce around on your local network making it harder to access)