ElderWendigo @ ElderWendigo @sh.itjust.works

Posts

0

Comments

485

Joined

2 yr. ago

Function. In this case it's not just a matter of definitions because the windows options do not offer the same utility and convenience I've come to expect from a package manager for the last decade or more. It's a bit like me asking for a chocolate chip cookie and someone handing me a handful of chocolate chips and a cup of flour and wondering why I look disappointed.

I expect a package manager to handle all of my packages, be they system or third party. I also expect to be able to add repositories from developers for apps I need to be more up to date than the default system versions. This functions to also allow applications to be managed that aren't in the default repositories at all. I expect to be able to handle all updates with a simple command and be able to schedule those updates for when it suites my convenience, not when the operating system developers see fit. Those are the things I mean when I call something a package manager.

The windows store is really just a single application repository though, not a full featured package management system e.g. one that updates the operating system itself or allows alternative repository sources.

It's funny to me how windows users expect package management from each and every individual application instead of expecting that to be a basic function of their operating system.

I didn't call you anything, but it is interesting that you lept to that conclusion. Dictionaries are descriptive not prescriptive, so not sure how that's relevant in this discussion.

I've done both. The shield is both MUCH MUCH MUCH easier to setup and is so much more powerful than the Pi that N64, PS1, and GameCube Games are more likely to play well. OP didn't mention being on a budget. They also didn't mention their Linux skill level. Given thosee facts the shield is worth the price difference. They're not really saving money if they can't get the Pi working.

Buy an nvidia shield. Install retroarch. Find ROMs and put them on a USB drive, plug into shield. Pair any Bluetooth controller(s?). Play all the games.

Lies don't need to be intentional. You may not have been lying in the moment, but (especially if it's by your own actions) you have made yourself a liar after the fact if you don't keep to your promise. Your logic sounds like a narcissist's rhetoric. Your intent in the moment is worthless without follow through and does not relieve you of responsibility.

I already use MusicBrainz data to properly name a file away my digital music collection. I contribute release info and revisions whenever I can to further that same goal. Plex uses MusicBrainz data to help me search, filter, and play through a music library that is honestly bigger than I could ever fully listen to. It just makes sense that I be able to integrate and leverage my listening data so that I can better find the tracks and releases I've "lost" in my own collection and find new music. It's even more of a bonus that all that data is open, so I feel more like I'm actually contributing something to society (even if it's as trivial as music data and listening habits) instead of just giving it away to a private company to sell or keep secret as they see fit.

If you've ever seen the skull of a horned animal versus an antlered animal the difference between antler and horn is pretty clear. The center of a horned animals horn is bone and forms a single continuous piece connected to the skull, surrounded by flesh and hard keratin (like finger nails). Antlers grow more like a knuckle, not connected to the skull as one continuous piece.

Another horned oddity is the rhino, whose "horn" is more like a specialized fingernail (keratin again) than a true horn. A rhino "horn" is like a compressed lock of hair filed to a point, a hair shiv if you will.

Yet another weird horn like thing is the giraffe. They have bone knobby lumps on their head that are like something between a horn and an antler, being bone fused to the skull surrounded by flesh but without keratin.

Then there are narwhals. I don't know anything about narwhals. But they are cool and have "horns".

Like this one? Santa's reindeer are probably all female.

Why wait for the company to go under? FDA approval should mandate that the full spec and source code be open source and open to review by anyone, but especially the people in which those things are implanted and all of their medical practitioners. Medicine (and any publicly supported science in general) should never be closed off from public scrutiny.

None of what you've just said here is true. They don't work like house keys. Your system and my system are VERY different because I'm not making copies of my private keys anywhere. They never leave the safe place I created them. I only ever transfer the public keys. I could post my public keys here and there would be no security compromise for me. You came here asking for help. I tried to help you. I'm sorry it wasn't what you wanted to hear. Your attitude sucks.

Linux users have too much self respect and expect too much privacy and control over their own devices. That's a problem.

Do you really want an explanation for why a market might want large signage that they can change without much extra labor? Seems self evident to me.

And this comment is about as "First World Problems" as it gets.

No, it is inherently bad to copy around private keys. You have some fundamental misunderstandings of how key authentication security works. RTFM.

No, you're missing the point and creating a false choice here. You're supposed to generate new keys for each client device and load their various public keys into the authorized keys file in your server user's home folder. Copying around your private key like that is just BAD security and not how public key authentication is designed to work. It's not as if the only two options are your bad way or passwords.

As an example, you copy your single private key to various devices and even carry (a probably un encrypted) copy around with you on a thumb drive, while I generate a fresh key set from each client that I use to connect. When your private key is compromised (when, NOT if), you must remove that public key from your server to lock out the bad actor, but that also completely locks you out. Unless you have physical password access to the machine at the moment its compromised, you're also locked out. When one of my keys is compromised, I can just exclude that machine's key from my authorized keys list on the server and continue accessing my machine remotely via any of the other uncompromised clients.

Why are you trying to reuse an ssh key? That seems like a really bad practice. It's just not the way key pair authentication is supposed to work. Passing around and sharing private keys is BAD. Client devices create their own private keys and only share public keys. Just create a new key from ConnectBot and get it to your server via other methods. If you're already away from home without any other means of connecting, that last part is admittedly tricky and you may be SOL.

Isn't ConnectBot a dead project anyway? Last I checked, it hadn't been updated in years. Well, I guess I was wrong here. I can't find a simple full list of all the past updates, but I seem to remember moving away from ConnectBot because it lacked some feature I wanted and no longer worked on my new Android device. I've been satisfied with JuiceSSH, but I'm happy that ConnectBot is still alive since it was one of the first apps I installed on the first generation Android phone.

It's more than just knowing things outside the ms office ecosystem. People use the tools they have. So when IT locks down the whole system and it takes an act of God to get anything else installed, you find ways to hammer that nail with whatever blunt object you have in hand.

My guest WiFi is called Honeypot. I leave it up even when guests aren't around, but for some reason none of my neighbors have tried to connect. Either they're all much more tech savvy or much less tech savvy than I give them credit.