Inbred: chaorace’s family has been a bit too familiar. (Can be inherited)
This article is good, really good. Somehow despite having used plenty of builders in the past I barely even knew half of the stuff documented here.
I’m particularly interested in learning more about the special paths that derivation outputs can provide – looking forward to seeing that section expanded.
Another reason is that “CP” got jokingly coopted by abusers in the form of various dogwhistles (e.g.: “cheese pizza”). It made more sense to adopt a new acronym rather than try to uphold any sense of decorum while sharing ownership of the term w/ edgelords & predators.
Communism with western characteristics?
Oh, bother…
Delicious gruvbox. Excellent choice with the focus highlight color (I do something similar).
If you use picom, try out this shadow config I made for a similar theme. It creates a neat accent effect that complements the focus border and gives a flatter look:
shadow = true;
shadow-radius = 1;
shadow-opacity = 0.50;
shadow-offset-x = 2;
shadow-offset-y = 2;
shadow-color = "#211521"
Hence, “Zot”:
Zot’s identity layer is unique. It provides invisible single sign-on across all sites in the grid.
It also provides nomadic identity, so that your communications with friends, family, and or anyone else you’re communicating with won’t be affected by the loss of your primary communication node - either temporarily or permanently.
The important bits of your identity and relationships can be backed up to a thumb drive, or your laptop, and may appear at any node in the grid at any time - with all your friends and preferences intact.
Crucially, these nomadic instances are kept in sync so any instance can take over if another one is compromised or damaged. This protects you against not only major system failure, but also temporary site overloads and governmental manipulation or censorship.
Nomadic identity, single sign-on, and Hubzilla’s decentralisation of hubs, we believe, introduce a high degree of degree of resiliency and persistence in internet communications, that are sorely needed amidst global trends towards corporate centralization, as well as mass and indiscriminate government surveillance and censorship.
As you browse the grid, viewing channels and their unique content, you are seamlessly authenticated as you go, even across completely different server hubs. No passwords to enter. Nothing to type. You’re just greeted by name on every new site you visit.
How does Zot do that? We call it magic-auth, because Hubzilla hides the details of the complexities that go into single sign-on logins, and nomadic identities, from the experience of browsing on the grid. This is one of the design goals of Hubzilla: to increase privacy, and freedom on the web, while reducing the complexity and tedium brought by the need to enter new passwords and login names for every different sight that someone might visit online. You login only once on your home hub (or any nomadic backup hub you have chosen). This allows you to access any authenticated services provided anywhere in the grid - such as shopping, blogs, forums, and access to private information. Your password isn’t stored on a thousand different sites; it is stored on servers that you control or that you have chosen to trust.
You cannot be silenced. You cannot be removed from the grid unless you yourself choose to exit it.
In hell! 🔥🔥
I like flakes a lot, speaking as a type of user which I’ll call a “casual packager”.
This is to say that I like being a good citizen and sharing my packaging efforts… while also simultaneously feeling totally uninterested in becoming an owner-for-life. Flakes let me share a package without those pesky strings – when the user installs a package using one of my flakes, a personal lockfile gets generated at the latest git commit and that’s that. If the user doesn’t like the version they get, then the power is in their hands to choose a different git ref via their own generated lockfile.
Obviously this is something of a user footgun, especially for consumers of high-impact or security-critical applications, but most of those things are already important enough to get packaged. When it comes to niche, infrequently updated stuff, this approach works super well and helps to draw many reluctant packagers like myself out into the open.