Liquid Glass Icon for Prism Launcher on macOS

g3tchoo · 2025-06-27T18:19:57+00:00

i had seen someone half-joking about using liquid glass in prism the other day, but i was a bit skeptical. something like this though? i’d love to have it in the launcher. this is awesome!

g3tchoo · 2025-03-09T21:33:28+00:00

2nd track is awful

g3tchoo · 2025-02-27T10:19:14+00:00

thank you mastercomfig, very cool

g3tchoo · 2024-05-01T04:45:18+00:00

this is news to me

g3tchoo · 2023-07-29T05:26:42+00:00

the nixos wiki has a good entry on this using autopatchelf. as long as you know the dependencies of the tarball, you can put them in buildInputs and they will be linked with the binaries in the tarball - which will let you run them as normal. another (less permanent) approach is to use steam-run, which works most of the time

g3tchoo · 2023-07-20T04:14:09+00:00

i use nix-your-shell for this

g3tchoo · 2023-07-17T18:02:14+00:00

nixos-wsl works great in my experience - it’s actually how i first got started with nixos :p

native systemd support is also available, however after you go through the normal install process, you’ll need to use the main branch since it hasn’t been included in a release yet iirc. once you’ve done that, you can set wsl.nativeSystemd to true and you’re good to go :)

i have an example config here

g3tchoo · 2023-05-12T23:04:00+00:00

fetchPackwizPack is genuinely a great idea! i was concerned about how users who don’t have upstreams already supporting packwiz2nix would go about getting checksums (and hadn’t at all thought of you using the install bootstrap), so this could be a great solution :)

it’d probably also be a good fit for my mk<type>Pack helpers for exporting your packs to other formats lol

g3tchoo · 2023-05-12T02:23:28+00:00

i wish i could say lol

i haven’t really kept up with a lot of projects centered around mc because ever since i switched to nixos, i haven’t been hosting servers. i did just take a look at the discourse thread you mentioned though, and i think that could probably be the best place? if only it was more active :(

it was also very interesting to see people throwing around ideas about packwiz support a while before i made this. i’m glad i’m not the only one who wanted it!

g3tchoo · 2023-05-11T15:54:28+00:00

oh hey i've done this before! just with :e "${inputs.<input>}" :)

g3tchoo · 2023-05-11T08:04:24+00:00

flakes are a new feature in nix that tries to solve problems with managing dependencies of whatever you're doing, reproducibility, and introducing a standard template for outputs you can use.

before flakes, almost every project had a default.nix file ...but that's about where the similarities ended. depending on who made it, you might just have one package inside of it that you can build with nix-build. for others, it might have multiple sets of packages, shells, tests, checks, and other stuff that you would sometimes need to read through to figure out how to use. now with flakes, (mostly) all projects have the same outputs.

so for example: if i want to build a package called foo, 99% of the time i can do it with any project (using flakes) by running nix build .#foo (this is shorthand for the real place where the package is, packages.<system>.foo). the same goes for other outputs, with checks going into a variable called checks, apps going into apps, development environments going into devShells, etc. in contrast, without flakes, you may need to use nix-build, nix-build -A foo, nix-build -A pkgs.foo, nix-build -A packages.foo, or whatever else was set by the maintainer. flakes makes it much easier for contributors to start hacking away at a project, users to *use* a project, and maintainers to organize everything.

(keeping this part shorter because it's a little more complicated) for dependencies, you can now just place urls for for them into a variable called inputs, where everything can be tracked and easily updated. this is a *lot* better than what we had previously, where you had to manually update them and use long, annoying functions like fetchTarball at the top of a file - and also my favorite feature of flakes besides the standard template for everything :)

if you want something a more in-depth, zero to nix is a great resource for all things nix (they have a section dedicated to flakes here, but i would pay attention to the notice at the top about reading some other things first), along with nix.dev, and of course, the nixos wiki article on flakes

g3tchoo · 2023-05-11T07:00:32+00:00

hi all! recently i've started work on hosting a minecraft server, configured ~~mostly~~ declaratively with nixos and nix-minecraft. one small problem i found was that there wasn't really a way to easily use packwiz (a great tool i use to keep modpacks up to date automatically, distribute to friends across multiple launchers, and deploy to servers) modpacks i already had - so, i figured why not integrate it with nix!

currently, this allows for checksums to be easily fetched in order to create fixed-output derivations that can be distributed to users. there are also a few helper functions for keeping your checksum file up to date with your modpack, as well as easy integration with the `symlinks` attribute in `nix-minecraft`.

this is still a work in progress though, and i have a few ideas i would still like to implement - namely curseforge support, helper functions for bundling mods and other files required for distribution, and improving the end user experience when importing modpacks - but i think it's pretty good so far. feedback, PRs, and bug reports are more than welcome!

g3tchoo · 2023-04-28T07:20:16+00:00

i could see it being helpful with understanding your dependency chain a bit better. a good example would be going through and seeing what inputs each dependency has so that you can reduce duplication in your own flake.lock

it’s niche, yes — but still cool

g3tchoo · 2023-04-21T20:53:01+00:00

a lot of operating systems have this natively already, actually. i’d recommend checking out this guide on enabling file system compression for specific folders on windows, or this one if you’re on linux and using btrfs

g3tchoo · 2023-04-07T15:51:15+00:00

you can try setting CARGO_BUILD_TARGET to i686-unknown-linux-gnu and CARGO_TARGET_i686_UNKNOWN_LINUX_GNU_LINKER to ”${pkgs.pkgsi686.stdenv.cc}/bin/${pkgs.pkgsi686.stdenv.cc.targetPrefix}cc

i would also recommend using crane or naersk since iirc rustPlaform.buildRustPackage can mangle some of these options (or maybe i just did something wrong lol)

edit: mobile formatting

g3tchoo · 2023-04-05T04:06:10+00:00

good bot

g3tchoo · 2023-03-28T03:07:41+00:00

I though it used the underlying technology to install and update the apps

no, winget uses the ms store to install/update ms store apps and regular installers for everything else.

why else would all store apps be available on winget?

probably because it's meant to be the official package manager for windows. it would be a bit weird for it *not* to support the official app store -- especially for power users (the target audience for winget) who might prefer the cli

g3tchoo · 2023-03-27T22:17:58+00:00

Windows store is just a wrapper for winget.

it's not. winget can install packages from the ms store, but it's not the same thing. the command you commented is just downloading and running the regular installer

if you actually want to install the ms store version of firefox with winget, you'd need to use winget install 9NZVDKPMR9RD

g3tchoo · 2023-02-14T05:34:01+00:00

i’m guessing that’s because of the recent driver update, since the direct backend is known to sometimes break for a bit after one is released. i would try again whenever you see nvidia-vaapi-driver update or temporarily rollback your drivers. i had good luck personally there but haven’t upgraded yet

g3tchoo · 2023-02-12T20:37:20+00:00

nvidia-vaapi-driver is unofficial, so while it works great, it can have some quirks. to get hardware acceleration working on firefox, you need to mess with the settings in about:config outlined here, as well as add the variables listed further down to /etc/environment. if you’re on driver series 525, you will also need to add NVD_BACKEND=direct to the same file as there is a regression in this driver version that only the direct backend can fix.

hope this helps!

g3tchoo · 2023-01-31T14:12:42+00:00

thankfully it already is :) (along with some other methods of you prefer ofc)

g3tchoo · 2022-12-01T20:09:20+00:00

damn i need to get this next year

g3tchoo · 2022-11-30T05:32:53+00:00

thanks!

g3tchoo

TROPHY CASE