What's a weird saying?
hallettj @ hallettj @leminal.space Posts 3Comments 186Joined 1 yr. ago

Do you have anything to check whether the current directory is under /media/
or /mnt/
so that you can change the drive letter according to a deterministic assignment?
/s
It seems to me that you're asking about two different things: zero-knowledge authentication, and public key authentication. I think you'd have a much easier time using public key auth. And tbh I don't know anything about the zero-knowledge stuff. I don't know what reading resources to point to, so I'll try to provide a little clarifying background instead.
The simplest way to a authenticate a user if you have their public key is probably to require every request to be signed with that key. The server gets the request, verifies the signature, and that's it, that's an authenticated request. Although adding a nonce to the signed content would be a good idea if replay attacks might be a problem.
If you want to be properly standards-compliant you want a standard "envelope" for signed requests. Personally I would use the multipart/signed MIME type since that is a ready-made, standardized format that is about as simple as it gets.
You mentioned JSON Web Tokens (JWTs) which are a similar idea. That's a format that you might think you could use for signing requests - it's sort of another quasi-standardized envelope format for signed data. But the wrinkle is that JWTs aren't used to sign arbitrary data. The data is expected to be a set of "claims". A JWT is a JSON header, JSON claims, and a signature all of three which are serialized with base64 and concatenated. Usually you would put a JWT in the Authorization header of an HTTP request like this:
Authorization: Bearer $jwt
Then the server verifies the JWT signature, inspects the "claims", and decides whether the request is authorized based on whether it has the right claims. JWTs make sense if you want an authentication token that is separate from the request body. They are more complicated than multipart/signed content since the purpose is to standardize a narrow use case, but to also support all of the features that the stakeholders wanted.
Another commenter suggested Diffie-Hellman key exchange which I think is not a bad idea as a third alternative if you want to establish sessions. Diffie-Hellman used in every https connection to establish a session key. In https the session key is used for symmetric encryption of all subsequent traffic over that connection. But the session key doesn't have to be an encryption key - you could use the key exchange to establish a session password. You could use that temporary password to authenticate all requests in that session. I do know of an intro video for Diffie-Hellman: https://youtu.be/Ex_ObHVftDg
The first two options I suggested require the server to have user public keys for each account. The Diffie-Hellman option also requires users to have the server's public key available. An advantage is that Diffie-Hellman authenticates both parties to each other so users know they can trust the server. But if your server uses https you'll get server authentication anyway during the connection key exchange. And the Diffie-Hellman session password needs an encrypted connection to be secure. The JWT option would probably also need an encrypted connection.
My conclusion after researching this a while ago is that the good options are Borg and Restic. Both give you incremental backups with cheap timewise snapshots. They are quite similar to each other, and I don't know of a compelling reason to pick one over the other.
Always a good one! It seems overdue for an update to include Clojure, Go, Rust, Typescript, Swift, and Zig.
Are you using swayidle? It's supposed to automatically keep the screen on when there is full-screen video playing. It's the same in Gnome: you generally don't need caffeine if a full-screen video is going.
How are you playing videos? Maybe the player doesn't correctly implement the idle inhibit protocol. Or if you're using sway bindings to make the window fullscreen instead of using the app's own fullscreen mode then maybe the player doesn't know it's fullscreen, and doesn't set up the idle inhibit.
If you do want manual idle inhibit control, if you use Waybar it has an idle inhibitor module that mimics caffeine. If you don't use Waybar there is a little Python script you can run. Kill it when you want to stop inhibiting idle. actually wib looks like a better option
For the curious, https://arxiv.org/abs/1204.1749
Mostly from Josh Johnson
Clipboard support in the Wayland driver.
Nice!
Permanently Deleted
This seems like a restatement of X. We still don't understand Y. I'm especially confused about:
- Why are SHA-256 and friends ok, but IPFS CIDs are not? They have basically the same functionality.
- Do you need a distributed network, or is a single server ok?
There was some hint that maybe you're concerned about reproducibility for CIDs? If you fix the block size, hash algorithm, and content codec you'll get consistent results. SHA-256 also breaks data into chunks of 64 bytes as it happens.
Anyway Wikipedia has a list of content-addressable store implementations. A couple that stand out to me are git and git-annex.
I've mainly worked as an employee so I don't have as much experience with freelance gigs. But nearly every job I've had in 18 years has been through networking. Organizing and speaking at programming meetups opened a lot of doors for me. It gets a lot of attention on me while I get a chance to present myself as an expert.
Eventually I'd worked with enough people that when I've been looking for work I find I know people who've moved to new companies that are hiring.
I'm gonna take a couple of stabs in the dark.
According to this Stack Overflow answer using tee
can prevent the prompt from drawing which makes it appear that a script has not terminated. The answerer's workaround is to put a very short sleep command after the tee command.
If this is what happened to you maybe the reason the script works in bash but not in zsh is because you have different prompts configured in those two shells.
Another idea is to replace tee
with sponge
from moreutils
. The difference is that sponge
waits for the end of stdin before it starts writing which can avoid problems in some situations.
Oh yeah, and Nix has the advantage that you don't need containers. If you want to run a graphical app in a container it might be tricky to access the window manager on the host system. Maybe that's why you were setting up i3? Yeah, containers are great and flexible, but they also have a variety of downsides so Nix is better ;)
I agree; and I wanted to mention that you don't need NixOS which is a full distro. Nix the package manager can be installed on any Linux distro, on Macos, or on Windows with WSL. You can set up your reproducible environment by including a devenv config in your repo, or a Nix flake.
There is documentation available for flakes here: https://zero-to-nix.com/concepts/flakes/
They can flash by pressing the button. On some flashlights partially pressing and releasing the button flashes the light off and on. That's a notable difference from, say, lanterns where you need a cover or shield for signalling.
The problem with "torch" is that there's already a thing called "torch", and now I don't know which thing you mean. The word "flashlight" has avoided critical ambiguity in many of our Indiana Jones movies.
A pidgin language is a simplified language that appears when people need to communicate with each other, but they don't have a common language. But if the situation lasts long enough for children to grow up learning the mixture of languages as their native language then it quickly evolves into a creole. The difference is that a creole is not a simplified language, and it has regular grammar. While growing up children always "reanalyze" their language to regularize grammar and fill in gaps in expressiveness. This is a main driver in shifts in all languages. The effect is especially profound when starting from an irregular, simplified language.
Because of reanalysis pidgins tend to either be temporary, or to give way to creoles. I don't know of a pidgin that exists in the US right now. There are creoles - there are some details here
No, but I remember overhearing one of my teachers saying it's actually helpful. That was in the early 90s in California.
I'm not saying he won't get away with stuff he lawfully can't do. I'm saying that it's easier to get away with it if too many people think it's legal or normal.
I'm thinking about protesting and maybe a tax strike, particularly if the Supreme Court says that actually a president can withhold federal funding despite earlier courts repeatedly blocking previous presidents from trying the same crap.
But it's not about me specifically. I know it's cliché, but the guy in power only has power to the extent that people accept it. Right now there are lots of people out there who hate these orders, but are confused about whether they are legal, or assume they are legal, and are therefore less likely to resist. Public outrage is a real force that many governments have found themselves unable to simply shrug off.
I know there are lots of possible origins for this phrase, but I think of it as "pleases" and "thank yous". The "k" sound from "thank" followed by the word "you" combine to sound like the letter q.