Telekom Heimanschluss gekündigt

Ich habe heute meinen Telekom Heimanschluss in Deutschland gekündigt.
45€ im Monat für 100/40 Mbit/s.

Der Grund ist, ich habe eine DSL Vergleich Seite und alle außer Telekom Affiliate haben kein Problem mit der Seite, nur Telekom Affiliate lehnt ständig die Partnerschaft ab.

Website ergänzt nicht die Marke des Advertisers.
URL ist für die Advertiser-Marke nicht relevant.
und noch so ein Pseudobullshitgewäsch.
Hätte ich einen Deutschen Namen hätten sie mich nicht abgelehnt.

Mehrere Anfragen nach den Gründen blieben unbeantwortet.

Daraus ziehe ich die Konsequenz und kündige meinen Telekom Vertrag.
Ich sehe nicht ein an jemand Geld zu zahlen der mich nicht als Partner haben will.

Watch out! It’s the Angular Thought Police!

So, yesterday I was visiting Angular’s discord server, because after a little over a month with Vue I was missing Angular’s components and way to express event listeners and 2-way binding of variables as well as the class based approach.
Vue2 is a simple, super productive framework, especially with Quasar, with a rich ecosystem and excellent libraries like vuex-orm, which is really fantastic, mind blowing.
It’s not perfect, nothing in this world is. The same way that Angular isn’t perfect or React or Svelte.
The worst part of Angular is the forced rxjs, if you’re doing anything more complex than a Hello World application anyway.
Continue reading “Watch out! It’s the Angular Thought Police!”

Keycloak-js client with Quasar (now updated for v2)

So you’d like to use openid-connect (oidc), especially keycloak (kc) in your Quasar app.

There’s a package, @dsb-norge/vue-keycloak-js . I’d recommend you fork it and create your own version with the keycloak-js version that matches your Keycloak server. However it also works with just the version used in this git repository.

The git repository is available at
https://github.com/dsb-norge/vue-keycloak-js

This is for Quasar v1

Alright let’s get started.

1. Create a file named silent-check-sso.html with the following content:

Put that file in the public directory as its path is
public/silent-check-sso.html.

2. Create boot/keycloak.js

3. Reference the created boot file in quasar.conf.js

And that’s really all there is to it.

After this is done you can access the keycloak object via $keycloak in your template.

This is for Qusasar v2:

Thanks a bunch to Excel1 and yusufkandemir for figuring it out.

First you have to upgrade or use the v2 branch of @dsb-norge/vue-keycloak-js.
e.g. npm i @dsb-norge/vue-keycloak-js@2
or use your own fork

But essentially you do whatever you would do for v1 only the boot/keycloak.js file is different

The boot/keycloak.js file

and of course don’t forget to add it to the boot array in quasar.conf.js