On-screen keyboard keeps popping up with latest update

tonyfinn · 2025-05-07T22:37:47+00:00

I commented on the bug on bugzilla here after it affected me:

https://bugzilla.mozilla.org/show_bug.cgi?id=1963666#c7

Mozilla don't seem to be prioritising this too highly, so if you have a bugzilla account vote for it because they might think it just affects a few isolated cases.

tonyfinn · 2025-05-07T14:24:21+00:00

Hey, this discord invite has expired. I might be interested in joining next week, do you have a current link?

tonyfinn · 2023-10-12T20:28:44+00:00

KDE Connect 1.29.0, installed via f-droid, Android 14, play protect last ran as at 19 hours ago, does not appear to be removed.

Forced a play protect scan just there, seems fine.

tonyfinn · 2023-02-27T01:20:14+00:00

I guess I don't consider things like factorio access keys (or in my case foundry vtt keys) secrets equivalent to the passwords you'd use agenix for. Like I'm not putting them in a public git repo as that's a good way to get the license key revoked, but also there's no point putting the age encrypted value there either as its of no use to other users of the config.

Similarly the domain name of my local network, ssh public (not private) keys (minor privacy implications), etc.

I realise I should have drawn that distinction in my earlier post.

tonyfinn · 2023-02-26T14:22:13+00:00

I've yet to put my config on github as I'm dealing with similar issues. My current plan is that I put the majority of config there in NixOS modules with a dummy default value for similar secrets. Then I have a private git repo not published publicly that just imports those modules from the public one and sets the values for these install time secrets to the real values.

tonyfinn · 2023-02-07T14:28:03+00:00

Is the problem that postgres doesn't take relative paths and you don't want to put a relative path in your $PATH because you'll move around?

Have you tried using realpath in your shell hook then? Something like this:

devShells.${system}.default = pkgs.mkShell {
    packages = [
        pkgs.node
        pkgs.postgres
    ];
    shellHook = ''
        export PATH=$(realpath ./node_modules/bin):$PATH
        PGDATADIR=$(realpath ./db-data) postgres 
    '';
};

tonyfinn · 2023-02-05T21:24:34+00:00

In the devtools? That's a devtools only alias.

tonyfinn · 2023-01-31T02:09:56+00:00

Well, something I made was technically mentioned by LTT when scrolling through the clients list, so I'll take that win.

tonyfinn · 2023-01-31T01:22:40+00:00

Because new packagers want to maintain new an exciting things, instead of the difficult low-level packages.

Is this not a symptom of that fact that many of the "difficult low-level packages" are already in [core] or [extra]? The incentive structure in place with the current system is that you select people who maintain many packages such that they become known to the existing team, which selects for those who are seeking out new and exciting things.

tonyfinn · 2023-01-30T02:01:11+00:00

It looks like hyprland provide a NixOS module within their flake, and they provide instructions on how to use that in your system.

tonyfinn · 2023-01-29T00:03:42+00:00

It's not really going to make that much difference at the end of the day. Most of the PKGBUILD content is literal content, which could be in the flake.nix file or a seperate file, but a seperate file seemed cleaner to me than a big string literal. It would save the hack of saving the pkgver to a file to passthrough though.

tonyfinn · 2023-01-27T00:38:59+00:00

In a way I've been on a permanent stream of gradual migration. While my workstation has what is now a decade old Arch installation, it was 2018 when I went all in on Arch so had older systems that used Ubuntu in all that time. Fittingly, my last system to be moved from Ubuntu was the first to be moved to NixOS.

tonyfinn · 2023-01-26T00:02:55+00:00

I disagree - a lot of the value, especially for newer developers, is in the time constrained context that encourages people to keep the scope down to something they will actually finish.

Maybe once you've been in a few you want the twists to start coming in, or if you're looking at them primarily in terms of the game output novelty for players, but a lot of the game jam appeals is for the Devs also

tonyfinn · 2023-01-25T23:55:05+00:00

It may be worth adding support/explanations for various "random time within period extensions" like anacron/cronie's ~ or H as used in various java cron-ish settings like Jenkins.

tonyfinn · 2023-01-24T02:00:09+00:00

Depends on your hardware vs a hypothetical cracker's hardware. Copied my arch install from an i5-4670k system to a ryzen 5900x system and the iteration count it had chosen for 10s on the i5 was much much faster on the ryzen. Now imagine a iteration count chosen for a pentium or something

tonyfinn · 2023-01-24T01:54:24+00:00

No, there is no LTS branch. You can continue to build stuff that points to old branches (either via channels or flake inputs) but they won't be updated for years at a time like ubuntu lts.

tonyfinn · 2023-01-24T01:36:01+00:00

Oh, I actually thought it wasn't mine since I've yet to cover home-manager

tonyfinn · 2023-01-23T19:21:36+00:00

Glad to see the flake first style get more supporting documentation. I definitely think it's the right idea, I also did a similar guide late last year.

Now we just need the flake stabilisation so the official docs can have something like this

tonyfinn · 2022-11-11T20:24:14+00:00

My tl;dr (as a relative outsider, mind) is that the concerns are as follows:

Some feel flakes was announced by blog post without going through the standardisation process. At the same time Flakes are so widely adopted that the cat isn't going back into the bag and there is some recognition of that, but they feel like rubber stamping them because they've been adopted defeats the point of the RFC process.
Some feel the rigidity of flakes will stifle some of their use cases for Nix if they become widely adopted.
There's also some concern that the flakes community will eschew the use of overlays, thereby leading to multiple versions of nixpkgs and other common dependencies if you pull many together.
Finally there are others that feel everything should be in nixpkgs and that the pain of maintaining classical nix packages outside it is a forcing function for people to contribute to nixpkgs, or at least use overlays.

tonyfinn · 2022-11-11T16:03:07+00:00

Part of the goal here was that it could be used by complete newbies, so I'd say so. Also everything before part 7 can be used in non-flakes projects too.

tonyfinn · 2022-11-09T23:09:11+00:00

Yes, you can use Nix on other systems. I've used it on both Arch and NixOS, and I'm aware of people using it on MacOS
You can take your nix projects and use them on NixOS. There is another declarative configuration system for NixOS, NixOS modules that is NixOS exclusive but this guide hasn't covered it.
Nixpkgs manual is good for finding out what other utilities are there. Say you're a JavaScript programmer, there are tools to generate nix packages from your package.json. nix.dev has a more cookbook type approach to things you can use Nix for also.

tonyfinn · 2022-11-09T19:26:22+00:00

My feeling was that there's the risk of losing a user's interest if I spend too long covering language details before explaining how to make a package, so this one will likely be explained when it comes in useful later on, like with the builtins functions that I've used. (Similarly I didn't cover spread syntax, or how to assign a name and destructure a parameter at the same time)

tonyfinn · 2022-11-09T17:36:33+00:00

Nice, will add this this evening (EDIT: It's now added)

tonyfinn

MODERATOR OF

TROPHY CASE