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 authentication² 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
This past Saturday: finished the #InsideTrail Redtail Ridge 30k #trailRace in 6:00:59.
A few notes:
This was my first trail race of 2024, and first in over 6 months, since last year’s Marin Ultra Challenge 50k and Broken Arrow 23k races in June¹. Saw pal Henri after changing into my trail shoes in the Lake Chabot Regional Park parking lot. The storms had scared many away, fewer than 100 showed up to the combined 30k & 50k start.
The muddy rainy adventure began when we veered off the initial paved trail around the lake and onto a rocky uphill stretch. It was mostly an out-and-back course, with a bit of a loop in the middle. On the second half of that loop there was one fork in the trail without race markings. After spending minutes taking a peek down both options, I guessed right. About a half mile later a wooden trail post validated my choice.
I kept a sustainable run/hike pace, with some sliding in the mud, stepping around many ruts and puddles of unknown depths. Slower finish than 5 years ago², yet this time with a negative split, and earned my first DLF award!
#30k #RedtailRidge #trailRun #trailRunner #runner #trailRunning #running #2024_048
¹ https://tantek.com/2023/178/t1/june-trailrunner-ultrarunner
² https://tantek.com/2019/048/t1/finshed-chabot-redtailridge-30k-pr
likes @beep@follow.ethanmarcotte.com reply at , @molly0xfff@hachyderm.io reply at , @molly0xfff@hachyderm.io toot at , @accordionpolar@indieweb.social reply at , @stevenjmesser@indieweb.social reply at , @nemobis@mamot.fr reply at , @lars@mastodon.social reply at , @KevinMarks@xoxo.zone reply at , @zeldman@front-end.social toot at , and @matthiasott@mastodon.social toot at
@mollywhite.net (@molly0xfff@hachyderm.io) my #IndieWeb blog is https://tantek.com/ with all posts & responses, @tantek.com #federated via #BridgyFed for posts & #fediverse @-@-responses¹, and lastly a time-delayed² Atom feed³ for top-posts only (notes, articles, sometimes photos)
¹ https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
² https://indieweb.org/publish_delay
³ https://tantek.com/updates.atom
New this week: the #IndieWeb community deployed a major modern update to the design, usability, and cross-device support of the https://indieweb.org/ home page and wiki in general! In brief:
* Updated MediaWiki install, updated themes, better mobile device support
* New default theme: Vector (2022), the same as English Wikipedia
* Lots of CSS fixes for content, sidebars, etc.
* Home page content simplification and more pleasing design update
Lots more details on the 2024 homepage and design update project page:
* https://indieweb.org/2024/homepage
This was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices.
Huge thanks in particular to @PaulRobertLloyd.com (@paulrobertlloyd@mastodon.social) for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com (@aaronpk@aaronparecki.com @aaronpk) for all the server-side software updates, PHP/IndieAuth wrangling, and critical devops too.
Go try the new https://indieweb.org/ on any browser, on any device, and share your experience!
#IndieNews
This is post 11 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/046/t1/the-ephemeral-web
→ https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
A couple of days ago in an informal discussion in the #indieweb chat channel about how different people view #Mastodon, the #fediverse, or #Bluesky, and services like #Bridgy & #BridgyFed quite differently, I noted¹ that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web.
There is the publicly viewable #OpenWeb that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web.
Then there are the https APIs that return JSON "web", the thing that I’ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I’ve previously used the more provocative phrase js;dr (JavaScript required, Didn’t Read) for this #ephemeralWeb, yet like many things, it turns out there is a spectrum from ephemeral to persistent.
One popular example on that spectrum that’s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I’m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise² over time.)
For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank:
https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083
Note: only a single Internet Archive snapshot was made of that post.
However if you View Source, you can find the entirety of that #queerAF post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML:
"**TL;DR: Queer[.]AF will close on 2024-04-12** …"
[.] added to avoid linking to a dead domain.
Note: such meta tags in js;dr pages were part of the motivation to specify metaformats.
To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains.
Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral.
When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.
Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body.
All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds.
If you’re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script.
Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site.
This design for longevity is both deliberate, and the default for which the web was designed. It’s also one of the explicit principles in the IndieWeb community.
If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work.
#persistentWeb #longWeb #LongNow
This is post 10 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available
→ https://tantek.com/2024/047/t1/indieweb-major-update-design
Post glossary:
API (Application Programming Interface)
https://indieweb.org/API
Bluesky
https://indieweb.org/Bluesky
Bridgy
https://brid.gy/
Bridgy Fed
https://fed.brid.gy/
ccTLD (country-code top level domain)
https://indieweb.org/ccTLD
curlable
https://indieweb.org/curlable
declarative web
https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb
Internet Archive
https://archive.org/
js;dr (JavaScript required; Didn’t Read)
https://tantek.com/2015/069/t1/js-dr-javascript-required-dead
JSON
https://indieweb.org/JSON
longevity
https://indieweb.org/longevity
Mastodon
https://indieweb.org/Mastodon
metaformats
https://microformats.org/wiki/metaformats
permalink
https://indieweb.org/permalink
principles in the IndieWeb community
https://indieweb.org/principles
progressive enhancement
https://indieweb.org/progressive_enhancement
reply
https://indieweb.org/reply
reply-context
https://indieweb.org/reply-context
robots.txt
https://indieweb.org/robots_txt
social media
https://indieweb.org/social_media
silo
https://indieweb.org/silo
View Source
https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html
¹ https://chat.indieweb.org/2024-02-13#t1707845454695700
² https://indieweb.org/site-deaths
Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.
I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats
Since that post nearly a year ago, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
* Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
* omg.lol profile links by default: https://home.omg.lol/info/profile-items
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
* https://github.com/microformats/h-entry/issues/32
3. #metaformats adoptions, implementations, and iteration
* There was growing practical interest in metaformats, so I updated the spec accordingly
* A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples
* Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues
Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
https://microformats.org/wiki/h-entry
h-review
https://microformats.org/wiki/h-review
link-preview
https://indieweb.org/link-preview
metaformats
https://microformats.org/wiki/metaformats
microformats
https://microformats.org/wiki/
microformats2
https://microformats.org/wiki/microformats2
rel-me
https://microformats.org/wiki/rel-me
#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
→ https://tantek.com/2024/046/t1/the-ephemeral-web
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
→ https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available
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
👍
likes @SutroTower’s reply
I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude
I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.
Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.
Feels like something big has shifted.
The #federated #IndieWeb has replaced another #socialMedia silo use-case.
This is post 7 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
→ https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon
Post glossary:
silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
use-case
https://indieweb.org/use_case
For the #IndieWeb ideals of independence from intermediaries, not requiring corporate platforms or other organizational intermediaries¹, the best systems we have still depend on organizations. However they are all swappable, at will, by the individual:
1. domain names, depend on registrars, which you can switch
2. web hosts, depend on hosting providers, which you can switch
3. internet access, depends on internet service providers, which you can switch
4. web browsing, depends on browsers, which you can switch
5. personal devices, that have choice of web browser and internet access, which you can switch, upgrade, and use multiples of simultaneously
When you can migrate from one provider to another, one device to another, without disruption, without breaking your people-to-people connections, the providers and devices serve you, instead of gatekeeping you.
This freedom to swap, freedom to choose, depends on practical #interoperability across multiple implementations, multiple services. Open standards are the means to encouraging, testing, and verifying this user-feature interoperability across implementations and services.
This is post 6 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
→ https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted
Post glossary:
domain name
https://indieweb.org/personal-domain
interoperability
https://www.w3.org/wiki/Interoperable
web host
https://indieweb.org/web_host
¹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
The #IndieWeb is for everyone, everyone who wants to be part of the world-wide-web of interconnected people. The social internet of people, a network of networks of people, connected peer-to-peer in human-scale groups, communities of locality and affinity.
These peer-to-peer links should not require corporate platforms or other organizational intermediaries, nor should they require depending on developer intermediaries, nor server administrator intermediaries.
This is the "indie" in IndieWeb, independence from intermediaries, not independence from people. Because the "web" in IndieWeb, is yes the Web of the World Wide Web, and it is also the Web of people.
The "indie" in IndieWeb is also the independent agency to opt-into human-scale groups, opt-into peer-to-peer connections, opt-into communities, opt-into publics. As the POSSE page says: “Figure out how you want to fit into the network”.
The "web" in IndieWeb is also an open acknowledgment and acceptance that regardless of what groups, connections, communities, and publics you opt-into, that they are all interconnected in a larger web, that even without connecting, you can accept and respect from a distance.
The IndieWeb is for everyone, everyone who wants independence from organizations, independence of agency to associate, and who embraces the web of humans that want to interconnect, to communicate, to value and respect each other, whether one degree apart or thirty.¹
This is post 5 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites
→ https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
Post glossary:
IndieWeb
https://indieweb.org/
POSSE
https://indieweb.org/POSSE
publics
https://indieweb.org/publics
¹ https://www.theguardian.com/technology/2008/aug/03/internet.email
👍
👍
@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites:
“Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code)
If you are designing or creating any kind of publishing or social features on the web, this post is for you.
It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between.
Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it?
Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they?
When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality?
When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to?
On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions.
Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network?
Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a “social website”?
If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation?
Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations?
Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a “house party protocol”, only letting in those you know, and perhaps allowing them to bring a +1 or 2?
I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites.
This is post 4 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned
→ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
Post glossary:
backfeed
https://indieweb.org/backfeed
blog
https://indieweb.org/blog
blogging
https://indieweb.org/blogging
comments
https://indieweb.org/comments
context collapse
https://indieweb.org/context_collapse
ephemerality
https://indieweb.org/ephemerality
js;dr
https://indieweb.org/js;dr
moderation
https://indieweb.org/moderation
POSSE
https://indieweb.org/POSSE
posts
https://indieweb.org/posts
publics
https://indieweb.org/publics
reply
https://indieweb.org/reply
Vouch
https://indieweb.org/Vouch
Webmention
https://indieweb.org/Webmention
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
→ https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites
Still remembering #aaronsw, eleven years, two days ago.
Previously, previously, previously:
* https://tantek.com/2017/011/t3/moment-remember-aaronsw
* https://tantek.com/2016/011/t4/three-years-lost-aaronsw
* https://tantek.com/2015/011/t1/still-missing-aaronsw
* https://tantek.com/2013/059/t1/doj-prosecutors-aaronsw-fear-face-saving-not-justice
* https://tantek.com/2013/029/t1/aaronsw-internet-archive-memorial-videos-speakers
* https://tantek.com/2013/026/b1/remembering-aaron-swartz-part-2-hacking-essence-advancing-humanity
* https://tantek.com/2013/025/b1/remembering-aaron-swartz-part-1-you-should-blog-that
#2013_011 #aaronswartz
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:
🎁 71 total gifts
📄 32 new IndieWeb wiki pages
📜 8 posts on improving blogs, IndieWeb specs, and event summaries
💻 7 Online meetups: IndieWeb CreateFest & 6 Homebrew Website Clubs
🧩 6 plugin updates: #Elgg IndieWeb & 5 #WordPress plugins updates
📫 5 This Week In The IndieWeb newsletters
🧱 4 library updates: new web components, #microformats2 parser update
🌉 3 Bridgy Fed updates & improvements
🎪 2 days of #IndieWebCamp San Diego
📚 1 indiebookclub new year in review overview feature
📽 1 IndieWeb movie viewings aggregator
⌨️ 1 personal predictive text engine
🧶 1 #Threads federating out #ActivityPub (followable by #BridgyFed)
Gift were shared by:
👥 21 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
→ https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned
@Tmichellemoore.com (@tmichellemoore@mastodon.social) yes! You can do it!
I created a section on the #100Days page specifically for #100Posts projects:
https://indieweb.org/100_days#100_posts_projects
Add yourself and join in!
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
