#meta 2024-01-26

2024-01-26 UTC
tnbd joined the channel
#
lifeofpablo.com edited /Planning (+18) "/* San Francisco */" (view diff)
#
lifeofpablo.com edited /Planning (+498) "/* Sacramento, CA */" (view diff)
[lifeofpablo] joined the channel
#
[lifeofpablo] I'm still looking for a Co-Organizer for Sacramento!
to2ds and barnaby joined the channel
#
tantek.com edited /Webmention (+31) "/* mention-tech */ link to new mention.tech domain, update feature description" (view diff)
#
tantek.com edited /mention-tech (+58) "link to mention.tech, formerly appspot" (view diff)
[0x3b0b] joined the channel
#
Loqi Just generated the first draft of this week's newsletter! https://indieweb.org/this-week/2024-01-26.html I'll generate a draft again tomorrow, so please add to it before then! https://indieweb.org/this-week#How_to
#
tantek.com edited /Bridgy_Fed (+3804) "start a Troubleshooting section with Activity not showing up in dashboard section of steps to take to debug" (view diff)
#
[tantek] !tell capjamesg[d] could you upload the photo from this week's HWC London/Europe? https://events.indieweb.org/2024/01/homebrew-website-club-europe-london-CHTpRRsewGQj Thank you!
#
Loqi Ok, I'll tell them that when I see them next
#
[tantek] lol the /test page is one of the most edited for this week. guess we better get busy with more edits
#
aaronpk oh dear
#
aaronpk wiki upgrade week
#
[tantek] ah drat, we lost the "max-width:100%" style rule for wiki images in the theme / MediaWiki update
#
[tantek] e.g. see /NYT - those images used to auto-fit to their container, and now they overflow 😕
#
aaronpk was that a custom css rule?
#
aaronpk i don't see it on https://indieweb.org/MediaWiki_customizations
#
[tantek] yeah it was a custom CSS rule
#
[tantek] found it
#
[tantek] https://indieweb.org/MediaWiki:Common.css
#
[tantek] that file is linked from /MediaWiki_customizations since it would be a DRY violating tax to keep such custom CSS rules listed in two places
#
[tantek] this rule: .image img { max-width:100%; height:auto }
#
aaronpk that looks like the actual live css for the site, so i guess the HTML changed and that rule no longer applies
#
tantek.com edited /MediaWiki:Common.css (+14) "new class in skin update for wiki file embedded images" (view diff)
#
aaronpk there's no "image" class anymore https://media.aaronpk.com/2024/01/25200317-1456.png
#
[tantek] and looks like I fixed it
#
[tantek] that should be sufficiently surgical until the next wiki update
#
aaronpk nice
#
tantek.com edited /MediaWiki_customizations (+780) "/* editable customizations */ add docs for image fitting, and how to fix if it breaks" (view diff)
#
[tantek] and left (hopefully somewhat discoverable) notes behind in case it breaks again and someone else is wondering what happened
#
tantek.com edited /MediaWiki_customizations (+160) "/* CSS customization docs */ documentation in heading" (view diff)
#
tantek.com edited /New_York_Times (+68) "purchased Wordle, incorporate See Alsos" (view diff)
#
[tantek] now if you search the MediaWiki customizations page for css or max-width you will find the docs
#
aaronpk tantek++
#
Loqi tantek has 21 karma in this channel over the last year (101 in all channels)
#
aaronpk i'm surprised that isn't a default css rule in mediawiki, how do people expect to be able to embed images normally?
#
tantek.com edited /Wordle (+655) "copy edit dfn, summarize IndieWeb relevance, separate game play into its own paragraph, sharing, Why post subsection, How to post subsection, btrem subsection, History, Acquisition motivating IndieWeb posting" (view diff)
#
[tantek] aaronpk from the MediaWiki docs I have read, they expect you to set fixed sizes for the widths etc. depending on the context that you will be embedding the image. since that's extra work, I figured I'd make the simpler image embedding default code "just work" reasonably
#
[tantek] !tell btrem can you review my edits to /Wordle since you created the page originally? Feel free to edit further to improve!
#
Loqi Ok, I'll tell them that when I see them next
#
aaronpk Makes sense
#
[tantek] also my guess is this is a "modern" problem with uploading of much higher resolution photos than people used to in the past
#
tantek.com edited /Bridgy_Fed (+0) "/* Verify Webmention is received by Bridgy Fed */ fix link ]" (view diff)
#
tantek.com edited /Bridgy_Fed (+216) "/* History */ fix date per original permalink, link masto tech archive page, note original masto. tech and hubzilla servers are offline" (view diff)
#
[tantek] well that ought to bump that page up into the Newsletter
#
aaronpk True, 640px ought to be enough for anyone right?
strugee-, gRegor, [jeremycherfas], [manton], [pfefferle], IWSlackGateway, [campegg]1, [tantek], [KevinMarks] and tnbd joined the channel
#
[KevinMarks] There is some trickiness for wider viewports where you want the text to wrap at a sensible line length but sometimes want images to be able to be wider than that - Tufte CSS has some variations for that.
omz13, tnbd, Guest6 and [Joe_Crawford] joined the channel
#
tilde.team ~zinricky edited /indieweb-carnival (+75) "Added my word on hosting the Carnival in Oct ’24" (view diff)
[Murray] and [tantek] joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
[tantek] Need a few more pages with 4+ edits to bump "test" off the list!
[Paul_Robert_Ll] joined the channel
#
[Paul_Robert_Ll] Cue https://indieweb.org/2024/homepage – any thoughts on this change and then switching the default theme?
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
capjamesg[d] [tantek] Added the photo!
#
capjamesg[d] [Paul_Robert_Ll] I love your design.
#
capjamesg[d] It (might) be a question for aaronpk on how to get it live on the wiki.
#
capjamesg[d] Your design feels like a _substantial_ improvement over what we have right now.
#
[tantek] capjamesg[d] you just missed the newsletter regen. wait 23 minutes, it
#
[tantek] ... will show up
#
capjamesg[d] 😄
#
capjamesg[d] I'm not done with today's meetings.
#
capjamesg[d] Four down, one to go.
#
[tantek] oof, may they go quickly & smoothly
#
capjamesg[d] Next one: Show and tell.
#
capjamesg[d] It is impossible to argue that one isn't fun 😄
#
capjamesg[d] (We show what we made at work, not random things, to be clear :D)
#
[tantek] [Paul_Robert_Ll] I'd suggest people try switching their Preferred theme to Vector (2022) for a bit (days? a week?) and see how it feels once you get used to it. FYI folks can do this by going to https://indieweb.org/Special:Preferences#mw-prefsection-rendering and choosing (•) Vector (2022)
#
capjamesg[d] [tantek] That feels counterproductive for this change that addresses a page that has been in need of change -- as recognized by the community -- for years.
#
capjamesg[d] I think testing, yes. But I'm cautious of us being here in a week because nobody read this message, changed their theme, and wrote feedback (which is all a big ask).
#
[tantek] capjamesg[d] why is suggesting people in the community try something counterproductive?
#
[tantek] also I think you may be conflating what the community has been asking for "for years" (which is a much larger redesign, a la /three_columns) with the general refresh design that [Paul_Robert_Ll] has done.
#
[tantek] [Paul_Robert_Ll] do you have a particular goal for when you think it would be good / impactful to switch to your refresh? E.g. is there some significant date? Perhaps first of the month?
#
aaronpk +1 for more testing by people here first. there's a lot of pages that have random things on them, so spot checking only a few here and there isn't really enough
#
capjamesg[d] I think setting a date helps.
#
[tantek] capjamesg[d] did the refresh design come up during HWC Europe? Did anyone mention it or any opinions about it?
#
capjamesg[d] The outcome I don't want is us having this same discussion next week.
#
capjamesg[d] [tantek] No!
#
[tantek] so that's not a good sign tbh
#
capjamesg[d] That's a sign nobody saw this, which is exactly what I'm talking about 😄
#
[tantek] having a live/sync chat about design changes is almost always very helpful, insightful, and nearly always reveals things (concerns, bugs) that async feedback does not
#
capjamesg[d] ++
#
capjamesg[d] I can arrange that next week.
#
[tantek] capjamesg[d], or it's a sign that there was literally not enough concern about it
#
[tantek] absence of input may indicate lack of discover or apathy. hard to tell which or a combination thereof. you can't assume either
#
capjamesg[d] [tantek] Given discussions have happened for years on the homepage and the topic has come up a lot in HWC Europe, I feel that any movement is great.
#
[tantek] again, don't conflate those two. this design refresh does NOT address the "discussions [that] have happened for years on the homepage"
#
capjamesg[d] No, but every time we have a discussion nothing happens other than another wiki page (a frustration that has been voiced several times). And something did now!
#
[tantek] what is three column
#
Loqi 2019/homepage is a project to update the IndieWeb community homepage in 2019, in particular with a three column layout designed for onboarding three common sets of visitors and new IndieWeb community members https://indieweb.org/three_column
#
capjamesg[d] We've got work to do!
#
capjamesg[d] But this is a step in the right direction (IMO) and I'd love to see what others think / if this inspires more.
#
[tantek] that's clearly not what this design refresh is about, so it's really unfair to both the folks who have had those conversations and to [Paul_Robert_Ll] who has done good work regardless to conflate them
#
aaronpk "I'd love to see what others think" exactly why you need to tell people how to preview the new theme on their user settings
#
aaronpk if we just flip the theme over, you probably won't hear from them if you haven't already!
#
capjamesg[d] I heard one frustration last week about the way we discuss things here that they aren't participating here because they can move faster elsewhere.
#
[tantek] yup and that's ok. we encourage people to move the fastest on their personal websites, that's the priority we direct people to.
#
capjamesg[d] And after I explicitly invited some people to join the discussion, they didn't.
#
capjamesg[d] I don't think it is okay.
#
[tantek] not everyone is going to be interested in everything, even after being invited. that doesn't mean we are doing anything wrong per se. that's also ok.
#
[tantek] people might not have time, or other reasons. /life_happens etc.
#
[tantek] please don't interpret lack of participation as justifying any particular reason like that. it's really unfair to everyone.
#
capjamesg[d] I see an invitation to a group of people who actively have personal websites in the "indie web" community not joining a discussion here after an invitation as a problem for us.
#
[tantek] it's not a problem, it's literally the default/baseline in volunteer / OSS work / communities.
#
capjamesg[d] Exactly. So if we have a contributor working on the homepage, we should be striving toward getting it into production!
#
capjamesg[d] Which sounds like it involves doing a live session.
#
capjamesg[d] Getting feedback.
#
capjamesg[d] Documenting it somewhere.
#
capjamesg[d] Incorporating said feedback.
#
capjamesg[d] Then making a release.
#
[tantek] yes that tends to produce better results, and is more inclusive of the community
#
aaronpk we are doing that, we've been going back and forth working on it, fixing css, etc etc
#
capjamesg[d] Exactly!
#
[tantek] having only a small number of people "cowboy" changes tends to reinforce any feelings of in/out groups and frankly *that* is a much harder/worse problem to solve
#
capjamesg[d] But what I'm saying is that we need to be more vocal about it!
#
[tantek] so I'm asking you to please be more sensitive and more community inclusive accordingly, even if it takes *weeks* longer
#
[tantek] yes, totally ok to be more vocal about it and bringing it up here for discussion, questions, feedback etc.!
#
capjamesg[d] I missed all the scrollback re: some of the changes made.
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
capjamesg[d] I'm excited about this change!
#
[tantek] ^ your HWC photo is in capjamesg[d]!
#
[tantek] [Paul_Robert_Ll] do you think we can work on incrementally (like in a backwards compatible way) adopting the styles from https://indieweb.org/User:Paulrobertlloyd.com/vector-2022.css into our current https://indieweb.org/MediaWiki:Common.css ?
#
[tantek] E.g. I already put in the max-width:100% rule (written from scratch from what I had there before I saw your vector-2022.css)
#
capjamesg[d] Excellent!
#
[tantek] If we can incorporate new vector-2022.css styles into the current Common.css (making whatever backcompat fixes we need to not break the current default theme / vector (2010)) then people trying vector 2022 won't need to add/edit their personal CSS to try the new design
#
[tantek] right now that's quite a bit of a barrier to trying the refresh design, that's why I'm asking
#
[tantek] capjamesg[d] btw as background, all past homepage and other large site redesign changes we made we literally had to do them during IndieWebCamps/IndieWebSummits or once we started having them, an Organizers Meetup where people *had* already looked at new logos, designs etc, and it took time, sometimes an hour, sometimes more, to actually get constructive feedback, do design iterations, then start testing changes, fixing bugs etc.
#
[tantek] Paul is quite thorough with these things, and a bunch of us have more familiarity with how MediaWiki styling/designs work (how to fix/break things 🙂 ), so I have greater confidence with this iteration, however it doesn't hurt to learn from and be cautious from experience
#
[tantek] tbc I'm quite excited about this refresh, it fixes so many papercuts and provides a more welcoming vibe. that's a good step forward, and maybe with the papercuts out of the way, we can focus on the more substantial structural redesign thoughts
#
[Paul_Robert_Ll] More than happy to add the vector-2022 changes to common.css; I think I need to be granted some sort of permission to edit that page though
#
[tantek] if you can test incorporating them the other way around, existing common.css rules into your vector-2022.css, I can help with incrementally editing the main common.css
#
[Paul_Robert_Ll] Ah, good idea! I’ll try that now…
#
[tantek] and what are you thinking for launch? feb 1st? valentine's day? flipping the switch live the morning of IWC Brighton? something else?
#
[Paul_Robert_Ll] While it’d be nice to have updated in time for when people can start getting tickets for IWC Brighton, perhaps best to not have too much to worry about on a single day! So maybe 14 Feb is a good date to shoot for?
#
capjamesg[d] Yay!
#
Loqi does a happy dance!
gRegor joined the channel
#
[campegg]1 FWIW, I have been using [Paul_Robert_Ll]’s updates via custom CSS for about a week now; I like it a lot and haven't come across anything that is notably broken (aside from the home page, which is a known thing)
gRegorLove_ joined the channel
#
[tantek] [campegg]++ thanks for testing!
#
Loqi [campegg] has 2 karma in this channel over the last year (5 in all channels)
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
capjamesg[d] A great newsletter!
#
gRegor I've not tried Paul's CSS changes yet, but have been using vector 2022 for months now. The upgrading of the core MW vector-2022 alone the other week has been great, resolved the sidebar issue.
#
[tantek] [Paul_Robert_Ll] one annoyance in the new look or maybe it's just Vector 2022 is the interline spacing on the left column list is way to big, it breaks the feeling of clustered items under the headings in the Sidebar
#
[tantek] way too* big
#
gRegor I'm still adjusting muscle memory though. Even though I'm used to it on Wikipedia, I forget sometimes I've collapsed the sidebar on our wiki and have to click the icon top left to check it :)
#
[tantek] when expanded I mean, the space between list-items is too big
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
paulrobertlloyd.com edited /User:Paulrobertlloyd.com/vector-2022.css (+1887) "Incorporate styles from common.css" (view diff)
#
[Paul_Robert_Ll] ☝ Got to do some experimentation with the above, and copy into and test with legacy theme. _Slightly_ tricky as ofcourse the existing common.css are applied before my custom styles. Will let you know when I think I have something worth testing.
#
paulrobertlloyd.com edited /User:Paulrobertlloyd.com/vector-2022.css (+87) "Add space above headings in sidebar" (view diff)
#
[Paul_Robert_Ll] [tantek] ☝ This change fixes sidebar/left column spacing
#
tantek.com edited /MediaWiki:Common.css (+106) "sidebar headings fix" (view diff)
#
[tantek] [Paul_Robert_Ll] that fixes the heading spacing but not the inter-list spacing which is so much that it reduces the list-ness of it
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
[Paul_Robert_Ll] I think that’s partly due to making sure the target size of those links is reasonable; the space is due to the padding applied to the links. Personally, I don’t mind it.
#
[tantek] I think it harms the semantics/legibility. increasing the target size of the links especially for mobile makes sense, but that wasn't ever a problem on desktop
#
[tantek] what I'm saying is that it is a regression in the look from the present
[lifeofpablo] joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
[tantek] we have tried for a while to encourage folks in HWC online meetups to use the #indieweb chat as the place to share links etc. from the meetup, and yet that doesn't seem to quite click. sometimes the Etherpad works, some subset of the folks at a HWC online contribute to it, however even that doesn't seem get everyone or even most people (in the meetup) participating
#
[Paul_Robert_Ll] Okay, I think the sidebar should look better with the latest changes in https://indieweb.org/User:Paulrobertlloyd.com/vector-2022.css
#
[tantek] folks have proposed (thanks capjamesg!) enabling the Zoom chat on the IndieWeb Zoom accounts as an alternative, but the downside there (as we experienced previously) is that it led to *less* participation in the community, as in people would pop-in, chat there, then disappear. whereas at least having a few more people go to the #indieweb chat to chat meant that at least *some* of them hung around a while
#
[tantek] would it help if we had a dedicated channel for HWC? e.g. # indieweb-hwc for live chats? that way it would be clear what the context of the chat was for, and not have to worry about imposing on other topics being discussed (e.g. as it is now in #indieweb or even here in #indieweb-meta)
#
tantek.com edited /MediaWiki:Common.css (+96) "try Paul's fix for the sidebar lists" (view diff)
#
[tantek] [Paul_Robert_Ll] yes that helped a bit. I'm going to try halving the padding on the link to see if that helps further
#
[tantek] links*
#
tantek.com edited /MediaWiki:Common.css (+96) "undo some of Vector 2022's list item spacing, tighten up sidebar list items a bit" (view diff)
#
tantek.com edited /MediaWiki:Common.css (+34) "cascade matching to override vector content list spacing inside the sidbar" (view diff)
#
[tantek] ^ [Paul_Robert_Ll] take a look
#
gRegor Whether a separate chat channel or not, I think a nice first step might be for Zoom Hosts to enable chat for only Hosts, and use the Zoom chat to periodically send links to the chat and etherpad.
#
gRegor It's a per-meeting setting based on searching a couple weeks ago, links should be in meta archives
#
gRegor Ack, I miss chat search for more recent stuff :/
#
[tantek] oh interesting, yes that makes sense as a good option for Zoom hosts to experiment with
#
[tantek] perhaps we can document that in the HWC page for organizers...
#
gRegor I'll find the zoom support page for it again.
#
[tantek] great, here's the place to add a list-item: https://indieweb.org/Homebrew_Website_Club#Setting_up_the_meeting_room
#
[tantek] IMO it would also help if an explicit IndieWeb chat link and Etherpad Notes link near the top of the Event Description, so it was easy to find, instead of buried at the bottom
#
gRegor +1
#
[tantek] Also, something like "Notes: https://etherpad.indieweb.... " is much better for visibility/discoverability/clickability rather than just a "Notes" link which is VERY easy to miss especially since the styling is so subtle (it's sorta blue, no underline)
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
gregorlove.com edited /Homebrew_Website_Club (+352) "/* Setting up the meeting room */ experimental: Zoom docs link, enable host/co-hosts to chat to broadcast chat/etherpad links" (view diff)
#
gRegor [tantek], What do you think of that section on https://events.indieweb.org/2024/01/homebrew-website-club-pacific-l8jJrVJmiF7q?
#
[tantek] gRegor++ that's a big improvement
#
Loqi gRegor has 38 karma in this channel over the last year (91 in all channels)
#
[tantek] I think we're still generally struggling how to put enough context in the summary / start of description but not so much that people just skim past. I don't have a good suggestion for that so far, been mostly leaving that up to individual organizers/hosts to figure out what seems to work for their meetup
#
gRegor Yeah, it's tricky. I noticed the Europe one uses a summary which shows up in the newsletter, but not Pacific
#
gRegor Though it's also the same description if several events are added like in today's newsletter
#
[tantek] right, seeing the same Summary over and over in the newsletter looks bad IMO. how can we fix that?
[Al_Abut] joined the channel
#
[Paul_Robert_Ll] Eek, I shared the wrong CSS (been editing both vector and vector-2022 files). This is the CSS needed for the sidebar:
#
[Paul_Robert_Ll] ```/* Adjust spacing of elements in sidebar */
#
[Paul_Robert_Ll] .vector-main-menu-container .vector-menu-heading {
#
[Paul_Robert_Ll] margin-top: 1em;
#
[Paul_Robert_Ll] }
#
[Paul_Robert_Ll] .vector-main-menu-container .vector-menu-content-list .mw-list-item a {
#
[Paul_Robert_Ll] padding-top: 0.25em;
#
[Paul_Robert_Ll] padding-bottom: 0.25em;
#
[Paul_Robert_Ll] }
#
[Paul_Robert_Ll] .vector-main-menu-container .vector-menu-content-list {
#
[Paul_Robert_Ll] padding-bottom: 0.5em;
#
[Paul_Robert_Ll] }```
#
[Paul_Robert_Ll] Currently, the CSS in custom.css is breaking the padding on other links around the UI
#
[tantek] you mean common.css?
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
[capjamesg] joined the channel
#
tantek.com edited /MediaWiki:Common.css (+167) "more sidebar spacing tweaks" (view diff)
#
tantek.com edited /MediaWiki:Common.css (-2) "slight reduction in sidebar li spacing" (view diff)
#
[tantek] [Paul_Robert_Ll] as a contrast, check out how tight the "Tools" menu is on the right sidebar is styled in Vector 2022. that looks much more appealing as a "menu" of things to click than the extra spaced things in the left sidebar
#
[Paul_Robert_Ll] It’s very difficult to tweak MediaWiki styles as it’s a bit of a wasps nest. For example, too broadly applied styles break things in unexpected places. This is what the toolbar currently looks like:
#
[Paul_Robert_Ll] https://chat-uploads.indieweb.org/files/2024/01/meta-20240126-210643-screenshot_2024-01-26_at_21.04.46.png
#
[Paul_Robert_Ll] `.vector-main-menu-container .vector-menu-content-list` keeps any changes scoped to the main menu. Other menus, I’d leave untouched.
#
[tantek] agreed on the fragility
#
tantek.com edited /MediaWiki:Common.css (-83) "remove extra bottom padding" (view diff)
#
tantek.com edited /MediaWiki:Common.css (+35) "scope CSS a bit more for the sidebar" (view diff)
#
[tantek] yes those scoping classes worked, toolbar should be fixed again
#
tantek.com edited /MediaWiki:Common.css (+0) "bump up left sidebar inter list-item spacing a bit to get closer to the Tools menu" (view diff)
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2024-01-26.html
#
tantek.com moved /Indiewebify.me to /IndieWebify.me "canonical capitalization on site"
#
tantek.com edited /IndieWebify.me (+0) "canonical caps" (view diff)
#
tantek.com edited /Ghost (+1420) "stub features & why sections, how to section with migrations, move articles above issues, focus on positive, also more recent, fix year in date, incorporate a few more SAs" (view diff)
#
aaronpk I am beginning to think I need to make the list of URLs in meetable configurable by the instance admin
#
sknebel so you set up e.g. having a pad link?
#
aaronpk for events.oauth.net I'd like links to the youtube recording and meeting minutes for IETF meetings for example, but it would just be distracting to have a "Minutes" field when editing an event for events.indieweb.org
#
aaronpk so i could make it part of the site settings, you'd define what extra fields you want on events
#
aaronpk i guess the next question is whether events themselves should also be able to add arbitrary extra fields
#
[Al_Abut] [tantek] thanks for the link to the discussion of Gresham’s
#
[Al_Abut] Law, I hadn’t heard of it and seeing it repurposed into “too much dev talk is like accidentally trolling” is interesting
#
[Al_Abut] Also I think I missed it because I’m trying to keep up with scrollbacks but sometimes I declare Slack bankruptcy when it’s like 780+ messages missed 😆
#
Loqi Just generated this week's newsletter! You still have a few minutes to make changes, and I'll re-generate it 10 minutes before it gets sent out at 3pm Pacific time. https://indieweb.org/this-week/2024-01-26.html
#
[tantek] the scrollback struggle is real [Al_Abut]
#
[tantek] if it helps, I find that once I've been away for more than a day (yes it happens 😂 ), the archives are much easier to read quickly than chat clients
#
[tantek] oops I got distracted by other things, let's see what else we can fix for the newsletter
#
tantek.com edited /omg.lol (+214) "bring your own domain is a key feature" (view diff)
#
[Al_Abut] Well I’m glad I scrolled back because I’m super glad to see there’s a new mobile-friendly theme in the works by [Paul_Robert_Ll]! When it comes to making things more broadly inviting, forget renaming the main chat channel, that’s going to be frigging huge.
#
tantek.com edited /indiewebify.me (+0) "r--" (view diff)
#
tantek.com edited /Indiewebify (+0) "r--" (view diff)
#
tantek.com edited /indiewebifyme (+0) "r--" (view diff)
#
tantek.com edited /indiewebify (+0) "r--" (view diff)
#
tantek.com edited /indieweb_validator (+0) "r--" (view diff)
#
tantek.com edited /webify (+0) "r--" (view diff)
#
tantek.com edited /Planning (+25) "SF needs a new venue" (view diff)
#
tantek.com edited /Bridgy_Fed (+24) "dfn user-focus" (view diff)
#
[tantek] ok that should bump the min edits needed for this newsletter to 4 and thus avoid the "test" page showing up
#
[tantek] guess we'll know in a little over a minute
#
[tantek] [Al_Abut] I agree, mobile-friendly viewing of the site is massive and it's been a heroic effort by aaronpk updating our MediaWiki and the design/theme/CSS updates & fixes by [Paul_Robert_Ll]++
#
Loqi [Paul_Robert_Ll] has 14 karma in this channel over the last year (22 in all channels)
#
Loqi Generated the final version of the newsletter! This will be sent out at 3pm Pacific time. https://indieweb.org/this-week/2024-01-26.html
#
[tantek] I mean the wiki/site should look MUCH better already (like right now) on mobile browsers
#
[tantek] newsletter is looking great!
#
[tantek] one improvement which will take some thinking and likely coding, can we cluster the upcoming "Homebrew Website Club Europe/London" events especially since they have the same title and summary?
#
[tantek] thoughts & ideas welcome gRegor, capjamesg[d], aaronpk, on either/both a good way to present a clustering of same-named/regular events, and potentially what logic/code to use for such clustering
#
capjamesg[d] Agreed.
#
capjamesg[d] It is nice having them planned out for the next few weeks so that people know they aren't going to miss the opportunity to join us.
#
capjamesg[d] It would be nice if the event appeared once with a "With future events held on..." list or something like that.
#
capjamesg[d] If two events have exactly the same name it can be implied they are part of a series. We usually change titles for special events like years in review.
#
capjamesg[d] Curious to hear what others think!
CRISPR joined the channel
#
[tantek] agreed capjamesg[d], perhaps clustering purely by direct event title string match would be sufficient, and then only display the Summary from the next upcoming event in that series, but then display the dates as "Wednesday, February 7 at 7:00pm, and again on February 14, 21, 28"
#
[tantek] with each of those linking to its specific instance so there is something directly clickable, e.g "February 14" would be a link, as would "21" and "28"
gRegor joined the channel
#
gRegor Can probably re-use some of the code used for clustering the event notes pages