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/)HR
Posts
1
Comments
24
Joined
2 yr. ago

  • Sounds like maybe you ran it as a container and didn't mount the document archive externally then updated the container. That would have likely blown away the actual ingested documents but left the Metadata (including the OCR data) where it was, assuming the database was either its own container or mounted externally

  • runas is trash, to be honest. I've been waiting 30 years for an OS-native tool that allows me to delegate specific commands for specific users to run with specific parameters as admin. Something I can do with sudo (well, sudoers) in 5 minutes is outright impossible on Windows. I'd like to believe that Microsoft will implement this part of sudo, but I'm not gonna hold my breath

  • I know this is a meme /c, but for real, I bought this exact same product a while back. If this is your photo, just be careful about what you put on it. Mine lasted 2 months with a grape vine on it before it collapsed.

    Source: Arch user

  • It's definitely the clunkiest of the 3. I almost gave up on it but if you stick with it you'll figure it out and maybe even learn to like it. RotTR and SotTR are both much better from a control perspective. FTL is great for when you just want a chill game. It's hard but not sweaty. I really wish they had it for Android...

  • I generally go back to the nostalgia-filled retro titles from the nes-psx eras or for a more modern experience I'll lean into Mark of the Ninja, Guacamelee, or FTL. I've also put an embarrassing number of hours into the new Tomb Raider trilogy and Breath of the Wild. BotW counts as vintage these days, right?

  • I feel like this is legitimately more true than a lot of people think. Say what you want about the average end user, but UX is a HUGE driver with regard to adoption and user uptake. You can have the best of everything else in your application, but if the UX sucks, folks just aren't going to use it

  • I kinda disagree with the context comment though. That era of computing was inherently wild - nobody had figured anything out yet beyond the most basic and general strokes, and security analysts (such as they were) had what would be considered a childish understanding of IT security by modern standards. Heck, Windows95 didn't even have the TCP stack enabled by default, so when these features were being designed, planned, and coded at Microsoft, there was no context for security on that kind of feature. Wikipedia says that Win95 was in the planning stage in 1992 - I take that with a grain of salt, but the concept is valid. Microsoft was writing the core features of Windows 95 before WAN was even really a thing. Like I said, I don't disagree with the idea that AutoRun was a terrible thing among many terrible things Microsoft is responsible for, but given the era in which AutoRun came out, it was a reasonable trade-off between security and functionality for the lowest common denominator of user. The whole thing should have been disabled (on 95 and 98) when Windows 98 came out since they should have known better at that point.

  • I don't disagree with this statement in general. That days, I don't know how old you are and whether or not you were really around the home PC space when the auto run feature first came to be. I can sort of understand what Microsoft was trying to accomplish with it... the mid-90's were a wild, lawless time with regard to personal computing. There was a lot of heartburn on the end user side because things were changing so rapidly. Getting them to understand that what a "drive letter" was, how to get there, and how to run an application from it (let alone what an application even was) proved challenging even under the best circumstances. The ability to insert a CD into the drive tray and have it "just work" (also a big theme in Win 95/98) was a godsend for a lot of publishers.

    Of course, in today's world, we look at that kind of feature and rightly say "yo, that's fucking crazy, why would you do that?", but in the old days it really did help. At the end of the day, it was a useful feature that, like a lot of windows legacy crap, was left in the OS after its usefulness had gone and just became another attack vector.

  • I'll also add to this that WSL is a security nightmare. If something manages to dig its way into your wsl install and add, for example, WINE, there's no end to the (hidden to your av) mischief it can enact.

  • I was just saying that there can be a lot of good reasons for downtime. Heck, I use a secondary in my network because sometimes my unraid host starts dnsmasq and it clobbers my adguard container

  • Depending on the client, it can be. The Microsoft page pretty cleanly defines expected dns client behavior [https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dns-client-resolution-timeouts#what-is-the-default-behavior-of-a-windows-7-or-windows-8-dns-client-when-two-dns-servers-are-configured-on-the-nic](Microsoft learn). There haven't been any published changes to this that I've seen, and it more or less matches my experience. Linux is a lawless land in this respect, but it really boils down to "it might", so caveat emptor there. That's also why I suggested a public ad blocking dns server as a secondary, in case multicast dns does its multicast dns thing

  • Home Improvement @lemmy.world

    Pipes knocking around 120bpm