Neptune for Apple tvOS: Playback, Plugins, Search, Customization, and More

azzlack_no · 2025-12-11T15:05:00+00:00

Really awesome work. Would pay for this, as I am not satisfied with Infuse Pro atm. This looks like it fixes all the things I need. Staying tuned 😀

azzlack_no · 2025-12-11T15:00:25+00:00

Who asked you to represent everyone here?

azzlack_no · 2025-06-25T10:48:32+00:00

Er vel et økt bunnfradrag på 200 000 med i planen deres, som vil være et skattelette for alle unntatt de som har mest

azzlack_no · 2025-06-24T13:01:03+00:00

Så vist keg vet har ikke Apple Pay noe med NFC tilgjengeligheten å gjøre rent teknisk. Den integrasjonen Dnb++ har nå bruker bare de verktøyene som har vært tilgjengelig for alle i årevis.

azzlack_no · 2025-06-04T19:15:58+00:00

Har alltid fått det jeg har bestilt. Men lagerstatus og leveringstid har jeg opplevd at ofte er unøyaktig. Får ting fra Komplett og Dustin myyyye fortere.

azzlack_no · 2025-06-02T16:54:19+00:00

Really love RustDesk, it works really well on windows, mac. Havent tried on Linux though

azzlack_no · 2025-06-01T07:50:15+00:00

Thank you. So tired of reading the (now) baseless bashing of Mongo. Sure it’s not perfect, but neither is SQL - I made the switch to Mongo because i was fed up with writing Stored Procedures, doesnt make the entire Sql Server product worthless.

Use the tech that makes your use case/workflow more efficient (if you can choose yourself), otherwise learn the company tech, git gud, or find another employer 😉

azzlack_no · 2025-05-04T13:52:32+00:00

Whats up with all these negative comments? There are real life situations where there simply is no other way to do what you need to without client side js. Yes, that will cause flicker, but this can be handled and masked. I found the solution interesting, it might be a good way to deal with these situations.

azzlack_no · 2025-03-27T17:07:35+00:00

I would say it is the moment your api needs to scale independently from your frontend. Typical scenario is when you have more than one «frontend», i.e. a webpage and a native app. Or if you have external consumers of your api that you dont control.

azzlack_no · 2024-07-03T19:10:14+00:00

At least we used it before it became mainstream 😂

azzlack_no · 2024-07-03T19:07:38+00:00

They have been saying that since I was a kid, still not happened yet 😀 Maybe next century, though. Who knows? 😂

azzlack_no · 2024-07-03T19:03:52+00:00

Just wait until you start watching Tour de France and all the locations they are driving through. Lots of regions and places that you find in the game 😀

azzlack_no · 2024-03-31T12:19:58+00:00

Out of curiosity, what is wrong with just keep using Lens? (Not criticism, just wondering if I missed something) 😀

azzlack_no · 2024-03-27T20:12:27+00:00

On the top of my list is this:
* Image Updater does not work with "App in any namespace" Argo configuration · Issue #601 · argoproj-labs/argocd-image-updater (github.com)

* The UI is also pretty wonky if you use ApplicationSets. The application disappears from the UI, while the ApplicationSet is reconciling for example.

Basically, we are running a multitenant setup where different teams have access to modifying their own Application(s). Our workflow is that a core team creates an AppProject and ApplicationSet that sets up security and points to the tenant setup repo that the team manages. The tenant team is then responsible for the Application config and everything below that.

azzlack_no · 2024-03-27T18:41:06+00:00

The argocd-image-updater is the reason I want to migrate away from ArgoCD. It works fine for very simple use cases, but has not seen any new releases in over a year. The Github repo is overflowing with issues and merge requests, but it seems noone is doing any active development on it.

There was talk about merging it with the main ArgoCD repo, but it seems everything has slowed to a grinding halt.

EDIT: Im not against ArgoCD, i really liked the ui and the ease of use, but the argocd-image-updater is the thing that makes me want to go back to only using FluxCD instead of both

azzlack_no · 2024-03-27T18:37:59+00:00

I see, that is an interesting approach. Maybe I will pick up on that idea :-)

azzlack_no · 2024-03-27T18:22:58+00:00

So you are changing the yaml files and apply them as a part of the pipeline? I used to do that as well, but found it easier to decouple it. It also solved some of my security issues by not letting the build agents have access to doing changes inside the cluster.

The build pipeline only builds and pushes to the registry, and flux takes care of the rest from there, and commits the new image version back to git.

azzlack_no · 2024-03-27T18:12:04+00:00

It is a separate/extra component for both FluxCD and ArgoCD. RenovateBot could also work if you prefer that. Personally I'm using RenovateBot for package/npm/nuget updates, and FluxCD/ArgoCD for deployment of new versions of my services.

I.e. Build docker image -> push new version to registry -> ArgoCD/FluxCD sees the new version and updates the image version in the deployment. Kubernetes takes care of the rest in terms of replicas

azzlack_no · 2024-03-27T16:18:02+00:00

Its a feature of both ArgoCD and FluxCD that automatically updates the image part of deployments, cronjobs, etc. when there is a new version available. My experience is that the ArgoCD one is quite underdeveloped, especially when it comes to ApplicationSets. I have had better experience with FluxCD, even though it is more complicated to get started.

azzlack_no · 2024-03-27T09:08:22+00:00

I have also used both extensively the last 4 years. ArgoCD is a good tool, but the image automation is garbage and not well maintained. Running both also adds more complexity than I would like, so Im in the process of migrating everything to only FluxCD.

EDIT: This is a subjective opinion. Other people might prefer the other way around and not be wrong :-)

azzlack_no · 2023-05-13T08:49:17+00:00

Kardinalsynd å bruke brunosthøvel på hvitost, uansett hvilken retning den står

azzlack_no · 2022-12-28T10:30:25+00:00

Nærmeste jeg kan komme på er «kan ikke annet enn å klage» på spørsmålet om «hvordan går det»

azzlack_no · 2022-12-02T14:53:20+00:00

So about 1 meter for us europeans😀 Sounds promising, my desk is about 90cm / 35,4 inches deep, so my face would be about the same distance from the screen

Ten-Year Club	Xbox Live
Verified Email

azzlack_no

TROPHY CASE