That’s very cool. Hopefully GNOME will steal this idea one day.

That won’t do in my case 'cause I need to share multiple windows throughout the session as I switch between my terminal/IDE/browser etc.

[I’ve now edited the initial question to reflect this]

The problem is that I need to switch workspaces rapidly as part of the share: terminal → browser → IDE → browser → IDE → terminal, etc. I can’t be constantly going back and toggling which window I’m sharing.

[I’ve now edited the initial question to reflect this]

I started using it 'cause I was working with a lot of Linux nerds and they convinced me to try it out. I liked the politics of the GPL and the potential in the Free ecosystem.

25 years later I refuse to use anything else. Windows & Mac are built to take options away from you, to force you do use your hardware their way, and I hate it. My machine does exactly what I want it to, with hundreds of keyboard shortcuts and a solid UI built atop transparent subsystems. Windows ties my hands while pushing ads and AI into my eyeballs. Mac only “Just Works” if you’re using it precisely the way that want you to and exclusively with other iShit. No thanks.

As this is your first go, I’d recommend not tinkering with USE flags at all. Take the defaults, find what you don’t like, and consider tweaks later. USE flags can end up like a sort of “dependency hell”, with one package not working correctly because it expects another package to have something you’ve excluded. It’s uncommon, but frustrating when it happens. It’s best to start with the defaults.

I suppose the most important thing to have post-apocalypse is a copy of Wikipedia.

This is the typical defence for copyright. It’s also innacurate to the point of being intellectually dishonest. It ignores the reality of capitalism where legal protections only exist for people and corporations that have the money/power to get what they want.

Your Thing™ example would be cloned and sold on Amazon by a broad range of fly-by-night companies, and that’s if you’re lucky. If you’re unlucky, Amazon will clone it themselves, obfuscate your product in its search results, and sell your product under their brand, sometimes even for more than you’re selling it.

If your Thing™ isnt a physical product but rather something creative, then 99 times out of 100, there are only really two paths available to you:

In the lucky case you sell your copyright to a third party that exploits it (and you), offering you a pittance while simultaneously tying your hands, preventing you from creating derivative works or even just giving it away… for the res t of your life, and that of your kids’. In the unlucky case, you can’t afford to promote your product, so you toil for years with little to no reward for your work. Then AI techbros scrape your art and sell it back to you exclusively for their profit.

Copyright has some great marketing, but it offers you little while the rich claim ownership over your art, and our society.

Those rights are yours. They’re only denied to you because of copyright and capitalism.

How would you reset the timer whenever input is detected though?

I’ve had a really hard time figuring out how to get cloud native pg working 'cause I couldn’t get longhorn working for disk space.

So instead I went with a separate Raspberry Pi that isn’t part of the cluster to host a single Postgres instance.

It’s inelegant, but has worked for years. Still, I’d rather host a separate pg instance for each project… I just have to figure the above out first.

#Solarpunk!

I have Arch on my desktop, and all my laptops, but all of my servers run Debian. If you want your machine to have all the latest stuff, then Arch is great. If you want it to Just Work™ all the time without any concerns, Debian is great.

Cool stuff! For future projects, you might want to check out Typer, as it’d save you a bunch of the boilerplate and supports things like tab completion too.

Don’t do it. AI makes you stupid, and using it for school is counterproductive.

My girlfriend’s dad had hundreds of movies on VHS, pirated from cassettes he’d rented in the past and copied at home by chaining two VCRs together over coaxial cable.

Software was wild pre-internet. My buddy had Windows 95 on 42 3¼" floppies that we copied onto additional sets of 42 floppies that we kept in heavy boxes and then painstakingly installed onto computers belonging to friends and family around the neighbourhood.

I also had a whole bunch of audio cassettes that contained music I dubbed from radio, other cassettes, and later CDs (burning your own was at first, impossible, and later, expensive).

I’m 46.

I’ve used FluxCD in the past and have looked into ArgoCD, but honestly, I’ve not seen any big benefit from either to be honest. I use k8s both at home and at work, and in both cases, we do “imperative” deploys: you run helm install ... either directly or via the CI and stuff is deployed.

So for example at my last job, our GitLab CI just had a section triggered exclusively for merges into master that ran helm install ... for all three environments. We had three values.yaml files, one for each environment, and when we wanted to deploy a new version, the process was:

1. Create a tag for our release version (ie. 1.2.3) and push it to the repo. This would trigger a build and push the resulting image into the container registry.
2. Push an update to the repo with the new tag set in the appropriate Helm values file. If we wanted to deploy 1.2.3 to development but not yet to staging or production, then the tag: value in each of the environment files would look like this:

• k8s/chart/environments/development.yaml: tag: 1.2.3
• k8s/chart/environments/staging.yaml: tag: 1.2.2
• k8s/chart/environments/production.yaml: tag: 1.2.2

Once that change is pushed, the CI will automatically apply it with helm install ... and make sure that all three environments are what they’re supposed to be.

As for dependent services, that should all be in your Helm chart so they’re stood up and torn down together. The specific case you mention about “Service A” being dependent on “Service B” but stood up before “Service B” is ready is a classic problem, but easily solved:

The dependent service (“A” in this case) should have an entrypoint that checks for everything else before starting. Here’s what I’m using right now in a project:

#!/bin/sh

while ! nc -z "${POSTGRES_HOST}" 5432; do
  echo "Waiting for postgres..."
  sleep 0.1
done
echo "PostgreSQL started"

touch /tmp/ready

exec "$@"

I’ve even got some code that checks that all the Django migrations have run first for the same situation. The Kubernetes philosophy is that any container should be able to die at any time and be eventually be brought back up and that every container needs to be prepared for this. Typically this means that your containers should operate on the basis of “if I can’t work, die, and hope the problem is solved by the time Kubernetes redeploys me”.

Kubernetes. For a homelab, the stripped-down k3s is fantastic and surprisingly easy to get going.

Once you’ve got Kubernetes set up, you can lean on all the many tools already out there for things like deploying complex projects (Helm) and monitoring (Prometheus/Grafana). OpenLens is a nice piece of software you can use to monitor and control your cluster too, as is k9s.

I’ll just leave this here.

I’ve had Gentoo (and later, Arch) on my Surface Pro 3 for a decade. It’s fully supported, touch screen and all.

As this is a new project, have you considered hosting your code somewhere other than GitHub? Codeberg and GitLab are similarly user-friendly platforms without the many downsides of supporting Microsoft.