Since a short time I am the proud owner of an old dial phone from the 70s. It is a “PTT 50 Tf3-39.205” from the company Zellweger Uster from 1972, which can only do the old pulse dialing.
With pulse dialing, corresponding pulses are sent for each dialed number: 1 at 1, 9 at dialed 9 etc. By timing the pulses correctly, the telephone number to be dialed is transmitted in the process.
Since this year I have an internet provider where dual stack IPv4/IPv6 is possible without DS-Lite. And after about 7 years!! after the IPv6 Launch Day on June 6th, 2012 I arrived with my home network in the IPv6 age.
The current season is known for the fact that it is a little bit colder outside and it gets colder inside the house or apartment.
Every year it is a challenge to find the right setting for the heating so that it is not too warm or too cold. It is even more difficult if there is no thermometer available đ.
Instead of buying a thermometer - or a weather station like Netatmo as a Christmas present đ, I thought I would build a small weather station myself.
In the previous blog entry [Pi-hole with DNS-over-TLS] I set up stubby for dns-over-tls on the pi-hole. I want to do the same now for DNS-over-HTTPS (DoH), but neither Stubby nor Unbound support the young protocol which answers DNS queries via HTTPS. Some browsers have now integrated DoH, but I would like to protect all DNS queries from my home network. Therefore I use the client of cloudflare written in Go: cloudflared.
Django (/ËdĘÃĻÅÉĄoĘ/ jang-goh) is a free, open source web application framework written in Python. Here you can find a tutorial from Django, if you don’t know it yet and want to try it out: https://docs.djangoproject.com/en/2.1/intro/tutorial01/. The next article is aimed at experienced Django developers.
Django and Microservices I have been using Django together with the task engine Celery for some time for asynchronous and distributed processing over several systems. Recently I am working on the topic “Microservices” and how they can be realized together with Django.
The new ACME v2 protocol for Let’s Encrypt certificates is live! Among other things, this now allows wildcard certificates to be obtained. This allows many individual certificates (such as subdomains) to be reduced to one, and no additional certificates are required for multiple subdomains.