Updates tagged with indiewebcamp on stadeus!
: Great #indieweb sessions at #btconf #Berlin!Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well!Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like:* 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse)* IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack)Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites!Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page!Want to connect your online home with online neighbors?* Join the IndieWeb #webring: https://indieweb.org/IndieWeb_WebringPrefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp!Glossary and links:btconf (Beyond Tellerrand conference) Berlin 2025 https://beyondtellerrand.com/events/berlin-2025communities (IndieWeb) https://indieweb.org/communitiesdigital gardens https://indieweb.org/digital_gardenhome (page) on the web https://indieweb.org/homepageHomebrew Website Club (HWC) online and in-person: https://events.indieweb.org/tag/hwcFront End Study Hall (FrESH) https://indieweb.org/freshIndieWebCamps - in-person and hybrid! https://events.indieweb.org/tag/indiewebcampThis is post 16 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos→ 🔮
's status on Friday, 07-Nov-2025 11:09:00 EST
Great #indieweb sessions at #btconf #Berlin! Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well! Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like: * 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse) * IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack) Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites! Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page! Want to connect your online home with online neighbors? * Join the IndieWeb #webring: https://indieweb.org/IndieWeb_Webring Prefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp! Glossary and links: btconf (Beyond Tellerrand conference) Berlin 2025 https://beyondtellerrand.com/events/berlin-2025 communities (IndieWeb) https://indieweb.org/communities digital gardens https://indieweb.org/digital_garden home (page) on the web https://indieweb.org/homepage Homebrew Website Club (HWC) online and in-person: https://events.indieweb.org/tag/hwc Front End Study Hall (FrESH) https://indieweb.org/fresh IndieWebCamps - in-person and hybrid! https://events.indieweb.org/tag/indiewebcamp This is post 16 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos → 🔮
: IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon.Session notes are up from day 1, recordings to follow:* https://indieweb.org/2025/Berlin/ScheduleDemos notes also up, recording to follow:* https://indieweb.org/2025/Berlin/DemosWant to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed:* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_MyQuestions about sessions or demos? Ask in #IndieWeb chat!* https://chat.indieweb.org/This is post 15 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin→ 🔮
's status on Friday, 07-Nov-2025 05:55:00 EST
IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon. Session notes are up from day 1, recordings to follow: * https://indieweb.org/2025/Berlin/Schedule Demos notes also up, recording to follow: * https://indieweb.org/2025/Berlin/Demos Want to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed: * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My Questions about sessions or demos? Ask in #IndieWeb chat! * https://chat.indieweb.org/ This is post 15 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin → 🔮
: 🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday.Want to keep up with #IndieWebCamp #Berlin participants?Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms)* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_MyWe’ll add more as folks sign-in at the camp!This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟← https://tantek.com/2025/303/t1/october-blogging-challenges→ 🔮
's status on Friday, 31-Oct-2025 18:14:00 EDT
🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday. Want to keep up with #IndieWebCamp #Berlin participants? Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms) * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My We’ll add more as folks sign-in at the camp! This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟 ← https://tantek.com/2025/303/t1/october-blogging-challenges → 🔮
: October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like:#Blogtober#IndieWebMovieClub on #Hackers#Inktober#Mathober#WeirdWebOctober+ coding challenges:#Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025Many more at:* https://indieweb.org/October* https://indieweb.org/blog_carnival🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration:* https://indieweb.org/HalloweenLast but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend!* https://indieweb.org/2025/BerlinThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions→ 🔮
's status on Thursday, 30-Oct-2025 19:27:00 EDT
October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like: #Blogtober #IndieWebMovieClub on #Hackers #Inktober #Mathober #WeirdWebOctober + coding challenges: #Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025 Many more at: * https://indieweb.org/October * https://indieweb.org/blog_carnival 🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration: * https://indieweb.org/Halloween Last but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend! * https://indieweb.org/2025/Berlin This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions → 🔮
: Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended!* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).* 18 introduced themselves² and their personal sites or aspirations for oneCollectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends.Session titles (and hashtags)* How to #POSSE* How to make the web queerer / stranger. #queer* Online presence after our #death* Threat modeling #threatmodeling* Non-technical collaboration on the internet. #collab* Locations and #places check-in* Writing with images. #imagewriting* Text authoring UX. #textUX* #SSR, organizing CSS/JS* Website design without being a designer. #designfordummies* Timeline algorithms. #timelinesEtherpad notes from sessions have been archived to the wiki, with session recordings to follow!Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.References ¹ https://indieweb.org/2024² https://indieweb.org/2024/Berlin/Intros³ https://indieweb.org/2024/Berlin/Schedule#SaturdayThis is post 28 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/306/t1/simple-embeds→ 🔮
's status on Saturday, 09-Nov-2024 08:31:00 EST
Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended! * 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22). * 18 introduced themselves² and their personal sites or aspirations for one Collectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends. Session titles (and hashtags) * How to #POSSE * How to make the web queerer / stranger. #queer * Online presence after our #death * Threat modeling #threatmodeling * Non-technical collaboration on the internet. #collab * Locations and #places check-in * Writing with images. #imagewriting * Text authoring UX. #textUX * #SSR, organizing CSS/JS * Website design without being a designer. #designfordummies * Timeline algorithms. #timelines Etherpad notes from sessions have been archived to the wiki, with session recordings to follow! Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants. References ¹ https://indieweb.org/2024 ² https://indieweb.org/2024/Berlin/Intros ³ https://indieweb.org/2024/Berlin/Schedule#Saturday This is post 28 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/306/t1/simple-embeds → 🔮
: European friends!🗓 I am going to Beyond Tellerand (@btconf@mastodon.social) Berlin next week 7-8 November and you should too!BTconf is the best independent web design, development, and inspiration conference in Europe.Everything from the speakers to the talks to the side events are a labor of love by @MarcThiele.com (@marcthiele@mastodon.social) and his crew, and it shows in the #btconf community he has gathered over the years.If you’re in #Berlin, or can hop on a train and join us, you should.🎟 Grab a ticket: https://btco.nf/tAnd while you’re there, consider joining us at #IndieWebCamp Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #barcamp style discussions sessions and an #indieweb Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.
's status on Friday, 01-Nov-2024 01:34:00 EDT
European friends! 🗓 I am going to Beyond Tellerand (@btconf@mastodon.social) Berlin next week 7-8 November and you should too! BTconf is the best independent web design, development, and inspiration conference in Europe. Everything from the speakers to the talks to the side events are a labor of love by @MarcThiele.com (@marcthiele@mastodon.social) and his crew, and it shows in the #btconf community he has gathered over the years. If you’re in #Berlin, or can hop on a train and join us, you should. 🎟 Grab a ticket: https://btco.nf/t And while you’re there, consider joining us at #IndieWebCamp Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #barcamp style discussions sessions and an #indieweb Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
's status on Sunday, 01-Sep-2024 17:51:00 EDT
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ 🔮
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → 🔮
: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
's status on Friday, 30-Aug-2024 00:09:00 EDT
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → https://tantek.com/2024/245/t1/read-write-suggest-edit-web
: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ 🔮
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → 🔮
: Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ https://tantek.com/2024/242/t1/indiewebcamp-portland
's status on Sunday, 25-Aug-2024 19:00:00 EDT
Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → https://tantek.com/2024/242/t1/indiewebcamp-portland
: Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ 🔮
Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → 🔮
: The Library of Infinite Loan is a physical world practice I conceived of many many years ago¹, implemented in minimal prototype form 5+ years ago², shared a summary with the #IndieWeb community at least four years ago at the #IndieWebCamp Austin in 2020³ and last year in IndieWeb chat⁴, so it’s about time⁵ I wrote it down. Summary: lend a #book from your personal library⁶ to a friend, on the conditions that they do not donate sell or dispose of it, and instead when they are done with it they return it or lend it to someone else who agrees to these conditions.My goal was to create a book lending system that:* preserves books — effectively in a giant #distributed communal #library* makes lending easier fiscally, psychologically, emotionally for both parties* encourages direct person-to-person lending without intermediaries* grows a culture of non-zero-sum sharing, preservation, and longterm thinkingThe basic steps to create a Library of Infinite Loan:1. Create a separate space (like a particular bookshelf) for #books to infinite lend. A small shelf in a guest room or common space like a hallway works well.2. Move books there that you are ok lending out and never seeing again3. Label that space your “Library of Infinite Loan”, or invite guests to borrow from your “Library of Infinite Loan”4. When visitors ask what that means, explain the RulesRules for borrowing from a Library of Infinite Loan (“the Rules”)1. Keep it as long as you like2. Do not sell donate or otherwise dispose of it3. You may give it a. back to the person you borrowed from b. or back to its original purchaser if they wrote their name and web address inside c. or (lend it) to someone else who agrees to the RulesThere are several ways to extend / expand the Library of Infinite Loan:* custom book plate: design a custom book plate for yourself with room for your name (and web address) on it e.g. “From Tantek’s (@tantek.com) Library” (with space), print it on longterm adhesive paper, and place it inside new books you purchase. When you move a book to your Library of Infinite Loan, amend the book plate to say ”… Library of Infinite Loan” and attach a copy of the Rules. * add a “borrowers log” with blank lines for anyone you lend it to or they lend it to, transitively, to optionally add their name, web address, and a date of borrowing. Then amend the rules to allow returning a book to who you borrowed from or anyone in the borrower log or original purchaser.* more media: CDs, vinyl records, DVDs, LaserDiscs, VHS, cassette tapes, video game cartridges etc.* other things * large tools — which usually come in a box with instruction manual, so there’s a logical place to put an “owners plate”, “borrowers log”, and copy of the rules. * artwork — a great way to rotate art among a communityThis is what I remember off the top of my head and with a little web searching. I know I have a bunch more notes in various places of my thoughts (and conversations) over the years about a Library of Infinite Loan. As I find those notes, I’ll post them as well.#infiniteLoan #libraryOfInfiniteLoanReferences:¹ I’m looking through old personal logs for earliest mentions of “infinite loan”² In my 2019 personal log I found a note that I “moved some books as library of infinite loan to guest room” where I had previously setup a small bookshelf for such books.³ https://indieweb.org/2020/Austin/reading⁴ https://chat.indieweb.org/2023-10-01#t1696202307311300⁵ I was also inspired by sharing the idea again to a couple of friends in an espresso-making livestream this morning⁶ https://indieweb.org/personal_library
's status on Monday, 29-Apr-2024 21:53:00 EDT
The Library of Infinite Loan is a physical world practice I conceived of many many years ago¹, implemented in minimal prototype form 5+ years ago², shared a summary with the #IndieWeb community at least four years ago at the #IndieWebCamp Austin in 2020³ and last year in IndieWeb chat⁴, so it’s about time⁵ I wrote it down. Summary: lend a #book from your personal library⁶ to a friend, on the conditions that they do not donate sell or dispose of it, and instead when they are done with it they return it or lend it to someone else who agrees to these conditions. My goal was to create a book lending system that: * preserves books — effectively in a giant #distributed communal #library * makes lending easier fiscally, psychologically, emotionally for both parties * encourages direct person-to-person lending without intermediaries * grows a culture of non-zero-sum sharing, preservation, and longterm thinking The basic steps to create a Library of Infinite Loan: 1. Create a separate space (like a particular bookshelf) for #books to infinite lend. A small shelf in a guest room or common space like a hallway works well. 2. Move books there that you are ok lending out and never seeing again 3. Label that space your “Library of Infinite Loan”, or invite guests to borrow from your “Library of Infinite Loan” 4. When visitors ask what that means, explain the Rules Rules for borrowing from a Library of Infinite Loan (“the Rules”) 1. Keep it as long as you like 2. Do not sell donate or otherwise dispose of it 3. You may give it a. back to the person you borrowed from b. or back to its original purchaser if they wrote their name and web address inside c. or (lend it) to someone else who agrees to the Rules There are several ways to extend / expand the Library of Infinite Loan: * custom book plate: design a custom book plate for yourself with room for your name (and web address) on it e.g. “From Tantek’s (@tantek.com) Library” (with space), print it on longterm adhesive paper, and place it inside new books you purchase. When you move a book to your Library of Infinite Loan, amend the book plate to say ”… Library of Infinite Loan” and attach a copy of the Rules. * add a “borrowers log” with blank lines for anyone you lend it to or they lend it to, transitively, to optionally add their name, web address, and a date of borrowing. Then amend the rules to allow returning a book to who you borrowed from or anyone in the borrower log or original purchaser. * more media: CDs, vinyl records, DVDs, LaserDiscs, VHS, cassette tapes, video game cartridges etc. * other things * large tools — which usually come in a box with instruction manual, so there’s a logical place to put an “owners plate”, “borrowers log”, and copy of the rules. * artwork — a great way to rotate art among a community This is what I remember off the top of my head and with a little web searching. I know I have a bunch more notes in various places of my thoughts (and conversations) over the years about a Library of Infinite Loan. As I find those notes, I’ll post them as well. #infiniteLoan #libraryOfInfiniteLoan References: ¹ I’m looking through old personal logs for earliest mentions of “infinite loan” ² In my 2019 personal log I found a note that I “moved some books as library of infinite loan to guest room” where I had previously setup a small bookshelf for such books. ³ https://indieweb.org/2020/Austin/reading ⁴ https://chat.indieweb.org/2023-10-01#t1696202307311300 ⁵ I was also inspired by sharing the idea again to a couple of friends in an espresso-making livestream this morning ⁶ https://indieweb.org/personal_library
: What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links.I went through the 13 Session Notes archives and did the following:* converted Markdown links to MediaWiki links* converted indieweb.org (and some services) links to local wiki page links* fixed (some) typosWith some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25I point this out to provide an example of an IndieWeb Create Day project that is:* incremental on top of someone else’s work* community contribution rather a personal-focused project* editing and wiki-gardening as valid contributions, not just creating new contentI point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:* new innovations (not incremental improvements)* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations* something large, a new service or a big feature, not numerous small edits & fixesIn this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation.For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-casesMy stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths.That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention* https://tantek.com/2023/014/t4/domain-first-federated-atmention* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMentionI was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:* https://indieweb.org/2024/Brighton/DemosThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases→ 🔮Glossary:Create Day https://indieweb.org/Create_DayIndieWebCamp Brighton 2024 https://indieweb.org/2024/BrightonReferences:¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two² https://indieweb.org/what_to_make_at_IndieWebCamp³ https://indieweb.org/2024/Brighton/Schedule#Saturday
's status on Tuesday, 12-Mar-2024 22:19:00 EDT
What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before. Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both. At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps. For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links. I went through the 13 Session Notes archives and did the following: * converted Markdown links to MediaWiki links * converted indieweb.org (and some services) links to local wiki page links * fixed (some) typos With some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits: * https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25 I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s work * community contribution rather a personal-focused project * editing and wiki-gardening as valid contributions, not just creating new content I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward: * new innovations (not incremental improvements) * solo (or maybe jointly in a small team) inventions, designs, specs, or implementations * something large, a new service or a big feature, not numerous small edits & fixes In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation. For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements. * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths. That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning: * https://tantek.com/2023/011/t1/indieweb-evolving-at-mention * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo * https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day: * https://indieweb.org/2024/Brighton/Demos This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases → 🔮 Glossary: Create Day https://indieweb.org/Create_Day IndieWebCamp Brighton 2024 https://indieweb.org/2024/Brighton References: ¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two ² https://indieweb.org/what_to_make_at_IndieWebCamp ³ https://indieweb.org/2024/Brighton/Schedule#Saturday
: Updated the auto-linking code¹ on my website last Sunday to handle a few more @-mention use-cases.In particular:* @-domains with dashes/hyphens like @sonja-weckenmann.de* @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is* @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantekI also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such "basic HTTP auth"^2 was poorly designed and should not be used (and thus should not be linked).If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions:* auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link* auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths.This code is only live on my website (testing in production³ as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub⁴ as well.With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification.This (blog post) is my contribution to today’s #IndieWebCamp Brighton⁵ #hackday!This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.⁶#autolink #atmention #atmentions #atat #atatmentionThis is post 12 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/047/t1/indieweb-major-update-design→ 🔮¹ https://tantek.com/cassis.js² https://en.wikipedia.org/wiki/Basic_access_authentication³ https://indieweb.org/test_in_production⁴ https://tantek.com/github/cassis³ https://indieweb.org/2024/Brighton⁴ https://tantek.com/2023/302/t1/indiewebcamp-completed-projects
's status on Sunday, 10-Mar-2024 10:55:00 EDT
Updated the auto-linking code¹ on my website last Sunday to handle a few more @-mention use-cases. In particular: * @-domains with dashes/hyphens like @sonja-weckenmann.de * @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is * @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantek I also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such "basic HTTP auth"^2 was poorly designed and should not be used (and thus should not be linked). If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions: * auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link * auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths. This code is only live on my website (testing in production³ as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub⁴ as well. With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification. This (blog post) is my contribution to today’s #IndieWebCamp Brighton⁵ #hackday! This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.⁶ #autolink #atmention #atmentions #atat #atatmention This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/047/t1/indieweb-major-update-design → 🔮 ¹ https://tantek.com/cassis.js ² https://en.wikipedia.org/wiki/Basic_access_authentication ³ https://indieweb.org/test_in_production ⁴ https://tantek.com/github/cassis ³ https://indieweb.org/2024/Brighton ⁴ https://tantek.com/2023/302/t1/indiewebcamp-completed-projects
: #Brighton #London and other #England & #Europe friends:🎪 #IndieWebCamp Brighton tickets are available!🎟 https://ti.to/indiewebcamp/brighton-2024🗓 2024-03-09…10🏢 The Skiff, Brighton, England🌐 https://indieweb.org/2024/BrightonGrab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_personFor more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-plannedThis is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon→ 🔮
's status on Sunday, 04-Feb-2024 23:08:00 EST
#Brighton #London and other #England & #Europe friends: 🎪 #IndieWebCamp Brighton tickets are available! 🎟 https://ti.to/indiewebcamp/brighton-2024 🗓 2024-03-09…10 🏢 The Skiff, Brighton, England 🌐 https://indieweb.org/2024/Brighton Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person For more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/ Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand! Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned This is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb ← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon → 🔮
: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel.Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers.Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰This is post 8 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted→ 🔮Post glossary:development channel (indieweb-dev) https://indieweb.org/discuss#devDiscord https://indieweb.org/Discordformat https://indieweb.org/formatHacker News (HN) https://indieweb.org/Hacker_NewsIndieWeb https://indieweb.org/IndieWebIndieWebCamp https://indieweb.org/IndieWebCampIRC https://indieweb.org/IRCjargon https://indieweb.org/jargonLoqi https://indieweb.org/Loqimain IndieWeb chat channel (on main) https://indieweb.org/discuss#indiewebMatrix https://indieweb.org/Matrixmeta chat channel https://indieweb.org/discuss#metaMediaWiki Category https://www.mediawiki.org/wiki/Project:Categoriesplumbing https://indieweb.org/plumbingprotocol https://indieweb.org/protocolReddit https://indieweb.org/Reddittools https://indieweb.org/toolsSlack https://indieweb.org/Slacksocial media silos https://indieweb.org/silos¹ https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling)² https://indieweb.org/discuss#Email³ https://indieweb.org/make_what_you_need⁴ https://indieweb.org/use_what_you_make⁵ https://indieweb.org/rename_to_IndieWeb⁶ https://indieweb.org/jargon⁷ https://indieweb.org/Category:jargon#Loqi_Nudge⁸ https://indieweb.org/discuss#Chat_Channels_Purposes⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800
's status on Sunday, 04-Feb-2024 18:05:00 EST
Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel. We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel. Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were. We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers. Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused. It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers. The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰ This is post 8 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted → 🔮 Post glossary: development channel (indieweb-dev) https://indieweb.org/discuss#dev Discord https://indieweb.org/Discord format https://indieweb.org/format Hacker News (HN) https://indieweb.org/Hacker_News IndieWeb https://indieweb.org/IndieWeb IndieWebCamp https://indieweb.org/IndieWebCamp IRC https://indieweb.org/IRC jargon https://indieweb.org/jargon Loqi https://indieweb.org/Loqi main IndieWeb chat channel (on main) https://indieweb.org/discuss#indieweb Matrix https://indieweb.org/Matrix meta chat channel https://indieweb.org/discuss#meta MediaWiki Category https://www.mediawiki.org/wiki/Project:Categories plumbing https://indieweb.org/plumbing protocol https://indieweb.org/protocol Reddit https://indieweb.org/Reddit tools https://indieweb.org/tools Slack https://indieweb.org/Slack social media silos https://indieweb.org/silos ¹ https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling) ² https://indieweb.org/discuss#Email ³ https://indieweb.org/make_what_you_need ⁴ https://indieweb.org/use_what_you_make ⁵ https://indieweb.org/rename_to_IndieWeb ⁶ https://indieweb.org/jargon ⁷ https://indieweb.org/Category:jargon#Loqi_Nudge ⁸ https://indieweb.org/discuss#Chat_Channels_Purposes ⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people ¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800
: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue such threads in the channel it started rather than break to another channel. It was also a constant bit of community labor to nudge developer conversations to the developer chat channel.We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel.Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers.Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.It takes a community to keep a community healthy and welcoming to newcomers. Eternal community vigilance is the price of being user-centric and welcoming to newcomers.The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰This is post 8 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted→ 🔮Post glossary:development channel (indieweb-dev) https://indieweb.org/discuss#devformat https://indieweb.org/formatIndieWeb https://indieweb.org/IndieWebIndieWebCamp https://indieweb.org/IndieWebCampjargon https://indieweb.org/jargonLoqi https://indieweb.org/Loqimain IndieWeb chat channel (on main) https://indieweb.org/discuss#indiewebmeta chat channel https://indieweb.org/discuss#metaMediaWiki Category https://www.mediawiki.org/wiki/Project:Categoriesplumbing https://indieweb.org/plumbingprotocol https://indieweb.org/protocoltools https://indieweb.org/toolssocial media silos https://indieweb.org/silos¹ https://www.paulgraham.com/trolls.html² https://indieweb.org/discuss#Email³ https://indieweb.org/make_what_you_need⁴ https://indieweb.org/use_what_you_make⁵ https://indieweb.org/rename_to_IndieWeb⁶ https://indieweb.org/jargon⁷ https://indieweb.org/Category:jargon#Loqi_Nudge⁸ https://indieweb.org/discuss#Chat_Channels_Purposes⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800
Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue such threads in the channel it started rather than break to another channel. It was also a constant bit of community labor to nudge developer conversations to the developer chat channel. We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel. Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were. We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers. Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused. It takes a community to keep a community healthy and welcoming to newcomers. Eternal community vigilance is the price of being user-centric and welcoming to newcomers. The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰ This is post 8 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted → 🔮 Post glossary: development channel (indieweb-dev) https://indieweb.org/discuss#dev format https://indieweb.org/format IndieWeb https://indieweb.org/IndieWeb IndieWebCamp https://indieweb.org/IndieWebCamp jargon https://indieweb.org/jargon Loqi https://indieweb.org/Loqi main IndieWeb chat channel (on main) https://indieweb.org/discuss#indieweb meta chat channel https://indieweb.org/discuss#meta MediaWiki Category https://www.mediawiki.org/wiki/Project:Categories plumbing https://indieweb.org/plumbing protocol https://indieweb.org/protocol tools https://indieweb.org/tools social media silos https://indieweb.org/silos ¹ https://www.paulgraham.com/trolls.html ² https://indieweb.org/discuss#Email ³ https://indieweb.org/make_what_you_need ⁴ https://indieweb.org/use_what_you_make ⁵ https://indieweb.org/rename_to_IndieWeb ⁶ https://indieweb.org/jargon ⁷ https://indieweb.org/Category:jargon#Loqi_Nudge ⁸ https://indieweb.org/discuss#Chat_Channels_Purposes ⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people ¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800
: The first IndieWebCamp of the year has been planned!🎪 IndieWebCamp Brighton🗓 2024-03-09…10🏢 The Skiff, Brighton, England🎟 Tickets available 2024-02-01!Event: https://events.indieweb.org/2024/03/indiewebcamp-brighton-2024-xRTP2hAZOvZdWiki: https://indieweb.org/2024/Brighton Questions about #IndieWebCamp? Ask in #IndieWeb chat!💬 https://chat.indieweb.org/This is post 3 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/003/t1/2023-indieweb-gift-calendar-numbers→ 🔮
's status on Tuesday, 23-Jan-2024 02:20:00 EST
The first IndieWebCamp of the year has been planned! 🎪 IndieWebCamp Brighton 🗓 2024-03-09…10 🏢 The Skiff, Brighton, England 🎟 Tickets available 2024-02-01! Event: https://events.indieweb.org/2024/03/indiewebcamp-brighton-2024-xRTP2hAZOvZd Wiki: https://indieweb.org/2024/Brighton Questions about #IndieWebCamp? Ask in #IndieWeb chat! 💬 https://chat.indieweb.org/ This is post 3 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/003/t1/2023-indieweb-gift-calendar-numbers → 🔮
: 31 days of #IndieWeb gifts: the _2023 IndieWeb Gift Calendar_ (https://indieweb.org/2023-12-indieweb-gift-calendar) wrapped up a full month of IndieWeb-related creations & updates from the community (and sometimes beyond) to everyone who wants to improve their #IndieWeb experience. From plugins & libraries, to tools & services, to events & meetups, to web components & wiki pages, and blog posts & newsletters, there was something for everyone.Some numbers:🎁 67 total gifts📄 32 new IndieWeb wiki pages📜 7 posts on improving blogs, IndieWeb specs, and event summaries💻 6 Homebrew Website Club online meetups📫 5 This Week In The IndieWeb newsletters🧱 4 library updates: new web components, #microformats2 parser update 🌉 3 Bridgy Fed updates & improvements 🧩 2 plugin updates: #Elgg IndieWeb & #WordPress #IndieAuth🎪 1 #IndieWebCamp San Diego (2 days!)📚 1 indiebookclub new year in review overview feature📽 1 IndieWeb movie viewings aggregator🧶 1 #Threads federating out #ActivityPub (followable by #BridgyFed)Gift were shared by:👥 20 individuals🏢 1 companyI compiled these numbers by hand. Let me know if you see any errors. There are many more potential stats like:* average (mean and median) number of gifts per contributor* how many edits to the Gift Calendar wiki page* how many different editors of the wiki page* average (mean and median) number of edits per editorI’ll leave those as exercises for others if they wish!This is post 2 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar→ 🔮
's status on Wednesday, 03-Jan-2024 19:09:00 EST
31 days of #IndieWeb gifts: the _2023 IndieWeb Gift Calendar_ (https://indieweb.org/2023-12-indieweb-gift-calendar) wrapped up a full month of IndieWeb-related creations & updates from the community (and sometimes beyond) to everyone who wants to improve their #IndieWeb experience. From plugins & libraries, to tools & services, to events & meetups, to web components & wiki pages, and blog posts & newsletters, there was something for everyone. Some numbers: 🎁 67 total gifts 📄 32 new IndieWeb wiki pages 📜 7 posts on improving blogs, IndieWeb specs, and event summaries 💻 6 Homebrew Website Club online meetups 📫 5 This Week In The IndieWeb newsletters 🧱 4 library updates: new web components, #microformats2 parser update 🌉 3 Bridgy Fed updates & improvements 🧩 2 plugin updates: #Elgg IndieWeb & #WordPress #IndieAuth 🎪 1 #IndieWebCamp San Diego (2 days!) 📚 1 indiebookclub new year in review overview feature 📽 1 IndieWeb movie viewings aggregator 🧶 1 #Threads federating out #ActivityPub (followable by #BridgyFed) Gift were shared by: 👥 20 individuals 🏢 1 company I compiled these numbers by hand. Let me know if you see any errors. There are many more potential stats like: * average (mean and median) number of gifts per contributor * how many edits to the Gift Calendar wiki page * how many different editors of the wiki page * average (mean and median) number of edits per editor I’ll leave those as exercises for others if they wish! This is post 2 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar → 🔮
: at the first ever #IndieWebCamp San Diego, documented a bunch of discussions and content in new and updated wiki pages on https://indieweb.org/ and updated my home page static events listing.#IndieWeb wiki pages created, from small stubs to longer and reasonably thorough:* https://indieweb.org/December* https://indieweb.org/joy* https://indieweb.org/what_to_make_at_IndieWebCamp
's status on Sunday, 17-Dec-2023 18:15:00 EST
at the first ever #IndieWebCamp San Diego, documented a bunch of discussions and content in new and updated wiki pages on https://indieweb.org/ and updated my home page static events listing. #IndieWeb wiki pages created, from small stubs to longer and reasonably thorough: * https://indieweb.org/December * https://indieweb.org/joy * https://indieweb.org/what_to_make_at_IndieWebCamp
: coding at #IndieWebCamp Nuremberg, completed the following projects:0.0: fixed the https://chat.indieweb.org/ footer to drop #Matrix as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provide an explicit link/encouragement for filing issues0.5: investigated IndieWeb wiki issues (mobile presentation), possible fixes, and documented them: https://indieweb.org/MediaWiki_customizations#Issues0.7: add HTML <search> element support to my home page and permalinks as nerdsniped by @adactio.com (@adactio@mastodon.social @adactio); expanded to <search role=search> to also support folks using older browsers / screenreaders that only support #ARIA 1.1.0.8: replaced my incorrect use of HTML attribute aria-hidden="true" (on my links to #BridgyFed) as pointed out by @jkphl.is (@jkphl@mastodon.social @jkphl) and https://sonja-weckenmann.de (@sweckenmann@mas.to), with hidden="from-humans". Since other values are allowed on the hidden attribute and treated as hidden="hidden", the "from-humans" value communicates a subtle semantic that the element is intended for consumption by robots & crawlers, like #Bridgy.0.8.1 Update: created a pull-request (https://github.com/snarfed/bridgy-fed/pull/701) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well.Time is up for today’s IndieWebCamp Create Day so my remaining projects will have to wait.
's status on Sunday, 29-Oct-2023 11:18:00 EDT
coding at #IndieWebCamp Nuremberg, completed the following projects: 0.0: fixed the https://chat.indieweb.org/ footer to drop #Matrix as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provide an explicit link/encouragement for filing issues 0.5: investigated IndieWeb wiki issues (mobile presentation), possible fixes, and documented them: https://indieweb.org/MediaWiki_customizations#Issues 0.7: add HTML <search> element support to my home page and permalinks as nerdsniped by @adactio.com (@adactio@mastodon.social @adactio); expanded to <search role=search> to also support folks using older browsers / screenreaders that only support #ARIA 1.1. 0.8: replaced my incorrect use of HTML attribute aria-hidden="true" (on my links to #BridgyFed) as pointed out by @jkphl.is (@jkphl@mastodon.social @jkphl) and https://sonja-weckenmann.de (@sweckenmann@mas.to), with hidden="from-humans". Since other values are allowed on the hidden attribute and treated as hidden="hidden", the "from-humans" value communicates a subtle semantic that the element is intended for consumption by robots & crawlers, like #Bridgy. 0.8.1 Update: created a pull-request (https://github.com/snarfed/bridgy-fed/pull/701) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well. Time is up for today’s IndieWebCamp Create Day so my remaining projects will have to wait.
: Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl).Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ️ More info: https://indieweb.org/2023/Nuremberg#bordernone #bono23 #IndieWeb
's status on Friday, 27-Oct-2023 19:23:00 EDT
Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl). Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ). Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday! 🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k 🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc ℹ️ More info: https://indieweb.org/2023/Nuremberg #bordernone #bono23 #IndieWeb
: 1 month ago today: Victory Column en route to@IndieWebCamp#Berlin.Our second #IndieWebCamp@MozillaBerlinthis year, we had amazing participants(2,3), hosted an@OptOutSocialhackathon, and a keynote by founder Teresa(4 📷@cheukting_ho)!About a dozen sessions with notes and some with session videos linked from the schedule:https://indieweb.org/2019/Berlin2/ScheduleLast but not least, great working with co-organizers Yulia (@ioctaptceb),@RosemaryOrchard, and@DShansketo put it all together and discuss community at the Organizers meetup the day before the camp(5).Previously:https://tantek.com/2019/327/t1/amazing-start-indiewebcamp-berlin#VictoryColumn#IndieWeb#community#organizers#grateful#2019_328#20191124#latergram#nofilter
's status on Tuesday, 24-Dec-2019 04:04:00 EST
1 month ago today: Victory Column en route to@IndieWebCamp#Berlin. Our second #IndieWebCamp@MozillaBerlinthis year, we had amazing participants(2,3), hosted an@OptOutSocialhackathon, and a keynote by founder Teresa(4 📷@cheukting_ho)! About a dozen sessions with notes and some with session videos linked from the schedule:https://indieweb.org/2019/Berlin2/Schedule Last but not least, great working with co-organizers Yulia (@ioctaptceb),@RosemaryOrchard, and@DShansketo put it all together and discuss community at the Organizers meetup the day before the camp(5). Previously:https://tantek.com/2019/327/t1/amazing-start-indiewebcamp-berlin #VictoryColumn#IndieWeb#community#organizers#grateful#2019_328#20191124#latergram#nofilter
: #IndieWebCamp#Brighton:For my #hackdayproject I added a #serviceworkerto myhttps://tantek.com/home page with some #offlinesupport:1 Custom Offline page2 Precache home page, CSS, JS, and cache as you go photos3 Precache /contact & /pay pages
's status on Sunday, 20-Oct-2019 12:20:00 EDT
#IndieWebCamp#Brighton: For my #hackdayproject I added a #serviceworkerto myhttps://tantek.com/home page with some #offlinesupport: 1 Custom Offline page 2 Precache home page, CSS, JS, and cache as you go photos 3 Precache /contact & /pay pages
: #IndieWebCamp Brighton:I proposed and am facilitating a session on:Local first vs.Offline first vs.no cloud,and multidevices.#localofflineWhat’s the difference between #LocalFirst & #OfflineFirst?etc.
's status on Saturday, 19-Oct-2019 09:48:00 EDT
#IndieWebCamp Brighton: I proposed and am facilitating a session on: Local first vs. Offline first vs. no cloud, and multidevices. #localoffline What’s the difference between #LocalFirst & #OfflineFirst? etc.
: #IndieWebCamp NYC: facilitating session on Why Publish with @schmarty @dshanske @tiereeee et al. Many reasons folks like to publish things (publicly) online. Notes being captured into an Etherpad, to be archived to #indieweb wiki after. #whypublish #meta
's status on Saturday, 05-Oct-2019 14:45:00 EDT
#IndieWebCamp NYC: facilitating session on Why Publish with @schmarty @dshanske @tiereeee et al. Many reasons folks like to publish things (publicly) online. Notes being captured into an Etherpad, to be archived to #indieweb wiki after. #whypublish #meta
: Announcing today:IndieWebCamp Brighton is BACK for 2019!Super excited to return to@68MiddleStafter 3 years for the sixth #IndieWebCamp#BrightonOct 19-20th, thanks to host@adactio!Save the dates and start booking travel:https://indieweb.org/2019/Brighton
's status on Sunday, 12-May-2019 16:42:00 EDT
Announcing today: IndieWebCamp Brighton is BACK for 2019! Super excited to return to@68MiddleStafter 3 years for the sixth #IndieWebCamp#BrightonOct 19-20th, thanks to host@adactio! Save the dates and start booking travel: https://indieweb.org/2019/Brighton
: #IndieWebCamp Düsseldorf hack day minor site improvements:* better #webactions text symbols ♥♺↵ https://indieweb.org/webactions#emoji_text_labels* better reply-context symbol ↳ https://indieweb.org/reply-context#Minimal_text_reply_contextsand figured out flex>grid>flex CSS for table>tr>td for @aaronpk monthly archives.
's status on Sunday, 12-May-2019 06:41:00 EDT
#IndieWebCamp Düsseldorf hack day minor site improvements: * better #webactions text symbols ♥♺↵ https://indieweb.org/webactions#emoji_text_labels * better reply-context symbol ↳ https://indieweb.org/reply-context#Minimal_text_reply_contexts and figured out flex>grid>flex CSS for table>tr>td for @aaronpk monthly archives.
: During #IndieWebCamp#BerlinI built a simple theme switcher for my site!hyperlinks -> URL query param -> PHP to add class to & query param to local links -> CSS class selectors -> CSS variables -> colors & font. No cookies, no JS. #indieweb
's status on Tuesday, 07-May-2019 20:45:00 EDT
During #IndieWebCamp#BerlinI built a simple theme switcher for my site! hyperlinks -> URL query param -> PHP to add class to & query param to local links -> CSS class selectors -> CSS variables -> colors & font. No cookies, no JS. #indieweb
: #IndieWebCamp #Austin day 2: Make, create, and hack!Mine: webhost migration (mine shuts down EOD 3/6 ET)Step 1 done: reduce TTLs on hosted domains to minimum allowed by my registrar (600s).Improving #IndieWeb docs as I go:* indieweb.org/migration* indieweb.org/TTL
's status on Sunday, 24-Feb-2019 12:15:00 EST
#IndieWebCamp #Austin day 2: Make, create, and hack! Mine: webhost migration (mine shuts down EOD 3/6 ET) Step 1 done: reduce TTLs on hosted domains to minimum allowed by my registrar (600s). Improving #IndieWeb docs as I go: * indieweb.org/migration * indieweb.org/TTL
: Excited for #IndieWebCamp#Austinstarting soon!Check out the (and add yourself to) remote participation if you can’t make it in person!https://indieweb.org/2019/Austin#Remote_Participation#indieweb#openweb#dweb#independentweb
's status on Saturday, 23-Feb-2019 09:49:00 EST
Excited for #IndieWebCamp#Austinstarting soon! Check out the (and add yourself to) remote participation if you can’t make it in person! https://indieweb.org/2019/Austin#Remote_Participation #indieweb#openweb#dweb#independentweb
: Hello #Austin!Any Austin friends out & about downtown tonight?Looking forward to #IndieWebCamp Austin tomorrow morning at Capital (in the Omni lobby)Still a few spots available: https://2019.indieweb.org/austin#indieweb #openweb #dweb #independentweb
's status on Saturday, 23-Feb-2019 00:04:00 EST
Hello #Austin! Any Austin friends out & about downtown tonight? Looking forward to #IndieWebCamp Austin tomorrow morning at Capital (in the Omni lobby) Still a few spots available: https://2019.indieweb.org/austin #indieweb #openweb #dweb #independentweb
: #IndieWebCamp#Austinis next weekend!Get a #website, #ownyourdata, cut back #socialmedia, or hack on #dweb#webstandards.Join@manton2(@microdotblog)@aaronpk(#indieauth #webmention)@dshanske(#WordPress #IndieWeb) & more!RSVP:https://2019.indieweb.org/austin
's status on Friday, 15-Feb-2019 21:22:00 EST
#IndieWebCamp#Austinis next weekend! Get a #website, #ownyourdata, cut back #socialmedia, or hack on #dweb#webstandards. Join@manton2(@microdotblog)@aaronpk(#indieauth #webmention)@dshanske(#WordPress #IndieWeb) & more! RSVP:https://2019.indieweb.org/austin
: At #IndieWebCamp@MozillaBerlin, coded some archive navigation in@Falcon: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress.Next steps:https://indieweb.org/Falcon#archive_pagesRelated #indiewebpages:*https://indieweb.org/navigation*https://indieweb.org/pagination*https://indieweb.org/archive_navigation
's status on Sunday, 04-Nov-2018 11:00:00 EST
At #IndieWebCamp@MozillaBerlin, coded some archive navigation in@Falcon: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress. Next steps:https://indieweb.org/Falcon#archive_pages Related #indiewebpages: *https://indieweb.org/navigation *https://indieweb.org/pagination *https://indieweb.org/archive_navigation
: #IndieWebCamp NYC off to a great start with keynotes:* @Bali_Maha Connecting the World: Intentions and Realities https://blog.mahabali.me/educational-technology-2/connecting-the-world-intentions-and-realities-keynote-sept-28-indiewebcamp/* @iamjessklein Designing for participation in open spaces https://docs.google.com/presentation/d/1dnCDc6BAohIuL8fxB2_nOqtpzGX6RWt1BE4Vay4tC2Y/edit?usp=sharingLive feed: https://www.youtube.com/watch?v=ZlkhhMiGP-g
's status on Friday, 28-Sep-2018 10:45:00 EDT
#IndieWebCamp NYC off to a great start with keynotes: * @Bali_Maha Connecting the World: Intentions and Realities https://blog.mahabali.me/educational-technology-2/connecting-the-world-intentions-and-realities-keynote-sept-28-indiewebcamp/ * @iamjessklein Designing for participation in open spaces https://docs.google.com/presentation/d/1dnCDc6BAohIuL8fxB2_nOqtpzGX6RWt1BE4Vay4tC2Y/edit?usp=sharing Live feed: https://www.youtube.com/watch?v=ZlkhhMiGP-g
: led #IndieWebCamp#Austinsession on Payments, Pledges, and Donations, Oh My!Discussed:* #indieweb.org/paypages work:tantek.com/pay* #Patreonbacklash, creators/patrons stuck* or use Stripe,@W3C#PaymentRequest APISession Notes:https://indieweb.org/2017/Austin/payAnd plan to build/improve on our sites tomorrow@IndieWebCamp#AustinHack Day!Come on by:https://2017.indieweb.org/austin
's status on Saturday, 09-Dec-2017 17:00:00 EST
led #IndieWebCamp#Austinsession on Payments, Pledges, and Donations, Oh My! Discussed: * #indieweb.org/paypages work:tantek.com/pay * #Patreonbacklash, creators/patrons stuck * or use Stripe,@W3C#PaymentRequest API Session Notes:https://indieweb.org/2017/Austin/pay And plan to build/improve on our sites tomorrow@IndieWebCamp#AustinHack Day! Come on by:https://2017.indieweb.org/austin
mmn: I was asked about it in #IndieWebCamp's IRC channel and figured: what the heck, why not?
mmn's status on Thursday, 04-Jun-2015 10:32:05 EDT
I was asked about it in #IndieWebCamp's IRC channel and figured: what the heck, why not?