Public key authentication is more secure than nothing, and is more convenient than shared secrets and symmetric encryption, but bit for bit the secret material necessary for public key cryptographic schemes to be secure is more data than is required for symmetric algorithms.

But more to your point, public key cryptography is basically a usability nightmare. In order to talk to anyone you need to first validate their key using an entirely out of band scheme you already trust, and if you don’t do that then all the end to end encryption in the world is theatre.

Of course I’m being hyperbolic, it’s the internet, but seriously there a lot of people feeling secure with public key systems that are either totally insecure, or could be insecure and they wouldn’t know, or are secure to some random bystander but insecure to people and organizations that are often included in people’s threat models.

In the link you posted to the original question, it has a section on self hosting. That link takes you here where they say there are two servers.

Also, the documentation for Self Hosting basically starts by saying there are two servers.

I’m not sure how you self hosted it without hearing about it 😛

Ah, the Relay Server is only half of the service! If I understand correctly from the documentation I skimmed, and my existing knowledge of streaming systems, the relay server is just there to handle relaying the video stream from one device to another one in the worst-case-scenario that they can’t reach each other to form a direct client-to-client connection.

So probably your relay server has never been used.

But that’s just for media, and just for bad network configurations. The actual part that coordinates who can see which devices, etc, and sets up the media connections, is the other server, which it sounds like you’re not running. So your services are currently still using the public server to find each other and initiate contact!

I don’t know, I haven’t hosted RustDesk myself, but it sounds like maybe you’re not actually using your self-hosted server for your clients? Because that message sounds like it’s entirely about “The Public Server” which is not your server. Right?

Having the bios able to see the disk, but a live boot can’t, makes no real sense to me. If a partition was messed up I’d get that, but to not even see there is a disk to partition, doesn’t feel right. I know it’s probably a dumb question, but you didn’t happen to be messing around in BIOS settings or something right? Is it possible you changed some settings a while ago but haven’t rebooted in a while, and this issue was waiting for you this whole time?

If you don’t have any other slots on the mother board to try the disk in, you could buy an external adapter for whatever kind of disk you have, which would allow you to use this thing as a USB drive. That should at least allow the live boots to see it.

Also also, is it possible you have two disks, and grub is on one and your data is on the other? Again, kinda weird question, but it’s a kinda weird situation…

For me Jellyfin’s strength is that it can keep track of my wife’s place in her shows independent from mine, and also that the metadata and watched state and progress is synced between phone, tablet, and TV.

I have friends that daily drive BSD, but I never have. For me it’s because Open Source is already a small field, and Linux solves all the problems I have, while also having the most mind-share, focus, and community. I want it to be FOSS for ethics, which Linux is, but otherwise don’t need anything that BSD offers, so there’s no reason for me to attempt anything more. If there’s even one compatibility problem, it’d be one too many for no benefit.

That having been said, I do donate money every month to one of them, because I like that they exist. So that’s probably weird…

Similar to others here, but slightly different: start with what you’re most excited about. There’ll be some shitty parts where you’re confused and frustrated, and if you feel like you’re just doing something you’re “supposed to do”, it can feel like a job for no pay. Pick something you have an inner thrill for, and maybe that fire can carry you through the dark.

Yeah, like other people covered, it’s unfortunate but also very important. It’s easy to tie “visible wifi networks” to “surprisingly precise location on globe” in many places, so the permission is named for the worst case scenario. Yes, the app might just be looking for a wifi, but it also could use that same information to locate you, so it’s the location permission. Sensible.

If they wanted to support just this one feature without requiring a location permission, they could maybe have an API that is “are you currently connected to this opaque token” API where the app can ask “am I connected” and is just told “yes” or “no”. That’s probably safe enough. And then I could register the app with my wifi without the app even knowing what my Wifi is, it just gets a unique but random string.

The same is true of bluetooth. If I can list nearby bluetooth, I can see that speaker and this TV and guess location. But there could be an API that hides that, there just isn’t currently

I’ve encountered it very little, but when I encounter it it’s because I try to do something and it doesn’t work. So I check the permissions with ls -l, and it all seems reasonable. Huh, this should work. Try again, nope. Hmm. 20 minutes of trying random variations, strange results. Oh fuck, is this SELinux? Shit. Where do those configs exist again? How do I configure that? Google “SELinux cheat sheet” hmmm, I don’t have enough context to use that, Google “SELinux getting started”. Read tutorial, try to skim just enough to figure out what’s going wrong for me.

So I don’t hate it, I just haven’t ever had a use for it, but it has surprised me in a bad way before and cost me a lot of time and confusion, but I’ve never spent the time getting familiar because I’ve never had a use for it. And it comes up rarely enough I never remember anything about it by the time it bites me. I can’t even recall now what I was trying to do the last time I bumped into it.

For an honest answer, from an Open Source perspective, it’s mostly auth, profiles, and discoverability.

Presuming I have a GitHub account, when I encounter a library or tool or something that’s hosted on GitHub that means I can fork it, make issues, comment on issues, make pull requests from my fork to upstream tied to issues, and generally have seamless interaction with any and all software on GitHub.

Or, if I have my account added to a project, then I can also merge PRs and push to master and be a maintainer of that software without any friction.

When I see that software is hosted on KDE’s thing it’s like “Ugh”. I have to login to that, and create a profile for that, and then figure out how tickets work there, and how do I contribute to that. It’s enough to just not, most of the time. And maybe I do that for kdenlive. Then I have a bug for Gimp. Okay, what the heck do they use? Is that another login? How do I contribute over there? Is registration even open? Okay guix, oh boy a mailing list. Do I want to subscribe to a dev mailing list just to submit a 2 line patch? I think I’ll just not… I’m sure someone else will fix it eventually…

So besides all that, some people like their GitHub profile, and like that people can see all the things they’ve contributed to from one spot. That’s why it’s often linked on resumes, but beyond that there’s also a kind of cultural cachet to having a diverse and positive profile, should someone look. If someone is a maintainer of a repo with a lot of stars, that might tell you they’re “important” even if you don’t know why. Because maybe you’re a JS programmer, but this person seems to be big in the Java community, because they seem to maintain a few high profile java libraries.

And then lastly, it’s sometimes useful as a shortcut in searching. “Source code” is kind of a useless term for searching, so if I search “ruby Ledger file library” I’m more likely to get some docs or a rubygems page, but if I search “ruby Ledger file GitHub” I’m probably going to get what I actually want, which is a readme and a git uri I can clone and play around with. Or a web view of the source I can search through to debug something without cloning. At least assuming that is what I want, it depends on what my goals are, but it’s useful often enough that I do it sometimes as a way of jumping to the source part.

I’m typically anti-centralization, and anti-microsoft, and if we all move away from GitHub I’m sure I’ll live, but this is why I like it despite its problems. And sometimes I want a webview of file contents, with search, without cloning, so sue me 😛

I don’t know the original author’s opinions on AI, but I think it’s still fair to say that it was clearly Copilot’s goal to steal all the code and be good, and they had all the code, and so ethics aside one would expect them to have succeeded with flying colour at whatever their goals were, even if those were bad goals.

But they failed instead, which is impressive.

It’s nice of this poster to ignore the $181m spent on “other projects” and conclude this is some kind of scam. If we include the Linux Kernel with the other projects part, that’s about 67%, or two thirds, of their expenses are paying for various and assorted open source projects. Among them the kernel. So if you’re a “cash and cash alone” person, then 2/3rds of your money is still going as cash to software projects.

And if we include things like community tooling and project services, which may help a project in ways beyond just cash that becomes about 78% in total, or over three quarters.

That’s pretty good, I think, but to each their own.

Right, but what I’m saying is that git doesn’t store authorship information or line-by-line history, no matter how it’s done. Figuring out which line came from where is an algorithm the git blame command does every time you request it, and that algorithm can give different results depending on which options you give the blame command. And so what you’ve found here is a collection of commits that produces a situation the default blame algorithm can follow, without any optional flags, which is neat! Maybe not great for git history, but neat!

Interesting. Yeah, sounds like what git blame -C is for, so I’ve never made copies when splitting files, I’ve just moved lines between files naively. But I guess if one’s tools are limited and doesn’t have the ability to -C, then I guess I could respect the hack that is that solution?

I mean, I’m 99% sure git doesn’t store blame or authorship info in the pack files, even as a convenience cache, and just guesses by traversing the patch log with heuristics live when you run blame anyway, so the history mostly doesn’t matter there, but the way you’ve done it does seem to have tricked the heuristics into doing what you want without relying on an option, so that’s neat! It’s an interesting hack, and I like interesting hacks 😛

By the way, if there are down votes, they’re not from me!

Yeah, I’m with you. I mean, git isn’t magic. You “can” squash anything, including a merge commit, by just being at the end result, running git reset <commit you want to be squashed off of> and then running a manual git add and commit there. That’s basically all a squash is.

But what you’ll be left with us a single commit that contains all of the code from the branch you’re squashing and also all the code pulled in from every branch you merged, all written as though it all came from this one commit. And maybe that’s what you want? But it feels like also maybe it’s not?

Right… for sure… but then if you don’t want to squash, then it doesn’t matter you can’t squash a merge commit.

Huh. I have never in my 19 year career using git, ever wanted to copy a file and pretend all of the history of that file is also the history of the new file. I mean, I don’t think I’ve ever even wanted to copy a file? Why are you copying a file?

Like, maybe I’m just too familiar with git to see the forest for the trees, but what the heck are you doing over there? 😅

And just in case it’s useful, a tip is that you can use git blame -C to have the blame algorithm use a heuristic to try and find a “source” line if it was moved, including from another file, during a commit, and then continue following the history of that line, to try and get the real commit where this was written, not just the last time it was moved around.

I’m pretty sure all the Linux filesystems I’ve ever used don’t care about tilde. You might have to escape it or quote it if you’re typing it into a shell, since the shell might try to replace it with your homedir, but I don’t think the FS cares.

On my ext4 FS I was able to touch me~ow just now with no issues.

I don’t know a lot about stuff, but is there a reason you’re backing up the files off the disks, rather than imaging the disks into an ISO or something? I’ve never owned a 360 disk, so maybe there’s some reason I don’t know.