I am currently 2/6 done with [1] this 13,2k piece Disney puzzle and this guide will be much helpful once I need to hang it as that has been bothering me a bit since the sheer proportions of the puzzle are starting to appear. That might not be soon though, as I didn't account for lack of sunlight during winter, turns out doing puzzle with artificial lightning is not easy, puzzle reflects some of it and it's strain on the eyes.

1 - https://en.clementoni.com/collections/adult-puzzle/products/...

Having correct light is crucial, be wary of the eye strain. I found that I could only productively puzzle during certain times of the day with good sunlight. Those long sessions during the night were really bad for my eye sight.

I found that a ceiling light fixture is really bad for painting as well, since wet paint reflects a lot of light. I got some powerful LED lamps [1] pointing up as an experiment and they have worked out well; I was afraid of the 6000K temperature looking too blue but I think when they are powerful enough they look really nice. The trick was to put them somewhere aside so there is no direct reflection path.

[1] https://www.amazon.com/dp/B0962X573M

I used Gentoo since about 2012 up until 2022 then switched to Debian mainly because lot less things used to break during updates and my old CPU ( i7 4790k ) became a bit dated to compile every new version of Golang, Rust and Chromium - just hours and hours of brutal grind. Since flatpak can provide up to date versions of a lot of desktop software on Debian there is very little point switching back. Maybe one day if I get my hands on some ridiculously powerful CPU like 7800 or 9800X3D then might try it again.

I just got a Ryzen AI 395+ and compilation times are insane, kernel compiles in one minute! :D https://www.phoronix.com/review/amd-ryzen-ai-max-pro-395/5

Wow! 1 min?! that is absolutely nuts! I remember having to recompile the kernel on my 386,486 etc,

> The hype for this is remarkable and people have been counting the hours since it was announced 2 weeks ago.

There was a person /u/UrsaRyan on reddit.com/r/civ doing a Sid Meier's Civilization related meme for about two years on daily basis until next (seventh?) installment in the game was released. That one flopped though, so yea, not sure what my point is, guess something about hype for a game on reddit or something and in the end it not paying off.

Yeah, I am using my Deck with 512GB sdcard and could never tell it is actually running from sdcard. It does a lot of game updates and always finishes those in reasonable time, at least for me. That card is going strong with all the writes going on on steam deck

I used this back in the days and it was awesome. Sadly after the dawn of tiling window managers this is obsolete since you will never really see it as windows always takes full screen. If anyone knows how to make it play well with i3wm or awesome wm, let me know, would gladly use this again.

Does not help you but the question nerd sniped me to try it as an exercise in my preferred tiling WM spectrwm.

https://github.com/conformal/spectrwm

This lets it act as a sort of toolbar, present on all workspaces.

in .spectrwmrc add

    #shrink the region by 112 to allow space for the widget
    region = screen[1]:2448x1440+0+0
    #add quirk to remove from normal workspaces
    quirk[Gkrellm] = WS[-1]

then start on right side of screen

    gkrellm -geometry -0+0

I normally would probably just put that in my .xsession but there is an option to auto start it with spectrwm, untested

    autorun = ws[-1]:gkrellm -geometry -0+0

Would be cool to see a screenshot

IIRC AwesomeWM has the option to define the area of the screen used for tiling. It's called workarea[0] I think. So in theory you should be able to just make the screen a bit smaller and free some screen estate for other things.

[0] https://awesomewm.org/doc/api/classes/screen.html#screen.wor...

Nothing is preventing you to add an IP whitelist and/or basic auth to same configuration. That is what I do to all my nginx configurations to be extra careful, so nothing slips by accident.

I got something similar running with nginx myself with purpose of getting access to my internal services from outside. The main idea here is that internal services are not on same machine this nginx is running on, so it will pass around to needed server in internal network. It goes like this:

  server_name ~^(?<service>(?:lubelogger|wiki|kibana|zabbix|mail|grafana|git|books|zm))\.domain\.example$;
  location / {
        resolver 127.0.0.1;
        include proxy.conf;
        proxy_set_header Authorization "";
        proxy_set_header Host $service.internal;
        proxy_set_header Origin http://$service.internal;
        proxy_redirect http://$proxy_host/ /;
        proxy_pass http://$service.internal;
  }

Basically any regex matched subdomain is extracted and resolved as $service.internal and proxy passed to it. For this to work, of course any new service has to be registered in internal DNS. Adding whitelisted IPs and basic auth is also a good idea ( which I have, just removed from example ).

I would guess it depends on your exact smb configuration, as I recall there were multiple configuration parameters for transfer speed, like

> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072

I never benchmarked these though.

I haven't run a Samba instance that has changed those options from their defaults in like twenty years.

  # grep socket /etc/samba/smb.conf
  #

I don't have any performance-tweaking options set... just auth, share definitions and server identity and protocol information. I learned long ago that for SOHO (and probably even medium-size-office) use, the performance-tweaking defaults for well-tested software like this are just fine.

Minor nitpick - shouldn't you first define the service and only then a timer for it? Otherwise since you enabled timer and are still trying to figure out how to write service, systemd won't have anything to run when timer triggers. Maybe I am wrong, but that just feels like logical order. Anyways, after years on hating on systemd I also started to embrace it and porting my cron jobs to systemd timers and I must admit it's really nice, the overall overview with list-timers, next execution timestamp, total execution time, ordering of services so one can run after another is completed and of course the logging in journal so I can filter output and keep track of everything it's just wonderful experience.

EDIT: yea, the email reporting is certainly missing, but it was hard to control it since whole STDOUT was shipped, which is not what I wanted most of the time anyways. It would be good to come up with some way to still have small overview emails sent about important jobs done, maybe a dependency service which starts when important job finished and just sends an email about that

Kubernetes admin here with ~2y experience. Since a lot of you have misconception of what this guy is doing I will try to explain. Author wrote a piece of code which will interact with network gateway to get IPv4/IPv6 network address and then update kubernetes configuration accordingly from within a container running on said cluster. That seems to be needed, because MetalLB component in use exposes kubernetes deployments in cluster via predefined IPv6 network address pool which is given from ISP, so if that changes, cluster configuration should change too. This is one of most bizarre things I have read about kubernetes this year and probably shouldn't exist outside a home testing environment, but hey, props to author for coming up with such idea.

OP here.

Thanks. If I was a company, I would probably be in control over when my IPv6 range changes. And if my ISP is any good (I just recently switched to it), my IPv6 network should stay the same.

The network range in a home setting is always given by your ISP, most likely with DHCPV6 prefix delegation, very rarely do you in a home setting dish out for a permanent IPv6 network range. Granted, most decent ISPs try to persist it, since there's no good reasons not to, and it's a strong recommendation from standardization bodies etc. But it's still just best effort, accidents happen, state get lost, and suddently you have a different network.

Sure, it's probably take me less than an hour to just change everything, but we are hackers here, so what's the fun in that? At least I gravitate towards perfecting things even beyong pure needs, just because I can. At work, I have to call it a day when it gives no more significant gain, at home I am free to think "this is fine, but can I actually do it better?". If the answer is yes, and you have the time, I'd say go for it. Some people like to watch cat videos on Youtube, I prefer to tinker with getting stuff to work. Sometimes it's useful, sometimes it's just for the fun of it.

I'm on my way to improve this, by the way. I plan to create a Unifi Networking Operator that can help me not only this, but to configure my Unifi Gateway and firewall rules through Kubernetes properties. It will be more logical to let my "dynamic IP" setup just change Kubernetes properties, and let the OPerator handling the Unifi Configuration of it.

Overkill? Hell, yes! Fun? For me, at least? Will I learn something? Yes, I will learn how to create a Kubernetes Operator!

Yeah, I'm a beginner in Kubernetes, but not in IT and sysadmining in general, I've got 30 years experience there. For now, Kubernetes is a just-for-fun project at home, but it's used to run my day-to-day home services, which makes it even more fun to improve it. We use Kubernetes where I work, but not in my area, it's not inconcieveable that my home-tinkering will be of benefit at work, some day.

And yes. I run a personal blog (in my Kubernetes cluster). I try to make it a bit educational, with more or less repeatable experiments for people to pick and chose from.

Some will be good, some will probably be a bad idea. But as long as there's learnings to be had, it's worth doing.