#dev 2024-07-16
2024-07-16 UTC
barnaby, thegreekgeek, thegreekgeek_, [snarfed], solislupus[d], Zegnat, oenone, gRegor, gRegorLove_, GuestZero, gRegorLove__, [Murray], Star, benji, Zic, GuestZero_, [contact898], [KevinMarks], eitilt, eitilt1, [pfefferle], StarrWulfe, [Joe_Crawford], joshproehl and [jacky] joined the channel
# 
[jacky] call to action for anyone wanting to do something _bold_: https://mastodon.social/@sarahjamielewis/112797152700861866
GuestZero joined the channel
gRegorLove_, Zic, [schmarty], jonnybarnes, wagle and StarrWul1 joined the channel
# 
timeissuspect I'm getting increasingly disturbed by the accepted wisdom that a blog is a time sequenced object, and your latest content is at the top.
# timeissuspect A lot of my posts on money have got nothing to do with today's date, and the order in which I created them is certainly not the order to read them in.
# timeissuspect The thing that will break is articles where I have cross linked to those scheduled posts, those links will break until the series is fully published again
# IWDiscord <timeissuspect>
# timeissuspect So I'm going to experiment with taking a selection, putting a future scheduled date (one post per day) and release a series on one topic. That means my RSS subsribers will get something each day that connects to the previous day, as will visitors to the website.
# IWDiscord <timeissuspect>
# IWDiscord <timeissuspect>
# timeissuspect This is "recycling content" which might be frowned upon in purist circles
eitilt and [aciccarello] joined the channel
# 
[aciccarello] I think it is fair to question the date based timeline model if your content doesn't fit that well
# [aciccarello] Humans do have a recency bias though.
Jah joined the channel
# timeissuspect that's true, but I don't put dates on my blog posts anyway. It may be that someone read an article I created three months ago and sees it again in their feed and feels aggrieved. I don't have that many subscribers anyway and most readers will not have read the back catalogue.
# timeissuspect I'll give it a go and see what happens. Republishing old content within a current context is much easier that trying to think of something new to write.
# IWDiscord <timeissuspect>
# [Joe_Crawford] A lot of the time bias was about how the earliest blogging tools worked and how things got divided up as time passed. Archive pages of lots of posts with full content (or just an excerpt), often by month, or individual pages. URL structure seems like this small decision but has big implications for how one expects to use a site.
# 
artlung For me the only way to manage that stuff across time is to put the content and the dependency (the script and styles, usually, but also images or other assets) as close to the content as possible. Sometimes like a txt or json file that mentions it. So my-article.html is right next to my-article.figure-1.gif and my-article.js are all in the same folder.
# [Joe_Crawford] For the headers in my site when I switched to keeping *every* bit of CSS and JavaScript inline in the HTML of each header because I don't have confidence in creating a system that will be future-proof.
[Otto_Rask] joined the channel
# [Otto_Rask] timeissuspect i've been thinking of building my site through blog-ish updates that feed into a more "static" personal wiki-like thing, i.e. the small constant updates are interlinked with static pages/categories with which i can beef the page contents and get inspired to write other things in there as well
# [Otto_Rask] kind of how wikis often show a "latest changes" feed, but I make the feed happen first and then decide what parts of the "wiki" are affected
# [Otto_Rask] and that allows me to fire off blog posts that never have to relate to the wikilike areas of the site
# [Otto_Rask] (this all is of course very fuzzy in my head still, no decision made on any specifics)
[morganm], gRegor and [Ros] joined the channel
# 
Loqi 🌱🪴 A digital garden is a particular practice of creating & growing an online and public IndieWeb presence that focuses more on topics & relationships than a timeline like blogs, has content of different levels of development, is imperfect and often a playground for experimentation, learning, revising, iteration, and growth for diverse content, perhaps interlinked with other digital gardens https://indieweb.org/digital_garden
[qubyte] joined the channel
# 
capjamesg[d] nsmsn[d] What does the browser do by default?
# capjamesg[d] Nothing?
# capjamesg[d] I wonder why my browser doesn't show any red links for my site. Maybe because I have styled a and it applies as default to everything?
# capjamesg[d] I set a
{ color: royalblue }# capjamesg[d] I see!
# capjamesg[d] gRegor I didn't realise that `a
{ color: var(--primary-color); }` implicitly set it to all pseudo-classes too.# capjamesg[d] gRegor+
# capjamesg[d] gRegor__
# capjamesg[d] Ahhh
# capjamesg[d] gRegor++
# capjamesg[d] (Pro tip: don't type at an angle)
# capjamesg[d] This is fascinating!
# IWDiscord <nsmsn>
# IWDiscord <nsmsn>
sebsel and thegreekgeek joined the channel
# 
[Murray] huh so this is an interesting discussion 🤔 I hadn't realised using an `a
{...}` rule would impact pseudo classes, because they should have higher specificity. I guess the browser stylesheet is weighted below any reference stylesheets (and those below inline), but I'm still surprised this cascades like this. Feels wrong...eitilt joined the channel
GWG joined the channel
# capjamesg[d] Zegnat and to target a class should I say a.xyz
{}? And an attribute as a[data-xyz=true] {}barnaby joined the channel
superkuh joined the channel
Zic joined the channel