Epsilon_02

@liaizon @6543 some more information what's going on: https://codeberg.org/thefederationinfo/the-federation.info/issues/379#issuecomment-25230205

@LovesTha oh I have another idea, how about a live system? 🤔

@LovesTha well that's unfortunate 😅
IIRC the python project was created with poetry. I looked it up, poetry exists in the alpine packages, so at least the container itself should be small compared to an Ubuntu one. But yeah you have to do a rebuild to use docker because of the daemon.

@LovesTha you can try to create a package via nix-init https://github.com/nix-community/nix-init
This should do the most things for you and then run this package locally (forgot the exact CLI commands for this). What I have read very often here on mastodon is that Nix and python is the tinkering heavy pairing what you can get.

Could a VM/docker maybe do the trick? Since this sounds like it will be a one shot and hopefully never looked at it again.

@pglpm @dreua @adventure_tense I do the same when looking for new projects.

Since this is scraper prevention maybe they will loose this when the current scraper campaign is done 🤔

@dreua @pglpm @adventure_tense I tried it, when logged in, it works.

@trevdev weird it works flawless on my systems. Here is my config if you are still interested to tinker with:
services.greetd = {
enable = true;
useTextGreeter = true;
settings = {
default_session = {
command = "${lib.getExe pkgs.tuigreet} --time --remember --remember-session --cmd niri-session";
user = "greeter";
};
};
};

And yes user is just "greeter" when I used my user name it broke

@trevdev I don't know which greeter you are using, but I am quite happy with greetd with tuigreet which starts niri in my case (everything configured via nix of course). The Arch wiki provides good examples which are sway so I think this should work out of the box, but I don't have much experience with sway https://wiki.archlinux.org/title/Greetd#tuigreet

@vivekanandanks agreed, I just wanted to mention that guix has its roots in nix

@vivekanandanks another thought of mine is, that #nix is already the word for all the other things, because #lix is as fork of it and works with the same language, also determinate nix. #guix is also a fork of nix IIRC.So with nix you mean all of it because everything else was created out of it
I think that's the same as "let me google it" which just means I search through the internet and I don't have to use Google for this kind of task. Its easier to say as "let me search through the internet"

@vivekanandanks thanks for clarification.
How about going with the history of the name "nix" which has a few different meanings, dependents how you interpret it. As far as I remember it comes from the dutch word "niks" which means "nothing", also the German word "nix" means also "nothing".
So with #nix / #lix / #guix we are able to produce something out of nothing 🤔
Well I also found out that "nix" should mean "snowflake" in Latin.

Aside from that I like #declarative and #atomic the most.

@vivekanandanks one additional thing, their is for example a bot which boosts posts with #nixos even of accounts which are currently not "known" by the server my account is on, so I would miss these posts without that bot.
I don't know the correct term for that behavior but I have read something about it that not always all posts are coming through to someone if two servers never have "spoken" together. So a bot helps with that. But maybe this is deprecated knowledge.

@vivekanandanks well I for example follow #nix #nixos and #lix because these are the three which I am interested in and want to see posts. I'm quite sure most of us will have q similar "collection" of hashtags which they follow.
I think with #nix and #guix you will get 90% of the people you want to see your posts and don't have to add so many hashtags.
I think I would miss future posts if another hashtag is used.

@Brett_E_Carlock sounds reasonable that this should work.

I just looked up your repo in codeberg and it looks like it worked?

@Brett_E_Carlock I think the only way to do this is with a script which accesses the API reads out the issues content and writes them to another repo. But this will only work with issues not with PRs. Is moving/renaming a repo not an option?
The only other thing is to ask an admin if they could do some SQL magic in the DB.

Stupid idea after some thinking: move the repo where you want it to be, then fork it and modify the content of the moved repo to your liking. Then kill the link of the fork.

@rozodru the star was mainly for the poking.

Creating an ISO based on my config is one of the many things on my long todo list, since as I know myself I will do some over engineering again 😅

@rozodru found your project through this post. I am happy with my own NixOS config, but you got a star from me, because I like the idea (and reason behind it) and maybe I need it in future for a fast spinning up a NixOS based live system

@pat_dev @bnjbvr @thelastpsion codeberg was using Anubis for some time for the resource heavy paths and moved away from it and replaced it with a link-labyrinth (forgot the name of it).

@IncredibleLaser yes, but with flake-parts it changes a little bit, for the outer passes `inputs` and `self` and the inner one (what also @vivekanandanks uses in their example) is for `pkgs`, `config`, `lib` and so on which gets passed directly into the module and does not come from outside of the module. At least that's how I understood this.
E.g.
{inputs, self, ...}: {
flake.nixosModules.somemodule = {pkgs, config, lib, ...}: {
...
}
}
But these are optional when you only pass `...`

@vivekanandanks in your shared GitHub link. Sorry this got lost during reformulating my sentence 😅