#meta 2022-01-28

2022-01-28 UTC
j12t joined the channel
#
[tantek] web3 << Comparison to IndieWeb: https://twitter.com/johnjohnston/status/1486817984299552772
#
@johnjohnston Liked https://mxb.dev/blog/make-free-stuff/ (http://mxb.dev) Despite what web3 claims, it’s possible to “own” your content without a proof of it on the blockchain (see: IndieWeb). It’s also possible to create things just for the sake of putting them out into the world. (twitter.com/_/status/1486817984299552772)
#
Loqi ok, I added "Comparison to IndieWeb: https://twitter.com/johnjohnston/status/1486817984299552772" to the "See Also" section of /Web_3.0 https://indieweb.org/wiki/index.php?diff=79380&oldid=79342
#
Loqi Just generated the first draft of this week's newsletter! https://indieweb.org/this-week/2022-01-28.html I'll generate a draft again tomorrow, so please add to it before then! https://indieweb.org/this-week#How_to
#
GWG- That reminds me. Photo
strugee, balupton[d], [tonz], maxwelljoslyn[d], alex_, _maxwelljoslyn[d, saptaks_znc, Seirdy, strugee_, [jeremyfelt], [manton], [tw2113_Slack_], [KevinMarks], IWSlackGateway, jjuran, Zegnat, sknebel, jacky, [jeremycherfas] and sgreger joined the channel
#
sgreger Hi. Haven't been here in a while. It seems it is not possible to update a webmention that was accidentally sent to IndieNews as a bookmark. I fixed my markup and resubmitted, but IndieNews created a second webmention entry rather than updating the original.
#
sgreger Long story short: sorry for the duplicate :)
#
[tantek] ^ aaronpk, sounds like a bug in IndieNews's webmention update handler (or delete for that matter)
#
[tantek] and hello sgreger!
#
[tantek] you wrote something about pixelating avatars right?
#
[tantek] for privacy reasons I think?
#
sgreger I created an issue at https://github.com/aaronpk/IndieNews/issues/54 – just not sure is this a feature or a bug
#
Loqi [sebastiangreger] #54 Unable to update webmention after first version contained a bookmark microformat
#
sgreger tantek: http://sgnet.test/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr
#
sgreger tantek: https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr
#
Loqi [Sebastian Greger] The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR)
#
[tantek] yes that's the one! and it's 3x3 pixels as I remember!
#
[tantek] I'm considering 3x3 pixelated external avatars to avoid displaying "unpleasant" avatars
#
sgreger tantek: yes. i can see if i can find the code snippet somewhere, if that's of use to you?
#
[tantek] that would be cool!
#
[tantek] I'll start a page
#
capjamesg[d] [tantek] interesting. I hadn't thought about that.
#
capjamesg[d] That code snippet would be useful sgreger!
#
sgreger I really liked the aesthetics of the 3x3 avatars, even though no longer using them… I believe I have that snippet somwhere as I recall sharing it an IWC once
#
loqi.me created /pixelated (+322) "prompted by [tantek] and dfn added by [tantek]" (view diff)
#
sebastiangreger.net edited /pixelated (+241) "add use cases and sample code" (view diff)
#
sgreger It was just an adaption of example code from SO, so I simply added a link there (not sure about the licensing, as our wiki is CC0 and SO answers are CC-BY-SA)
#
@IndieScripter Always a pleasure to follow another #IndieWeb person. This time it's Pelle Wessman @voxpelli who rightly posits "corepack must be the least celebrated gem of newer node versions". https://twitter.com/voxpelli/status/1486737012971474944 (twitter.com/_/status/1486992473289211904)
Seb[d] and [Francesco_Impr] joined the channel
#
capjamesg[d] web3 << Keep the web free, say no to Web3: https://yesterweb.org/no-to-web3/index.html
#
Loqi ok, I added "Keep the web free, say no to Web3: https://yesterweb.org/no-to-web3/index.html" to the "See Also" section of /Web_3.0 https://indieweb.org/wiki/index.php?diff=79384&oldid=79380
[Grant_Hutchins] joined the channel
#
aaronpk That is weird, it's supposed to let you update submissions
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
#
Loqi [github] Error deploying aaronpk/IndieNews to https://news.indieweb.org
#
Loqi [github] Error deploying aaronpk/IndieNews to https://news.indieweb.org
sgreger joined the channel
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
#
aaronpk that should fix it
#
sgreger aaronpk: Yes, that commit looks like the behaviour I expected. Thanks for looking into it!
#
aaronpk surprised this hadn't come up earlier tbh!
#
sgreger Well, it was a pretty significant, and in that very specific, change in my markup (from bookmark to note), so I guess I unveiled some edge case there ;)
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
marksuth[d], Seb[d], wackycity[d], sayanarijit[d], Eddy04[d], Christian_Olivie, Silicon[d], edburns[d], grantcodes[d], hoenir, mossymaker[d], tracydurnell[d], kimberlyhirsh[d], balupton[d], capjamesg[d], Asaf_Agranat[d], rattroupe[d], corenominal[d], Ramon[d], MarkJR84[d], Jeremiah[d], shaunix[d], hans63us[d], Myst[d], sarahd[d], maxwelljoslyn[d] and aspenmayer[d] joined the channel
#
sgreger Still trying to fine-tune my markup after that hiccup.
#
sgreger https://indieweb.org/bookmark states "For submissions of bookmarks, IndieNews displays the name and domain of the bookmarked post as if it were posted directly […]"
#
sgreger That was not the case for my submission. The "bookmark" showed up with the title of my note.
#
sgreger This is separate from the "update webmention" issue; maybe something odd with my markup? (I had `class="h-cite u-bookmark-of"` on an <a> element inside the `h-entry` my note)
#
sgreger s/my/of my/i
jamietanna, jacky and petermolnar joined the channel
#
@voxpelli Got free from my current assignment a bit earlier than originally anticipated, so open to new freelance work in Node.js, JS, semantic HTML, standards, IndieWeb etc starting immediately. (twitter.com/_/status/1487090647794343937)
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
[asuh] joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
sebastiangreger.net edited /LimeSurvey (+96) "/* See Also */ add Yakforms as LimeSurvey alternative" (view diff)
#
sebastiangreger.net uploaded /File:content-warning-example-sg.png "Screenshot of a bookmark card with active content warning for an accessibility issue. https://indieweb.org/File:content-warning-example-sg.png"
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
sebastiangreger.net edited /content_warning (+283) "add example of a11y seizure warning" (view diff)
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
neceve joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
tracydurnell[d] at HWC either this week or last week, we had the idea of including a short bullet list of "highlights" or "topics discussed" at events in the newsletter - is that something that's technically possible since it's auto-generated? I don't know how it works 😂
#
aaronpk neat! it pulls all the event data from the events.indieweb.org pages so we'd have to find a way to include it there
#
tracydurnell[d] makes sense
#
tracydurnell[d] I assume it pulls certain fields, so we'd either need to add a new field or figure out an existing field to put it in?
jacky and [aciccarello]1 joined the channel
#
aaronpk yep
#
tracydurnell[d] 👍
doosboox3, klez and GWG joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
aaronpk that's an interesting use case for some new markup. there's clearly a consuming use case for it already
#
[tantek] I mean there's already p-summary for that
#
aaronpk Could work, but that does feel slightly different
#
aaronpk maybe the difference is what you'd expect to find there before and after an event
#
[tantek] either way it's a summary. whether it changes before/after has nothing to do with the name of the field. I mean "highlights" is a summary
#
[tantek] an editable field would work, as a summary should be human authored
#
[tantek] and updating it after the fact would work
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
Nuve joined the channel
#
aaronpk Sounds reasonable
#
aaronpk should I race the clock...?
#
[tantek] to add a text field? I mean I bet you could do it. Question is then getting content into it for a couple of events
#
aaronpk Text field, and also newsletter parsing update
#
aaronpk ok here we go
#
[tantek] oh wow yeah. UI to edit, backend to publish, backend to parse, backend to format for publication
#
aaronpk also.. what if any HTML is allowed in summary?
#
aaronpk both on the event page as well as in the newsletter
#
aaronpk and where to display it? seems like the summary should be at the top before the event and at the bottom after?
jacky joined the channel
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
sknebel could also be a highlighted response instead of something edited on the site?
#
GWG aaronpk: I'd allow links and lists at least
#
aaronpk alright summary field is on events.indieweb.org anyone want to add some data so i can pull stuff into the newsletter?
#
aaronpk interesting, the newsletter already has "summary" in it
#
Loqi [Event Updated] aaronparecki.com updated "Jan 26, 2022 6:00pm Homebrew Website Club - Pacific" changed summary https://events.indieweb.org/event/334/history/1007/diff
#
aaronpk let's see if that works
#
aaronpk yep! now go add some real info tracydurnell[d]!
#
tracydurnell[d] cool, will do!
#
tracydurnell[d] aaronpk++ thanks for adding!
#
Loqi aaronpk has 30 karma in this channel over the last year (121 in all channels)
#
Loqi [Event Updated] tracydurnell.com updated "Jan 26, 2022 6:00pm Homebrew Website Club - Pacific" changed summary "revise summary with topics discussed" https://events.indieweb.org/event/334/history/1008/diff
#
tracydurnell[d] doesn't look like the markdown is working
#
Loqi [Event Updated] aaronparecki.com updated "Jan 26, 2022 6:00pm Homebrew Website Club - Pacific" changed summary "add newline for markdown list" https://events.indieweb.org/event/334/history/1009/diff
#
Loqi [Event Updated] aaronparecki.com updated "Jan 26, 2022 6:00pm Homebrew Website Club - Pacific" changed summary "use markdown link syntax" https://events.indieweb.org/event/334/history/1010/diff
#
aaronpk i fixed it
#
aaronpk it's picky
#
tracydurnell[d] haha fair 😉
#
aaronpk i'm tempted to add a preprocessor to make mediawiki link syntax work too
#
tracydurnell[d] I think this looks good on the event!
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
aaronpk tracydurnell[d]++ yay
#
Loqi tracydurnell[d] has 17 karma in this channel over the last year (21 in all channels)
#
Loqi 😃
jacky joined the channel
#
aaronpk suggestions welcome for visual formatting on the event page
#
aaronpk right now the summary appears above the description with no heading
#
tracydurnell[d] I feel like it's ok without a heading
#
tracydurnell[d] having the rules between sections kind of highlights it
#
tracydurnell[d] but maybe it'll depend on how people use it 😉
Nuve joined the channel
#
Loqi [Event Updated] tracydurnell.com updated "Jan 22, 2022 9:30am IndieWebCamp Popup: Analog Meets Online" changed summary "add summary of things discussed" https://events.indieweb.org/event/324/history/1011/diff
#
tracydurnell.com edited /2022/Pop-ups/Analog_Meets_Online (+313) "add a short topic summary at top" (view diff)
#
tracydurnell[d] I also added the summary to the top section of the wiki page for the pop-up, do you think that's helpful?
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
[tantek] wow stuff! looking ...
#
[tantek] aaronpk++ brilliant!
#
Loqi aaronpk has 31 karma in this channel over the last year (122 in all channels)
#
[tantek] yes, keep the summary of the event both before and after!
#
[tantek] aaronpk, what I was expecting in the newsletter: a "More..." link right after the summary that links to a fragment on the event page right after the summary
#
[tantek] e.g. slap an id on <div class="e-content description segment content">
#
[tantek] maybe id="event-description"
#
[tantek] and then add the "More..." text right after the summary in the newsletter (on its own line right after the summary, but with CSS style="text-align:right" would be fine) that links to e.g. https://events.indieweb.org/2022/01/homebrew-website-club-pacific-7N5iRHCxRt7K#event-description
#
[tantek] This way when we do update the Event description to e.g. link to the archived Etherpad notes, those are readily discoverable via the newsletter as well
#
[tantek] it also helps provide motivation to archive the etherpad notes more promptly, and link to them in an update to the description on the event page, since folks may be clicking through to see them via the newsletter
#
capjamesg[d] That all happened quickly. Amazing!
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
[tantek] what is MDN
#
Loqi Mozilla Developer Network is a web development resource https://indieweb.org/MDN
#
capjamesg[d] That stub needs fleshed out a bit if only to add a better definition.
#
[tantek] ^ capjamesg[d] perhaps you could expand that page, at least listing the newly updated Microformats page that's been listed
#
[tantek] 😄
#
capjamesg[d] Yes, I shall do so!
#
[tantek] and then maybe add a Brainstorming section per edgeduchess[d]'s recommendation for 'entries for all the main "indieweb" components'
#
capjamesg[d] I will get on that tomorrow. I agree with what edgeduchess[d] said about MDN explanations being good and to the point.
#
[tantek] let's at least capture that as a suggestion, and then can discuss which specific IndieWeb components / building blocks would be good / appropriate on MDN and prioritize them respectively
#
capjamesg[d] I think we would have to agree on an appropriate remit for such a guide, so as not to attempt to duplicate the IndieWeb wiki pages.
#
capjamesg[d] I think a “what is”, “why”, and “how to” would be a good rundown for at least a beginning of such an article on an IndieWeb concept.
#
capjamesg[d] I’d also vote for webmentions to be documented first.
#
capjamesg[d] +1 tantek
[James_Van_Dyne] joined the channel
#
[snarfed] also vs the https://microformats.org/wiki/microformats2 pages
#
capjamesg[d] I agree. I’ll look around MDN a bit more to gain a further understanding of the way they write content. I refer to it a lot but need to take a closer look.
#
capjamesg[d] And refer to the style guide again.
#
[snarfed] (you all will know better than me where the three sites should overlap/diverge, I have no opinion)
#
[tantek] capjamesg[d] I think with explicit thoughtfulness about the purpose & audience of each of the sites, we can come up with what kinds of content / structure makes the most sense on each
#
[tantek] e.g. (roughly off the top of my head for microformats related pages)
#
[tantek] microformats wiki : specifications
#
[tantek] indieweb wiki : user-understandable definition of said microformats and why those matter to users, and developer understandable "Why" and "How to" sections, and "IndieWeb Examples" along with allowing lots more messy / unstructured wiki content "in progress"
#
[tantek] MDN : very focused *web developer* perspective brief definition, use-cases, and how-to, with very good copywriting / copyediting, no "messy" or "unstructured" / in-progress content, and links to the official spec (on microformats wiki) and the IndieWeb community "discussion" page as well
#
[tantek] that's a rough idea of the kind of thing we could put in /MDN#Brainstorming for how to work towards writing up a new topic for MDN (hint: do the respective work above on the microformats and IndieWeb wikis first, and then subset/curate/rewrite for the MDN audience accordingly)
#
capjamesg[d] I agree. That is a good outline for how we should think about the different wikis.
#
capjamesg[d] Definitely, MDN content should be well-structured and written with the intent of helping someone easily comprehend and start working with a topic.
#
Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2022-01-28.html
#
capjamesg[d] This is something I’ll contribute to.
#
capjamesg[d] I’d love to have cohesive resources that introduce people to IndieWeb topics in prose / code snippets vs. the wiki format.
#
capjamesg[d] The wiki works really well but sometimes a focused piece does better for learning, especially when you are a beginner.
#
[schmarty] i'd like to see some explainers that detail how multiple indieweb building blocks come together to make higher-level "features"
#
[schmarty] (for example "show responses from twitter" goes quite deep)
#
capjamesg[d] Yes! That’s a key one.
#
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/2022-01-28.html
#
Loqi Generated the final version of the newsletter! This will be sent out at 3pm Pacific time. https://indieweb.org/this-week/2022-01-28.html
#
@indiewebcamp This week in the #indieweb https://indieweb.org/this-week/2022-01-28.html (twitter.com/_/status/1487202588189597700)