957 karma · joined July 2, 2015
Portfolio + Contact: https://woblick.dev
[ my public key: https://keybase.io/kovah; my proof: https://keybase.io/kovah/sigs/-sBuEO0prQsZmSl1dsb0UsKiGsJS7IhSyEpVcgVL3OA ]
Edit: added a link to the features page.
You have like 50 sources in your RSS reader, 300 people you follow on social media sites and like a dozen of other possible sources for interesting content. But what I noticed: once you add a new source to your feed, chances are high that a) it doesn't really fit your interests and becomes noise, or b) it becomes a "famous" source and quality of the content stagnates over time as more and more low-quality content gets pushed into it.
Personally, I don't see any chance that this will be solved in the near future, because the current state of the web with walled gardens, propietary content formats and the unbelievable push for monetarization of content leads to more and more problems.
[1]: https://fragdenstaat.de/anfrage/kostenaufstellung-der-corona...
Hard to predict which path they choose, but I try to stay positive and assume that they have at least one manager capable of thinking rational and in favor of the pro users.
"This will implicitly tell the browser to load the CSS file in a non-blocking fashion, applying the styles only to the print context. However, the moment the file arrives, we tell the browser to apply it to all contexts, thus styling the rest of the page."
The browser ignores the file because it's just for print and can be loaded later on. But when the page is fully loaded (onload="..."), the media property is set to "all" and does not stay at "print". When this happens, the browser now knows it should load it as soon as possible and does so.
As you mentioned: if JS is disabled, the file will never load. The author states that his solution is not 100% perfect: "[Async webfonts] should always be considered an enhancement anyway, so we need to be able to cope without them; we can and should design decent fallbacks for use during their absence, and;"
I think the point is: the contributions of some companies to few, very large projects are about the same as the thousands of 1-dollar-contributions private people do to the remaining 99.9% of open source software.
Depending on your actual API structure you may be able to generate a complete specification without ever touching any yaml. Been using it for the LinkAce API docs and it helped me a lot: https://stoplight.io/p/docs/gh/kovah/linkace-api-docs
Main topics are web development in general, Docker, PHP and other tech stuff. I do not post regularly but try to write a new article every now and then.
Most of the articles are about very specific problems, like mirroring private repositories to Gitea or how to setup DNSsec with Cloudflare and INWX. Currently writing a guide on how to install YouTrack on Synology Diskstations.