FizzyOrange

joined 2 years ago
[–] [email protected] 3 points 12 hours ago (1 children)

No, they're inherently optional in Git. There's no way to "check in" a git hook. You have to put in your README

Clone the repo and then please run pre-commit install! Oh and whatever you do don't git commit --no-verify!

You definitely need to actually check the lints in CI. It's very easy though, just add pre-commit run -a to your CI script.

[–] [email protected] 14 points 13 hours ago (1 children)

So... to store encrypted data that only the user can decrypt you don't need any fancy zero knowledge algorithms. Just have the user keep the encryption key.

For authentication you could use one of these algorithms. OPAQUE seems to be popular. I'm not an expert but it seems like it has several neat zero-knowledge style properties.

But probably forget about implementing it without a strong background in cryptography.

[–] [email protected] 4 points 14 hours ago (3 children)

To check that people ran the pre-commit linters.

Committing itself won’t be possible

That's not how pre-commit hooks work. They're entirely optional and opt-in. You need CI to also run them to ensure people don't forget.

[–] [email protected] 6 points 16 hours ago (5 children)

You need them in CI anyway to check people have actually done that, but yeah you definitely don't need to have CI automatically fix formatting and commit the fixes. That's crazy.

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

WPRS uses the term rootless like this. I didn't come up with it. But I agree it is not a great term. If you can think of a better one I will happily use it. Parallels calls it "coherence mode", which also isn't great.

Actually Xprs uses "seamless mode" which is probably better.

[–] [email protected] 1 points 1 day ago

Yeah it's more complex. I don't think there's any more overhead though, and there's no reason it will be slow.

Can’t you just run it locally?

No, unfortunately not.

[–] [email protected] 1 points 1 day ago (1 children)

Isn't it just basic X forwarding?

[–] [email protected] 1 points 1 day ago

Yeah true. It definitely has downsides. But so does begging corporations for money...

[–] [email protected] 2 points 1 day ago (1 children)

but there are literally dozens of strategies you probably don’t know about

Oh please tell me, wise old man! You can't be talking about garbage collection, reference counting, smart pointers, never-free, arenas, defer, or god forbid, the "I am perfect and can do it manually and never make mistakes" method. Because I know about all of those methods.

What are these other dozens of methods that I don't know about that mean Rust is unnecessary? 🙄

[–] [email protected] 1 points 1 day ago (2 children)

Sorry I misread, VNC is slow. RDP is a lot better. Does not appear to be rootless though, even though IIRC the RDP protocol does support that? I might have misremembered.

[–] [email protected] 1 points 1 day ago (1 children)

Yeah MJPEG isn't going to cut it, and as you say it's not rootless.

[–] [email protected] 1 points 1 day ago (2 children)

I mean it's totally possible in theory. Do you just mean nobody has actually written something that does this?

26
submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/[email protected]
 

Edit: rootless in this context means the remote windows appear like local windows; not in a big "desktop" window. It's nothing to do with the root account. Sorry, I didn't come up with that confusing term. If anyone can think of a better term let's use that!

This should be a simple task. I ssh to a remote server. I run a GUI command. It appears on my screen (and isn't laggy as hell).

Yet I've never found a solution that really works well in Linux. Here are some that I've tried over the years:

  • Remote X: this is just unusably slow, except maybe over a local network.
  • VNC: almost as slow as remote X and not rootless.
  • NX: IIRC this did perform well but I remember it being a pain to set up and it's proprietary.
  • Waypipe: I haven't actually tried this but based on the description it has the right UX. Unfortunately it only works with Wayland native apps and I'm not sure about the performance. Since it's just forwarding Wayland messages, similar to X forwarding, and not e.g. using a video codec I assume it will have similar performance issues (though maybe not as bad?).

I recently discovered wprs which sounds interesting but I haven't tried it.

Does anyone know if there is a good solution to this decades-old apparently unsolved problem?

I literally just want to ssh <server> xeyes and have xeyes (or whatever) appear on my screen, rootless, without lag, without complicated setup. Is that too much to ask?

 

Does anyone know of a website that will show you a graph of open/closed issues and PRs for a GitHub repo? This seems like such an obvious basic feature but GitHub only has a useless "insights" page which doesn't really show you anything.

 

Very impressive IDE integration for Dart macros. Something to aspire to.

view more: next ›