Show Navigation
Notices tagged with indiewebcamp
-
š 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-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 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/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/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/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-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-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 #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 #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 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) 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/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/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#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#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-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 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
-
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.
Tantek
All stadeus content and data are available under the