#dev 2022-08-16

2022-08-16 UTC
#
[tantek]
it's an excellent poster child for sometimes worse-is-worse.
#
[tantek]
also for, this is what happens when you abandon the "key design goal" in the interests of expediency for your particular use-case
#
[tantek]
[schmarty] on a positive note, I'm definitely curious what subset of "some markdown" you "use the heck out of"
#
[schmarty]
headings and lists and em/strong/code and code blocks. occasionally images.
jacky joined the channel
#
[tantek]
how many levels (to what depth) of headings have you found yourself using in practice?
#
[schmarty]
i am like a local minimum finder for just enough syntax to add emphasis or clarify ambiguity 😂
#
jacky
heh I noticed that at best, I go down to like h4
#
jacky
mainly on my work page
#
[schmarty]
i try to keep things to the ol' standard of one h1 per page and try not to nest more deeply than an h3.
#
jacky
I use a lot of the HTML5 tags and IIRC they suggest adjusting levels as things like <section>, <article> etc get deeprr
lagash joined the channel
#
[schmarty]
jacky: implied / reset heading levels in nested sections/articles has (finally) been removed from the HTML spec because browsers never implemented it 😅
#
[tantek]
!tell snarfed is there a corollary or "future" to "manual until it hurts" where what do you do when the automation breaks and becomes unmaintained / unmaintainable? I feel there's more to the story of "manual until it hurts" (perhaps not enough for a flow chart, yet). example, what happened to: w3.org/Terms
#
Loqi
Ok, I'll tell them that when I see them next
gRegor joined the channel
#
jacky
lol see then I have the doubled benefit of it being easy to style and shrink
#
[tantek]
jacky, the relative headings based on <section> & <article> never gained any serious adoption.
#
[tantek]
even <section> and <article> have likely caused more authoring headache than benefit for users
#
[tantek]
jacky, [schmarty] yeah, depth 4 is about the most for me in practice too. Good, I didn't bother designing beyond depth level 4 for an actual human readable (without wondering, what's this gibberish) plain text expression of headings
jacky joined the channel
jacky, pmlnr, jacky_, alex11, geoffo and AramZS joined the channel
#
GWG
My current project is a pain. Doing refactoring and cleanup on messy code and adding new unit tests.
#
GWG
I'm afraid I'm making it messier
jacky, jonnybarnes, geoffo, gxt, gRegorLove_, gRegor, [marksuth], tetov-irc and bterry joined the channel
#
@MeritzPress
Where a flower blooms tonight, Devout and purple, With a rift for a hollow power, That shivers it springs from a root - from Pluck At The Offering, Barbarity. Free excerpts. Order at http://amzn.to/2CF8fts or kindle http://amzn.to/2CV3tw4 #literature #writer #indieauth
(twitter.com/_/status/1559514068091805698)
jacky, abetusk, AramZS, jonnybarnes and [snarfed] joined the channel
#
[snarfed]
capjamesg: I'd want someone else to _drive_ a new Indie Map crawl, not just help...so it's up to them, not me, if it happens!
#
Loqi
[snarfed]: [tantek] left you a message 13 hours, 59 minutes ago: is there a corollary or "future" to "manual until it hurts" where what do you do when the automation breaks and becomes unmaintained / unmaintainable? I feel there's more to the story of "manual until it hurts" (perhaps not enough for a flow chart, yet). example, what happened to: w3.org/Terms
#
[snarfed]
and thanks re hackermention! my initial idea would have been really small and simple, but Firebase doesn't support it đŸ˜ĸ https://stackoverflow.com/a/73355286/186123 , so I'm doing it the more traditional way, ah well
#
[snarfed]
[tantek] maybe!
#
capjamesg
Ah, I thought I was in #chat.
#
capjamesg
Let's discuss there.
chenghiz_, jonnybarnes, jacky, thehedgeh0gtheyt, [KevinMarks] and bterry joined the channel
#
@kevinmarks
↩ī¸ #ToolsForThinking @jerrymichalski: How can we make a social memory so everyone can use their favourite tool, but connect between them? [km webmention!]
(twitter.com/_/status/1559574905162764289)
[Jamie_Tanna], jacky, geoffo, tbbrown, AramZS, jonnybarnes, [fluffy] and tommorris joined the channel
#
@_swiftp
↩ī¸ no but really for tools I've been curious about Astro for development and Webmentions for a comment system https://astro.build/ https://indieweb.org/Webmention
(twitter.com/_/status/1559619386268389377)
jacky, [campegg], [snarfed], geoffo, AramZS, tbbrown, tetov-irc, bterry and nertzy joined the channel