gRegor Morrill gregorlove.com

Have questions about HTML/CSS? Join the Front End Study Hall hosted by @artlung@xoxo.zone on Zoom next Wednesday, April 24!
#indieweb
gRegor Morrill gregorlove.com

Have questions about HTML/CSS? Join the Front End Study Hall hosted by @artlung@xoxo.zone on Zoom next Wednesday, April 24!
#indieweb
@jcrabapple dmv.community/@jcrabapple

Scribbles Categories

https://cool-as-heck.blog/post/scribbles-categories

#indieweb
@Zeronaut fosstodon.org/@Zeronaut

Just posted a new article on my blog called Joyous Jazz about Trying a new jazz club and sharing the joy of music with my partner
#GoHugo #indieweb #Blog

https://allisthewave.com/posts/2024-04-09-joyous-jazz/
@artlung xoxo.zone/@artlung

Front End Study Hall next Wednesday. Zoom open format HTML+CSS #IndieWeb. https://artlung.com/blog/2024/04/15/front-end-study-hall/ #IndieWeb
@brianb fosstodon.org/@brianb

I kind of miss having a search option on my blog.

https://blog.ohheybrian.com/2024/04/i-kind-of-miss-search/

#100DaysToOffload #indieweb
@anders thoresson.social/@anders

An observation: What started as a list with #11ty-related account I follow here is slowly transforming into an #indieweb/ #SmallWeb list. Not surprisingly perhaps that there is a huge overlap between the two communities.
@jcrabapple dmv.community/@jcrabapple

Finally, A Weekend We've Been Waiting For

https://cool-as-heck.blog/post/finally-a-weekend-we-ve-been-waiting-for

#indieweb
#indieweb mastodon.social/tags/indieweb

I wonder if anyone has tested this #PullRequest yet that adds #Micropub support to #Misskey? I kinda don't want this PR to get forcefully discarded because of too many merge conflicts with upstream... ​:sagume_think:​

I might try testing it out here in #Makai later but I will have to find a good Micropub client on #Android and #Windows first (feel free to suggest here I guess you #IndieWeb nerds ​:chuckling_okuu:​)

(Also for some reason my previous quote renote linking to this OP got lost, I don't remember deleting it... ​:SanaeConfuzzled:​)

RE: https://p1.a9z.dev/notes/9p80jquq4o
#indieweb mastodon.social/tags/indieweb
Last week I participated @W3.org (@w3c@w3c.social) #w3cAC (W3C Advisory Committee¹), #w3cAB (W3C Advisory Board² @ab@w3c.social), and #w3cBoard (Board of the W3C Corporation³) meetings in Hiroshima, Japan.

The AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the #w3cTAG), then separate meetings to focus on their own tasks & discussions.

The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the W3C TAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.

The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #w3cTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²):

* https://www.w3.org/wiki/AC/Meetings#2024_Spring

Most of the W3C meeting materials and discussions were also W3C Member-confidential, however many of the presentations are publicly viewable, and a few more may be shared publicly after the fact.

Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.

Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB

Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.

For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:
* 📄 report: https://www.w3.org/reports/ai-web-impact/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf
* ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch
* ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch
* 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf
* 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.
* 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/

I’ll update this list with additional resources as they are made publicly viewable.

If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday

References:

¹ https://w3.org/wiki/AC
² https://w3.org/wiki/AB
³ https://w3.org/wiki/Board
⁴ https://www.w3.org/Consortium/Process/
⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings
⁶ https://w3.org/tag
⁷ https://www.w3.org/groups/wg/
⁸ https://chapters.w3.org/
⁹ https://www.w3.org/invited-experts/#ac-observer
¹⁰ https://www.w3.org/wiki/TPAC
¹¹ https://www.w3.org/events/ac/2024/ac-2024/
¹² https://www.w3.org/membership/list/
¹³ https://en.wiktionary.org/wiki/hallway_track
¹⁴ https://microformats.org/wiki/existing-rel-values
¹⁵ https://indieweb.org/sidefile-antipattern
¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
Tantek Çelik tantek.com
Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard (Board of the W3C Corporation³) meetings in Hiroshima, Japan.

The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.

The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²):

* https://www.w3.org/wiki/AC/Meetings#2024_Spring

Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.

Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.

Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB

Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.

For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:
* 📄 report: https://www.w3.org/reports/ai-web-impact/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf
* ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch
* ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch
* 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf
* 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.
* 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/

I’ll update this list with additional resources as they are made publicly viewable.

If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday

References:

¹ https://w3.org/wiki/AC
² https://w3.org/wiki/AB
³ https://w3.org/wiki/Board
⁴ https://www.w3.org/Consortium/Process/
⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings
⁶ https://w3.org/tag
⁷ https://www.w3.org/groups/wg/
⁸ https://chapters.w3.org/
⁹ https://www.w3.org/invited-experts/#ac-observer
¹⁰ https://www.w3.org/wiki/TPAC
¹¹ https://www.w3.org/events/ac/2024/ac-2024/
¹² https://www.w3.org/membership/list/
¹³ https://en.wiktionary.org/wiki/hallway_track
¹⁴ https://microformats.org/wiki/existing-rel-values
¹⁵ https://indieweb.org/sidefile-antipattern
¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
#W3CAC #W3CAB #W3CBoard #w3cTAG #W3CTPAC #W3C #OpenAB #IndieWeb
@cory social.lol/@cory

🔗: Small Web, Indie Web #Tech #Blogging #IndieWeb #SmallWeb https://scottwillsey.com/small-web/
@alabut techhub.social/@alabut

@jaredwhite oh I hadn’t considered the blocking instances either. I wonder how many those are in practice? Maybe I’m just too basic and not cool enough for the rowdier parts of the fediverse 😂

So hey, while I’ve got you on the horn, thought I’d take a sec to say that I love what you’re doing with the CSS course! I started diving into a much overdue refresher on frontend skills since rebooting my site late last year and it’s been eye-opening to see how far native browser techniques have come while I was phoning it in with the same old tired Bootstrap grids.

I see that you’re thinking of adding other teachers and was wondering if you’d be interested in partnering up for a “Design for Non-Designers” course for devs or other design newbies? It’s a topic that’s come up lately on the #indieweb zoom calls and it’s fun to see people going through the same self-taught dev-to-design transition at the beginning of my career. Just a thought!
@fromjason mastodon.social/@fromjason

It's interesting how conversations about the #IndieWeb, #SmallWeb, and even federation, aren't happening on #BlueSky in any meaningful way.

In fact, none of the major microblogging platforms are engaged in conversations about the web as much as #Mastodon from what I can tell.
@jlsksr mastodon.online/@jlsksr

I really like personal homepages and have quite a list of them bookmarked. I'll post one every week until I don't. So here's Cool Personal Homepages #CPH Vol. 12: Eloy's website https://eloydegen.com/

@eloy is on Mastodon!

#SmallWeb #indieweb #smolweb #PersonalSites #homepage
@jaredwhite indieweb.social/@jaredwhite

✅ My Now page is now, now, not then any longer. Been meaning to check that off the ol' to-do list for a long time! 😅 Howdy springtime 2024! 🌸

📍 Now Read This:

https://jaredwhite.com/now

#NowPage #NowPages #Blog #Blogging #SmallWeb #IndieWeb
@larsolino indieweb.social/@larsolino

Started my permamanent under construction digital garden. First step was a plain HTML and CSS setup with hosting and domain configuration.

https://larsolino.com

#digitalgarden #realindieweb #indieweb #html #css
@larsolino indieweb.social/@larsolino

Started my permamanent under construction digital garden. First step was a plain HTML and CSS setup with hosting and domain configuration.

https://larsolino.com

#digitalgarden #realindieweb #indieweb #html #css
@janboddez indieweb.social/@janboddez

So, I have my site set up to no longer accept webmentions (i.e., remove the endpoint from the `Link` header) after a month or two—when I close “regular” comments, too.

Which means it’ll also discard any edit or delete requests that come in after that time. That doesn’t seem entirely right.

May be a reason to keep webmentions open (but, e.g., discard new mentions only).

(Not sure if ActivityPub replies are ever closed.)

#indieweb #webmention

(https://bddz.be/v0J)
#indieweb mastodon.social/tags/indieweb

So, I have my site set up to no longer accept webmentions (i.e., remove the endpoint from the Link header) after a month or two—when I close “regular” comments, too.

Which means it’ll also discard any edit or delete requests that come in after that time. That doesn’t seem entirely right.

May be a reason to keep webmentions open (but, e.g., discard new mentions only).

(Not sure if ActivityPub replies are ever closed.)

(https://bddz.be/v0J)