š¾ Archived View for fixato.org āŗ 2020-03-25-an-uneventful-day.gmi captured on 2022-04-29 at 12:27:55. Gemini links have been rewritten to link to archived content
ā¬ ļø Previous capture (2022-03-01)
-=-=-=-=-=-=-
First published on Wednesday 25 March 2020 01:00:00 CET
Last revised on Wednesday 25 March 2020 03:36:38 CET
Having stayed up for way too long last night, and thus needing a fairly long nap during the day, I canāt say Iāve done much worth mentioning. :) Iām grateful though that my SO had the day off, and didnāt mind me doing so.
My SO made #dinner tonight. We had some leftover hotdog #sausages --- probably one of the cheapest #meat / protein sources around here --- so she fried them up with some #onions, #beans and frozen #spinach. Beans and frozen veggies (especially spinach) are things we try to keep in stock, as they are so versatile, and can help a lot to make a meal more filling and/or add some iron to it.
There was plenty left, so sheāll probably have the leftovers for lunch tomorrow before she has to go to work. :) Meals that make for easy to heat up leftovers are some of my favourites. ;)
Getting our son #BeardGrabber to sleep is a bit of a mixed bag. Some nights are very easy, while others take a lot of effort. When I put him to bed tonight, he was first struggling a lot, but eventually he drifted off in my arms in the big bed. Unfortunately, transferring him to his bed failed on the first attempt, so the second time I let him sleep for a bit more in my bed, covered by his own blanket so it would warm up a bit more. The second attempt was successful fortunately, and I managed to transfer him to his own bed without him waking up.
After dinner, and putting BeardGrabber to bed, I went outside for a bit for some #dailyExercise in the form of a walk, and finishing up my #mobileGaming #dailies. My SO had already gotten me a hack in #Ingress and a spin in #PokƩmonGO, but I also wanted to finish up a 'Calamity task' in #HarryPotterWizardsUnite.
I didnāt go far, as I didnāt want to stay out for too long, and because with a cold wind and some rain every now and then, it was a tad uncomfortable, so I basically took the same route as I walked the day before with little BeardGrabber. Put some 'mushroom seeds' in the nearby 'greenhouse' in the Harry Potter game *(need to remember to 'harvest' them tomorrow night!)*, picked up 2 new #ResearchTasks in PokĆ©mon GO *(**Catch 10 PokĆ©mon** (because I still want a shiny #Magikarp!) and **Take A Snapshot Of Your Buddy** (because itās such an easy task))*, and made a couple fields from 2 #IngressPortals that were left uncaptured or had decayed.
walked the day before with little BeardGrabber
Today was also the start of a new 'tour' in #MarioKartTour, and I was happy to see that no-one had beaten my tour score, allowing me to rake in the rewards for ranking first in the weekly tournament! I spent most of the coins rewards on a level up ticket for one of the mid-tier karts; getting closer to maxing out the 'Super Blooper' kart. :) I know itās just a silly #Free2Play mobile game with quite a bit of #Pay2Win 'luck', but I like playing a couple of races at the end of the day, and it feels good to put down a good #highscore like one from earlier this week especially while not spending a single dime.
While I havenāt done much/any #coding after waking up, I did get a bit more done in between writing yesterdayās #blog post / #journal entry and sleep. I managed to add some form of #CSS-based blurring triggered by #JavaScript / #jQuery code on sections following #ContentWarning links, and added some more styling to the blog posts themselves.
So, for now the header looks like:
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css" integrity="sha384-ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T" crossorigin="anonymous"> <link rel="stylesheet" href="https://fixato.org/media/css/housestyle.css"> <link rel="stylesheet" href="blog.css"> <script src="https://code.jquery.com/jquery-3.4.1.slim.min.js" integrity="sha256-pasqAKBDmFT4eHoN2ndd6lN370kFiGUFyTiUHWhU7k8=" crossorigin="anonymous"></script> <script async src="blog.js"></script>
With the #houseStyle for now being this bit of #CSS styling I copied from an earlier project:
html, body { background-color: #111; color: #ddd; }
.card { background-color: #222; }
.jumbotron { background-color: #112; border: 1px inset #FF1493; }
h1, h2, h3 { color: #FF7700; text-shadow: 1px 1px #666; }
a {
color : #00FF00;
}
a:visited {
color : #00FF00;
}
a:active {
color : #00FF00;
}
a:hover {
color : #3399ff;
}
and the blog-specific CSS consisting of some styles to take care of the #YAML front-matter (which shouldnāt even be visible in the actual final result, but is generated by the current #Markdown to #HTML generator I use), add support for blurring text, and add some page width/padding/margin styling:
/* Avoid page breaks inside the most common attributes, especially for exports (i.e. PDF) */
td, h1, h2, h3, h4, h5, p, ul, ol, li {
page-break-inside: avoid;
}
html {
font-size: 11pt;
font-family: "Arial", "Roboto", "Open Sans";
}
body {
max-width: 70rem;
margin: auto auto;
}
p { margin: 0.5em }
h1, h2, h3, h4, h5, h6 { margin-bottom: 0; margin-block-end: 0; font-family: "Arial Black"}
h1 + p, h2 + p, h3 + p, h4 + p, h5 + p, h6 + p { margin-top: 0.25em}
#container {
background-color: rgba(0, 0, 0, 0.4); padding: 2rem
}
/* Hide the YAML front-matter */
#container > hr { display: none; }
#container > hr + h2 {
white-space: pre-wrap;
margin-bottom: 1em;
font-size: 1.1em;
}
.blur {
text-shadow: 0 0 8px white;
color: transparent;
}
.blur, *[data-cw-hash] {
cursor: pointer;
}
Then, given the following way to hack in #ContentWarning support through links before a section:
<p>
<a href="#CW-$TYPE">CW: description of the actual content-warning</a>
</p>
<p>content here</p>
<p>more cw-affected content here</p>
<hr/><!-- end of CW section can also be another header -->
these blocks get blurred and can be toggled with the following #JavaScript code:
$( document ).ready(function() {
// Blur sections following a ContentWarning link
$('a[href^="#CW"]').each(function() {
$( this ).parent().nextUntil('hr,h1,h2,h3,h4,h5,h6').addClass('blur').attr('data-cw-hash', $( this )ā½ā°ā¾.hash);
});
// De-blur sections matching the clicked blurred ContentWarning block
$('.blur[data-cw-hash]').click(function() {
$('a[href="' + $( this ).attr('data-cw-hash') + '"]').parent().nextUntil('hr,h1,h2,h3,h4,h5,h6').toggleClass('blur');
});
// De-blur sections matching the clicked ContentWarning link
$('a[href^="#CW"]').click(function() {
$('a[href="' + $( this )ā½ā°ā¾.hash + '"]').parent().nextUntil('hr,h1,h2,h3,h4,h5,h6').toggleClass('blur');
});
});
But part of this might change when I switch to generating the HTML from Markdown with the library that #Jekyll uses, #Kramdown IIRC?, or whatever #StaticSiteGenerator I eventually decide to use.
Kodymirus on the #Fediverse suggested a LaTeX strategy in response to my earlier complaints about Markdown, which sounded interesting, but I think Iād need to experiment some with #LaTeX first before giving that a closer look. I have a feeling that typing LaTeX just will not feel as fluent to me as the current solution, but that might just be because I donāt really have experience with writing LaTeX. It does sound more powerful though, and AFAIK has been supported by writers for longer.
earlier complaints about Markdown
Worth further consideration at least. :)
FiXato from the future here: I ended up scrapping this approach when switching from #Markdown to #AsciiDoc for various reasons. Primarily because defining the blocks wasnāt as intuitive as Iād liked, and because it relied on javascript, which made it less accessible as Iād like. While I could include the native HTML5 `<details>` and `<summary>` tags in #Markdown, I donāt like tightly coupling the source text files to their output format. Fortunately #AsciiDoctor supports them through the `[%collapsible]` block, which is what Iāve opted for at time of converting these Markdown posts. Iād still like to extend the collapsible-block, but for now the basic version will suffice.
This page has been viewed 48 times up to 2021-06-07 22:09:04 and received a total of 11 ā„
(It will be added to the counter upon the next page rebuild)