This has started happening a while ago (previously there was not perceptible delay) and luckily I don't have to visit HTTP sites very often but it is annoying and I would like to get rid of it.

I know HTTP is bad TYVM. I only use this HTTPS-only mode to forcibly upgrade to HTTPS whenever possible and be notified if it doesn't work.

Does anyone know why this is happening and how to disable it?

#Firefox @firefox@lemmy.world

cross-posted from: https://lemmy.ml/post/7171132

Oh, und wie krieg ich die Daten aus dem IT-Dinosaurier meiner Sparkasse in dieses System ohne den Verstand zu verlieren?

Update for the post two weeks ago: https://lemmy.ml/post/5814564

They've reverted the attempted license change and made it crystal clear that the entire project is under the AGPL now.

Im Moment gibt es so um die 4% p.a. Zinsen auf Festgeld, was bei durchschnittlicher Inflation bei der hohen Sicherheit langfristig eine sehr rentable Anlage wäre.
Nun sind die Zinsen grade ja nur so hoch, weil die Inflation auch riesig hoch ist. Voraussichtlich ändert sich das aber relativ bald (EZB geht von Rückkehr zu ca. 2% in ein zwei Jahren aus).

Wäre es da nicht mega sinnvoll Festgeld sehr lang (3-5J) zum jetzigen Zinssatz anzulegen? Selbst bei ein paar tausend Anlagevolumen würden da mehrere Hundert p.a. bei raus springen und dazu noch sicher.

Überseh ich da was?

Klar, im Moment bekommt man fast so viel (oder mehr) auf Tagesgeld, aber die Tagesgeldzinsen können ja genauso schnell runter gehen, wie sie gestiegen sind; Festgeldzinsen bleiben über den vereinbarten Zeitraum gleich.

Momentan habe ich in meinem Portfolio fast ausschließlich Aktienkapital, weil mir die hohen Drawdowns in meiner momentanen Lage noch egal sein können. Ein wenig Sicherheit wär aber schon nicht schlecht und da äugel ich jetzt Festgeld auf 5 Jahre zu 3.9% zu machen.

cross-posted from: https://lemmy.ml/post/6538892

BattlEye Innovations e.K.

Die "e.K." Rechtsform ist "Eingetragener Kaufmann".

cross-posted from: https://lemmy.ml/post/5142305

From: Ben Skeggs

This series adds support for loading and running on top of NVIDIA's GSP-RM firmware, instead of directly programming large portions of the hardware ourselves.

The implementation is a little crude in places, but the goal of this series is to get (more-or-less) GSP-RM support on par with what we already support on HW. Next steps would be to look at what features GSP-RM enables us to more fully support, and clean up the GSP-RM integration once it's known what those will require.

Things should be somewhat faster when running on GSP-RM, as it's able to control GPU clocks, which wasn't possible for us previously.

SVM support is not available when running on top of GSP-RM at this point, due to GPU fault buffers not being implemented yet. This won't effect any real use-case, as SVM is experimental at best in nouveau anyway.

Aside from that, things should more or less work as normal.

GSP-RM support is disabled by default for now (except on Ada, where it's the only option) and can be enabled with nouveau.config=NvGspRm=1.

There'll likely be some nit-picky bugs to sort through, but I don't anticipate any huge disasters. I've smoke-tested this on a selection of GPUs right back to nv50, testing both HW and GSP paths depending on the GPU, and more thoroughly tested on Turing/Ampere/Ada, both discrete and laptop GPUs.

Firmware from NVIDIA is required to enable this support.

From: Ben Skeggs

This series adds support for loading and running on top of NVIDIA's GSP-RM firmware, instead of directly programming large portions of the hardware ourselves.

The implementation is a little crude in places, but the goal of this series is to get (more-or-less) GSP-RM support on par with what we already support on HW. Next steps would be to look at what features GSP-RM enables us to more fully support, and clean up the GSP-RM integration once it's known what those will require.

Things should be somewhat faster when running on GSP-RM, as it's able to control GPU clocks, which wasn't possible for us previously.

SVM support is not available when running on top of GSP-RM at this point, due to GPU fault buffers not being implemented yet. This won't effect any real use-case, as SVM is experimental at best in nouveau anyway.

Aside from that, things should more or less work as normal.

GSP-RM support is disabled by default for now (except on Ada, where it's the only option) and can be enabled with nouveau.config=NvGspRm=1.

There'll likely be some nit-picky bugs to sort through, but I don't anticipate any huge disasters. I've smoke-tested this on a selection of GPUs right back to nv50, testing both HW and GSP paths depending on the GPU, and more thoroughly tested on Turing/Ampere/Ada, both discrete and laptop GPUs.

Firmware from NVIDIA is required to enable this support.