Notices by jade (leftpaddotpy@hachyderm.io)

are fedora and nixos exploring each others bodies this evening

wow the signal usernames design is good actually:
- username is exclusively an "adding you" thing
- this is because they are one way of getting an invitation to chat with you
- there's also randomized and resettable links that can be shared for this
- usernames must always have discriminator numbers, which can be freely selected
- usernames aren't shown to anyone you are in chats with
- by default phone numbers are no longer shared with chats

this seems to have basically Fixed it

@mathew @fourpenguins yup, it's of the exact same provenance as mine ultimately, and my html processor isn't that extensive at the end of the day.

we're both running makeinfo --html --no-split, just, their website is harder to find stuff on, they do fewer sneaky html editing tricks to make mobile work well (my site doesn't have x overflows but this is by deliberate effort), and their css is different.

@krans they are better than man pages *in content*, the info viewer, on the other paw, is terrible.....

i unironically advocate for just using lynx or w3m or something on docs.jade.fyi in place of the info viewer.

good evening! do you use #gnu software of any description? #postgres? #zsh?

have you found the manuals annoying and hard to find things in, or telling you to go f-- err i mean read the info page?

consider using the single page builds of such reference manuals on https://docs.jade.fyi

they have nice CSS and no page splitting so you can simply hit ctrl f

over the course of the last few months, my views on #anduril have changed from "please don't give them any support" to "we need to eject them from the #nixos community as soon as possible".

their employees (*multiple* right wing trolls) have collectively wasted *hundreds* of hours of contributor time arguing about sponsorship rules to stop them driving people away, and have begun to be actively cited by people as reasons to leave the community in higher numbers than they ever brought.

i have come to the realization that #prolog developers seem to be *way* more on their bullshit than #haskell developers, *and* they seem to have gotten a shocking amount done in their nearly boundless hubris in a more cursed and less-used language

you can write a Web site in this thing! what on earth. i mean i got paid to write website code in haskell, twice, but, this feels way less like it should be possible.

https://www.metalevel.at/prolog seems to be a good prolog book if you are also doing this

💭 hydras have so many heads to pat, they're very good and lovable creatures, even if they are full of perl and tech debt

A lot of the problems in the #Nix/#NixOS community are fundamental, built into its culture, from toxic development culture to the *two* repeated military-industrial sponsorship situations.

The culture of undermining community authority, of acceptability of conflict of interest, of tolerating abusive behaviour, goes up to the very top of the organization, with Eelco Dolstra.

You can read an extensive summary of the issues and sign an open letter to the Foundation here:

https://save-nix-together.org/

👀 I am working on making `inputs.meow.url = "https://some-forgejo/some/repo/archive/main.tar.gz";` Simply Work for forgejo-hosted nix flake inputs, which will probably land in forgejo 8.0.0

for progress, see: https://codeberg.org/forgejo/forgejo/pulls/3615

oh yeah the secret project I've been working on for two months, @lix_project, is finally in public preview. there's a fair number of rough edges in the website and infra remaining to fix but the software is rock solid.

thanks so much to the dozens of people who have been running `main` daily for several weeks and reporting the few remaining issues. at this point i would say it's just a stabler, faster, more user friendly #Nix 2.18.

if you want to try it out: https://lix.systems

contributions welcome! *provides postal address for sending floppies and zip disks by mail*

technically a nicer contribution experience than the average corporate project! more software should do this.

@smallcircles @jakehamilton @ktemkin one of the tvix developers is in the lix core team. we know it well :)

@artemist @Qyriad that's just Nix!!

@alanc @rst @raito @dalias yeah. which means really we have a responsibility to either make it possible to get those exact versions via docker or nix or so, or we need to abolish putting autoconf files in tarballs

@raito @alanc @dalias i would absolutely believe *autoconf* files to be a vector for malicious code, they're incomprehensible macro noise by nature, and this is just speaking as a nixos maintainer for whom these files are simply constantly broken and should not be used regardless of malice

tbh my view is that release tarballs that aren't simply the git state are a practice that should be abolished. or at least we should diff the heck out of them and figure out how to catch malicious autoconf.

@raito @alanc @dalias wonder if the solution here is to construct things to evaluate whether an autoconf script is one that could have been generated by any released version of autoconf and check the maintainers' work, so we could find out if there's malicious stuff going on (even if distros just ignore the release tarball anyway)

girl are you the ipv4 address space because you seem completely exhausted

@dalias every time I see people accusing systemd of not using the standard APIs, the so-called standard APIs in question did not exist before, and the functionality was, prior to systemd, achieved by the client software mutating things in such a way that assumes they were the only possible client (e.g. /etc/resolv.conf with VPN software, vs under systemd-resolved)

I simply do not understand your argument.

@dalias uhhhhh

> software should be decoupled, staying out of each other's way and exchanging data and reacting to events only through standard data formats and system interfaces.

"standard data formats". do you mean "text", for which you have a "broken handrolled C parser full of CVEs" because it's not actually structured *or* standard? or is there some magical format I have forgot about?

dbus is a standard data format. the systemd-standardized interfaces are a standard, structured format.