• 1 Post
  • 34 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle











  • I hope you understand how this is discouraging: at present, federation is anything but straightforward.

    There’s also a question of perspective. If you approach federation with the mindset that it will be like the sort of SSO you get with using google products, microsoft ecosystem, or facebook to log in to many websites, then yes: it’s doesn’t look straightforward.

    If you approach it with the perspective that the coupling between fediverse applications being more loosely coupled, and have the way email work in mind, then it is actually more natural. Each application can do their own thing, and provide all or partial compatibility with the fediverse. Think of a blog application, which rely on the fediverse only for the comment section of each blog posts, but also does other things specific to that application. Taking the example of email again, nobody thinks they should be able to log-in to microsoft outlook using their gmail account, or to gmail using their home-made account, in order to read and send emails.

    There’s a narrative aspect to it too.







  • The flakes interface of nix may change in the future, and you should be prepared to update your code, documentation etc. if and when that happens. Consider flakes have been around since nix 2.4 and the interface haven’t drastically changed since then. If that risk sounds acceptable to you, then do use it :)

    There is an ongoing effort to get flakes away from the experimental category, but as you may guess, it is a big chunk to stabilize all at once. The original RFC was closed https://github.com/NixOS/rfcs/pull/49 a long while ago, due to it describing the experimental feature, and not the final one. AFAIK, there’s no “one” RFC being discussed on finalizing an initial stable version of flakes (but I could swear I’ve heard of one).