Test to see if Mastodon integration works with brid.gy and my website.
-
-
Replying to a
:Nice! 👍
-
I’m vaccinated. First shot. Biontech.
-
I’m having trouble keeping up with my feed reader count of unread articles. Somehow again and again I delay opening up the damn thing and just start reading.
-
Via Daring Fireball: I’m trying out Hello Weather on my iPhone now. I especially like their privacy policy:
We don’t want to know anything about you unless you contact us yourself.
-
Replying to a
:I think something’s wrong with your RSS feed, too. 🙊
-
Replying to a
:Even better! 👍
-
One of the reasons I struggle with writing notes and articles for my blog on a regular basis is the fact that I don’t know who I’m writing for. (That, and an unhealthy mix of impostor syndrome.)
Who reads my content? For which audience do or should I write? Who even cares about the things I think about? Do my ramblings make any iota of meaningful difference in the world?
This thinking isn’t helpful. It’s the opposite. I can feel how it blocks my mind.
That’s why I now try to think of it as I think of good and relevant comments in code: I try to picture myself a few months into the future and document things for my future self. I make implicit knowledge explicit, for myself, in order to be able to remember. I materialize emotions and thoughts I have every day through words I put up on my blog.
The audience is me. Anyone else interested is welcome to join me in reading.
-
For years now my go-to pattern for CSS hyphenation was always something like this:
p { /* activate hyphenation */ hyphens: auto; /* add some sensible settings (http://clagnut.com/blog/2395/) */ hyphenate-limit-chars: 6 3 3; hyphenate-limit-last: always; hyphenate-limit-lines: 2; hyphenate-limit-zone: 8%; } @media screen and (min-width: 768px) { p { /* deactivate hyphenation for larger viewports */ hyphens: none; } }
Today at work we encountered a strange bug in combination with the
none
keyword. A floated element caused the text paragraphs besides it to create weird and random text breaks. Toggling thenone
keyword on those text paragraphs caused the bug to disappear.Upon further inspection I checked out the docs for the
hyphens
property. For thenone
value the following is stated:Words are not broken at line breaks, even if characters inside the words suggest line break points. Lines will only wrap at whitespace.
This seems rather aggressive. What I actually want is what the
manual
keyword offers (which is also the default value ofhyphens
):Words are broken for line-wrapping only where characters inside the word suggest line break opportunities. […]
Adding
manual
to the text paragraphs fixed the bug. Unfortunately I don’t know what exactly caused the bug, but I guess in certain layout combinations the aggressive nature ofnone
can cause browsers to create weird text flows.Again what learned, as we like to say in Germany!
-
I just came across a job offer for a “Frontend Developer”. In it is explicitly stated that you should not apply if you’ve never touched AWS or Kubernetes. I mean: what the actual f.