Swagtoy

Systemd commits: userdb: add birthDate, familyTree, killCount, potentialThreat, incomeYearly, isOnDoNotFly to JSON user records OpenRC commits: add... puppies! ^.^ :P and also..... kittens!! (^ :3 ^) and remove GNUism to comply with POSIX definition that was denied in court 25 years ago but later standardized as of 2028. You'd hope.

@nina_kali_nina @konstruct @FritzAdalis @lanodan I appreciate the kind response, because I am still recovering from release.. :) trying to take it easy.... Its a red flag for me too. I understand why people do it, but this is also a new trend, so I'm trying to light some awareness on when it occurs, that people should be critical, and not immediately jump the gun or ""harass"" project devs or whatever (not saying you were doing so, but it can happen, i imagine...im a bit anxious about it), because it affects us even though we absolutely don't want it. The copilot stuff too; it was an experiment by another dev who was told not to do so here. None of us are a fan here. We're not actually a large project, anyhow, maybe a large audience (thats a lot of foss stuff, actually). So its actually a bit easier to control, but its aproblem for all projects right now. Some are straight up endorsing it, some might be tight in reviewing AI stuff, some dont want a bit to do with it. Trying to aim to be the latter, but it still slipped through, and we aint perfect here. Its just what it is...

@nina_kali_nina@tech.lgbt @konstruct@woof.tech @FritzAdalis@infosec.exchange @lanodan@queer.hacktivis.me If you all want to look into it critically, feel free, but I wrote a response on it See: https://social.treehouse.systems/@swags/115914027180419851 I'm _okay_ with everyone doing this whole "blocking Claude" thing, but please don't immediately jump the gun for project maintainers who have had to put up with the bullshit!! We got rid of it, thankfully, but even then, that doesn't mean we just "all magically endorse it" and it kind if slipped in by a single developer who I've since talked to. The Claude one was a PR leached in by someone, but there were some copilot bits as well. There will be a no AI policy soon, so again, please don't take this as some bizarre last minute damage control... it was an issue well over with but Im now certainly a little topsy that people are gonna keep recycling this discussion :/ and it rubs me the wrong way too.

@mgorny@social.treehouse.systems It's always been my favorite distro... it has taught me a ton about Linux and still does everyday...

• Very very nice for debugging things and testing patches. This is one of the main reasons I love source based distros; portage just automates a lot of it :)
• Ports-tree like, so rather easy to package/work with.
• Portage is wonderful
• Superb documentation. I'd say gentoo tooling has the best documentation ive seen of any distribution.
• Love it's openness for portability; though ive mostly owned amd64 for my life ':D i still believe portability is very important...
• I truly love learning, and gentoo has certainly helped me do that.
• ..Very fun community. fkin love the community :)
• Seriously, i think i love contributing more than using it :) Everyone is friendly and good fun

More, but the list would get too long :)

@alice ill sit this one out

@lanodan @FritzAdalis @nina_kali_nina @konstruct It's most probably that will happen. Just haven't drafted up how we want it to look, it'll probably just be simple. Its also kind of been in the back of our minds. At this point its a "trade secret" rule to just not do AI commits or PRs, but writing it in stone would be nice. Rewriting history is gross in general IMO, yeah, even hiding old arguments that got heated or anything of the sort; I do not want to do things like that, because they are historically a bit significant to us, and shouldnt be hidden from other eyes even if it could damage our rep, its something to chew on for anyone.

@nina_kali_nina@tech.lgbt @konstruct@woof.tech @FritzAdalis@infosec.exchange @lanodan@queer.hacktivis.me I don't believe history was rewritten, we actually don't want to do that because its kind of important I suppose to leave mistakes in :P Its probably on a Co-authored-by snippet or some other git commit bit. You can grep git log and check. In any case, if we _did_ rewrite history, I am actually pretty certain that GitHub will not remove the "contributed" user that might, say, show up in stats or whatever.

@barthalion@social.treehouse.systems Ok true... there is a weird mix of satire and genuine arguments that I honestly cant distinguish them now :P fun read indeed!

@barthalion@social.treehouse.systems I agree with his flatpak/appimage points; maintain what you can, but:

Think about what it costs us as a society for you to be recompiling every package you install on Gentoo. For every ridiculous declarative config you HAVE to make yourself on NixOS

To be fair, I'm not sure why the hostility... a lot of gentoo, nixOS... debian, whatever people are usually contributing fixes, tests, and bug reports back upstream when they can, which I would be inclined to argue is still 'valuable'... this bit alone almost completely invalidates the entire argument because he thinks the fragmentation as a whole is "pointless" and "valueless", when... honestly, its really not; people who work with linux are still here to please themselves, after all, and usually those medding in their own territories would be expected to have to help themselves, anyway.

What a childish article, really.

@alice@mk.nyaa.place thx. i wanna be a stand up comedian some day. think id be alright

@verdre@mastodon.social Anytime i complain about how poor Linux's memory usage is someone comes and breathes down my spine about how they managed to keep it down to 200mb by running some window manager.. try that on a windows/mac!! But thats never what it's about 🥹 swap is _really_ barebones on Linux still. Then you have applications which swap out and never return back to ram, so they *feel* slow when your system was low on memory to begin with. This one used to eat me all the time and all you can really do is hit the swapoff key on your keyboard. And then... ""sparse"" swap space, so you alloc/dealloc swap space overtime... its just not really possible right now, unless you do some funky stuff like swapon a new segment then swapoff and monitor that over time (no idea if that even works). You probably need some systemd/service doohickey for that right now... at least thats all i can think of.

@aperezdc@oldbytes.space I have 6gb of memory on my laptop. I can make it work by having a massive swap part (i do now) or setting up a big swap file. It hits somewhere around the 20gb mark alone.