Notices by Jonathan Nogueira (jnogueira@fosstodon.org)

@civodul

I admit I'm still very much new to guile and guix but my attempts at stabilizing my channel so I don't have to fix it every time I `guix pull` has been a bit of a nightmare.

Compare to npm or cargo's lockfiles which guarantee the dependency will always stay the same no matter if any other dependencies or cargo changes (3/3)

@civodul

channel dependencies don't seem to be built to handle pinning the dependent channel to a specific commit, and nor could I get inferiors to work as package inputs without either of them causing a bunch of ABI errors. (2/3)

@civodul

As a developer in rust, javascript, and a maintainer of a personal guix channel, yes.

Main thing is that if you have dependencies for packages that aren't things you actively maintain in your own channel (in my case the gnu packages mainline) there's not really an effective way to pin a dependent channel's packages without it causing some cascade of errors. (1/3)

@civodul npm helped build the semver standardization into people's brains.

Between semver versioning being "wanted" packages and lockfiles, it made it super easy to kind of make certain guarantees about your dependency tree, even when that dependency was maintained by a third party.

That dependency pinning is so hard in guix is actually something that is a neverending headache for me and package management, personally.

@strypey
> The Bluesky PDSes therefore hold these signing keys custodially on behalf of users, and users log in to their home PDS via username and password. This provides a familiar user experience to users, and enables standard features such as password reset by email.

When she talks about user keys is she talking about Bluesky's hosted PDSes at bsky.social or is she talking about self-hosted PDSes?

Because Self-hosted PDSes have their own keys and don't depend on bsky.social.