Shakedown Social

Tantek ÇelikI really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent: * Paolo Feadin: <a class="" href="https://www.feadin.eu/en/posts/tomorrowland" rel="nofollow noopener" target="_blank">https://www.feadin.eu/en/posts/tomorrowland</a> * Thomas Vander Wal: <a class="" href="https://vanderwal.net/random/entrysel.php?blog=2119" rel="nofollow noopener" target="_blank">https://vanderwal.net/random/entrysel.php?blog=2119</a> * gRegor Morrill: <a class="" href="https://gregorlove.com/2025/05/tomorrowland/" rel="nofollow noopener" target="_blank">https://gregorlove.com/2025/05/tomorrowland/</a> * Benji: <a class="" href="https://www.benji.dog/watched/1748757918-tomorrowland-2015/" rel="nofollow noopener" target="_blank">https://www.benji.dog/watched/1748757918-tomorrowland-2015/</a> * James: <a class="" href="https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club" rel="nofollow noopener" target="_blank">https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club</a> As promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein: * <a class="" href="https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news" rel="nofollow noopener" target="_blank">https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news</a> * <a class="" href="https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association" rel="nofollow noopener" target="_blank">https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association</a> * <a class="" href="https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris" rel="nofollow noopener" target="_blank">https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris</a> * <a class="" href="https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland" rel="nofollow noopener" target="_blank">https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland</a> I rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post.   Previously: <a class="" href="https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland" rel="nofollow noopener" target="_blank">https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland</a> <a class="" href="https://indieweb.social/tags/TomorrowlandFilm" rel="nofollow noopener" target="_blank">#TomorrowlandFilm</a> <a class="" href="https://indieweb.social/tags/BeforeTomorrowland" rel="nofollow noopener" target="_blank">#BeforeTomorrowland</a> <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a> <a class="" href="https://indieweb.social/tags/IndieWebMovieClub" rel="nofollow noopener" target="_blank">#IndieWebMovieClub</a> This is post 12 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland" rel="nofollow noopener" target="_blank">https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland</a> → 🔮

Tantek ÇelikYesterday <a class="" href="https://last.fm/" rel="nofollow noopener" target="_blank">https://last.fm/</a> (<a class="h-cassis-username" href="https://twitter.com/lastfm" rel="nofollow noopener" target="_blank">@lastfm</a>) emailed their year in review reports, which they called <a class="" href="https://indieweb.social/tags/Playback24" rel="nofollow noopener" target="_blank">#Playback24</a> and Last.Year. Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.<a href="https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24#t5_r1_note-1" rel="nofollow noopener" target="_blank">¹</a> They’re also available on the web, without requiring a native mobile app to view. Mine is here: <a class="" href="https://www.last.fm/user/tantekc/listening-report/year" rel="nofollow noopener" target="_blank">https://www.last.fm/user/tantekc/listening-report/year</a> The page title calls it your <a class="" href="https://indieweb.social/tags/YearInMusic" rel="nofollow noopener" target="_blank">#YearInMusic</a>, and the URL your <a class="" href="https://indieweb.social/tags/ListeningReport" rel="nofollow noopener" target="_blank">#ListeningReport</a>. It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks. Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year. The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal <a class="" href="https://indieweb.social/tags/indieweb" rel="nofollow noopener" target="_blank">#indieweb</a> site. For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than <a class="" href="https://indieweb.social/tags/Spotify" rel="nofollow noopener" target="_blank">#Spotify</a>’s <a class="" href="https://indieweb.social/tags/Wrapped" rel="nofollow noopener" target="_blank">#Wrapped</a>. That’s step 1. Step 2 is figuring out a good way to blog at least some of it. This is post 5 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> <a class="" href="https://indieweb.social/tags/LastFM" rel="nofollow noopener" target="_blank">#LastFM</a> <a class="" href="https://indieweb.social/tags/YearInReview" rel="nofollow noopener" target="_blank">#YearInReview</a> ← <a class="" href="https://tantek.com/2025/002/t1/indieweb-third-place-community" rel="nofollow noopener" target="_blank">https://tantek.com/2025/002/t1/indieweb-third-place-community</a> → 🔮 Glossary: scrobble   <a class="" href="https://indieweb.org/scrobble" rel="nofollow noopener" target="_blank">https://indieweb.org/scrobble</a> year in review   <a class="" href="https://indieweb.org/year_in_review" rel="nofollow noopener" target="_blank">https://indieweb.org/year_in_review</a> <a href="https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24#t5_r1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://tantek.com/2025/001/t2/first-new-year-review-prior" rel="nofollow noopener" target="_blank">https://tantek.com/2025/001/t2/first-new-year-review-prior</a>

Tantek Çelik⚠️ .io domain<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-1" rel="nofollow noopener" target="_blank">¹</a> likely being phased-out<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-2" rel="nofollow noopener" target="_blank">²</a> — seven suggested steps Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you: * <a class="" href="https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands" rel="nofollow noopener" target="_blank">https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands</a> It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-3" rel="nofollow noopener" target="_blank">³</a>), so here are my suggested steps to take depending on your usage of .io domains: 1. Avoid buying new .io domains (or making plans with existing ones; sell if you can) 2. If you currently run a .io service<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-4" rel="nofollow noopener" target="_blank">⁴</a> (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects) 3. If you have a personal site on a .io domain<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-5" rel="nofollow noopener" target="_blank">⁵</a> or subdomain, make your own transition plan, and perhaps post about how others should link to your posts 4. If you are using someone else’s .io domain to publish (like <a class="" href="https://indieweb.social/tags/GitHubPages" rel="nofollow noopener" target="_blank">#GitHubPages</a><a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-6" rel="nofollow noopener" target="_blank">⁶</a>), make a transition plan to publish elsewhere and leave a forwarding note and link behind 5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain 6. Similarly if your site accepts <a class="" href="https://indieweb.social/tags/WebSignIn" rel="nofollow noopener" target="_blank">#WebSignIn</a> logins (via <a class="" href="https://indieweb.social/tags/IndieAuth" rel="nofollow noopener" target="_blank">#IndieAuth</a>, <a class="" href="https://indieweb.social/tags/RelMeAuth" rel="nofollow noopener" target="_blank">#RelMeAuth</a>, or even <a class="" href="https://indieweb.social/tags/OpenID" rel="nofollow noopener" target="_blank">#OpenID</a>), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5 7. If you have posts (or a whole <a class="" href="https://indieweb.social/tags/indieweb" rel="nofollow noopener" target="_blank">#indieweb</a> site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive) And of course, post about your <a class="" href="https://indieweb.social/tags/dotIO" rel="nofollow noopener" target="_blank">#dotIO</a> plans. Glossary Domain  <a class="" href="https://indieweb.org/domain" rel="nofollow noopener" target="_blank">https://indieweb.org/domain</a> IndieAuth  <a class="" href="https://indieweb.org/IndieAuth" rel="nofollow noopener" target="_blank">https://indieweb.org/IndieAuth</a> Internet Archive  <a class="" href="https://web.archive.org/" rel="nofollow noopener" target="_blank">https://web.archive.org/</a> OpenID  <a class="" href="https://indieweb.org/OpenID" rel="nofollow noopener" target="_blank">https://indieweb.org/OpenID</a> Redirect  <a class="" href="https://indieweb.org/redirect" rel="nofollow noopener" target="_blank">https://indieweb.org/redirect</a> RelMeAuth  <a class="" href="https://indieweb.org/RelMeAuth" rel="nofollow noopener" target="_blank">https://indieweb.org/RelMeAuth</a> Web sign-in  <a class="" href="https://indieweb.org/Web_sign-in" rel="nofollow noopener" target="_blank">https://indieweb.org/Web_sign-in</a> References: <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://indieweb.org/.io" rel="nofollow noopener" target="_blank">https://indieweb.org/.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-2" rel="nofollow noopener" target="_blank">²</a> <a class="" href="https://en.wikipedia.org/wiki/.io#Phasing_Out" rel="nofollow noopener" target="_blank">https://en.wikipedia.org/wiki/.io#Phasing_Out</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-3" rel="nofollow noopener" target="_blank">³</a> <a class="" href="https://en.wikipedia.org/wiki/.cs" rel="nofollow noopener" target="_blank">https://en.wikipedia.org/wiki/.cs</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-4" rel="nofollow noopener" target="_blank">⁴</a> E.g. <a class="" href="https://indieweb.org/webmention.io" rel="nofollow noopener" target="_blank">https://indieweb.org/webmention.io</a> or <a class="" href="https://indieweb.org/granary.io" rel="nofollow noopener" target="_blank">https://indieweb.org/granary.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-5" rel="nofollow noopener" target="_blank">⁵</a> E.g. <a class="" href="https://indieweb.org/werd.io" rel="nofollow noopener" target="_blank">https://indieweb.org/werd.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-6" rel="nofollow noopener" target="_blank">⁶</a> <a class="" href="https://indieweb.org/github.io" rel="nofollow noopener" target="_blank">https://indieweb.org/github.io</a> This is post 25 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful" rel="nofollow noopener" target="_blank">https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful</a> → 🔮

Tantek ÇelikYesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal <a class="" href="https://indieweb.social/tags/indieweb" rel="nofollow noopener" target="_blank">#indieweb</a> sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken. Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits. The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel<a href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker#t5XD1_note-1" rel="nofollow noopener" target="_blank">¹</a>. Figured it was worth writing up rather than waiting to implement it. Basic idea: You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain). This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store). User benefit: If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive/mirror copy instead, thus providing a one-click ability for the reader to “soft-repair” any otherwise apparently broken links to your site. Personal site publisher benefits: Having such a service worker that automatically provides your readers links to where they can view your content on an archive or mirror means you can go on vacation or otherwise step away from your personal site, knowing that if it does go down, (at least prior) site visitors will still have a way to click-through and view your published content. Additional enhancements: Ideally any archive or mirror copies would use rel=canonical to link back to the page on your domain, so any crawlers or search engines could automatically prefer your original page, or browsers could offer the user a choice to “View original”. You can do that by including a rel=canonical link in all your original pages, so when they are archived or mirrored, those copies automatically include a rel=canonical link back to your original page or post. The simplest implementation would be to ping the Internet Archive to save<a href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker#t5XD1_note-2" rel="nofollow noopener" target="_blank">²</a> your page or post upon publishing it. You could also add code to your site to explicitly generate a static mirror of your pages, perhaps with an SSG or crawler like Spiderpig, to a GitHub repo, which is then auto-served as GitHub static pages, perhaps on its own domain yet at the same paths as your original pages (to make it trivial to generate such mirror links automatically). If you’re using links to the Internet Archive, you can generate them automatically by prefixing your page URL with <a class="" href="https://web.archive.org/web/*/" rel="nofollow noopener" target="_blank">https://web.archive.org/web/*/</a> e.g. this post: <a class="" href="https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-worker" rel="nofollow noopener" target="_blank">https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-worker</a> Possible generic library: It may be possible to write this minimum interesting service worker (e.g. misv.js) as a generic (rather than site-specific) service worker that literally anyone with a personal site could “install” as is (a JS file, an HTML file, and a one-line script tag in their site-wide footer) and it would figure everything out from the context it is running in, unchanged (zero configuration necessary). This is post 14 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton" rel="nofollow noopener" target="_blank">https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton</a> → 🔮 Post glossary: GitHub static pages   <a class="" href="https://indieweb.org/GitHub_Pages" rel="nofollow noopener" target="_blank">https://indieweb.org/GitHub_Pages</a> HTML   <a class="" href="https://indieweb.org/HTML" rel="nofollow noopener" target="_blank">https://indieweb.org/HTML</a> JS   <a class="" href="https://indieweb.org/js" rel="nofollow noopener" target="_blank">https://indieweb.org/js</a> rel-canonical   <a class="" href="https://indieweb.org/rel-canonical" rel="nofollow noopener" target="_blank">https://indieweb.org/rel-canonical</a> service worker   <a class="" href="https://indieweb.org/service_worker" rel="nofollow noopener" target="_blank">https://indieweb.org/service_worker</a> Spiderpig   <a class="" href="https://indieweb.org/Spiderpig" rel="nofollow noopener" target="_blank">https://indieweb.org/Spiderpig</a> SSG   <a class="" href="https://indieweb.org/SSG" rel="nofollow noopener" target="_blank">https://indieweb.org/SSG</a>   References: <a href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker#t5XD1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://chat.indieweb.org/dev/2024-05-29#t1717006352142600" rel="nofollow noopener" target="_blank">https://chat.indieweb.org/dev/2024-05-29#t1717006352142600</a> <a href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker#t5XD1_ref-2" rel="nofollow noopener" target="_blank">²</a> <a class="" href="https://indieweb.org/Internet_Archive#Trigger_an_Archive" rel="nofollow noopener" target="_blank">https://indieweb.org/Internet_Archive#Trigger_an_Archive</a>

Tantek ÇelikA couple of days ago in an informal discussion in the <a class="" href="https://indieweb.social/tags/indieweb" rel="nofollow noopener" target="_blank">#indieweb</a> chat channel about how different people view <a class="" href="https://indieweb.social/tags/Mastodon" rel="nofollow noopener" target="_blank">#Mastodon</a>, the <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a>, or <a class="" href="https://indieweb.social/tags/Bluesky" rel="nofollow noopener" target="_blank">#Bluesky</a>, and services like <a class="" href="https://indieweb.social/tags/Bridgy" rel="nofollow noopener" target="_blank">#Bridgy</a> & <a class="" href="https://indieweb.social/tags/BridgyFed" rel="nofollow noopener" target="_blank">#BridgyFed</a> quite differently, I noted<a href="https://tantek.com/2024/046/t1/the-ephemeral-web#t5VU1_note-1" rel="nofollow noopener" target="_blank">¹</a> 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 <a class="" href="https://indieweb.social/tags/OpenWeb" rel="nofollow noopener" target="_blank">#OpenWeb</a> that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being <a class="" href="https://indieweb.social/tags/curlable" rel="nofollow noopener" target="_blank">#curlable</a>, 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 <a class="" href="https://indieweb.social/tags/ephemeralWeb" rel="nofollow noopener" target="_blank">#ephemeralWeb</a>, 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<a href="https://tantek.com/2024/046/t1/the-ephemeral-web#t5VU1_note-2" rel="nofollow noopener" target="_blank">²</a> over time.) For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank: <a class="" href="https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083" rel="nofollow noopener" target="_blank">https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083</a> Note: only a single Internet Archive snapshot was made of that post. However if you View Source, you can find the entirety of that <a class="" href="https://indieweb.social/tags/queerAF" rel="nofollow noopener" target="_blank">#queerAF</a> 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. <a class="" href="https://indieweb.social/tags/persistentWeb" rel="nofollow noopener" target="_blank">#persistentWeb</a> <a class="" href="https://indieweb.social/tags/longWeb" rel="nofollow noopener" target="_blank">#longWeb</a> <a class="" href="https://indieweb.social/tags/LongNow" rel="nofollow noopener" target="_blank">#LongNow</a> This is post 10 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available" rel="nofollow noopener" target="_blank">https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available</a> → 🔮 Post glossary: API (Application Programming Interface)   <a class="" href="https://indieweb.org/API" rel="nofollow noopener" target="_blank">https://indieweb.org/API</a> Bluesky   <a class="" href="https://indieweb.org/Bluesky" rel="nofollow noopener" target="_blank">https://indieweb.org/Bluesky</a> Bridgy   <a class="" href="https://brid.gy/" rel="nofollow noopener" target="_blank">https://brid.gy/</a> Bridgy Fed   <a class="" href="https://fed.brid.gy/" rel="nofollow noopener" target="_blank">https://fed.brid.gy/</a> ccTLD (country-code top level domain)   <a class="" href="https://indieweb.org/ccTLD" rel="nofollow noopener" target="_blank">https://indieweb.org/ccTLD</a> curlable   <a class="" href="https://indieweb.org/curlable" rel="nofollow noopener" target="_blank">https://indieweb.org/curlable</a> declarative web   <a class="" href="https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb" rel="nofollow noopener" target="_blank">https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb</a> Internet Archive   <a class="" href="https://archive.org/" rel="nofollow noopener" target="_blank">https://archive.org/</a> js;dr (JavaScript required; Didn’t Read)   <a class="" href="https://tantek.com/2015/069/t1/js-dr-javascript-required-dead" rel="nofollow noopener" target="_blank">https://tantek.com/2015/069/t1/js-dr-javascript-required-dead</a> JSON   <a class="" href="https://indieweb.org/JSON" rel="nofollow noopener" target="_blank">https://indieweb.org/JSON</a> longevity   <a class="" href="https://indieweb.org/longevity" rel="nofollow noopener" target="_blank">https://indieweb.org/longevity</a> Mastodon   <a class="" href="https://indieweb.org/Mastodon" rel="nofollow noopener" target="_blank">https://indieweb.org/Mastodon</a> metaformats   <a class="" href="https://microformats.org/wiki/metaformats" rel="nofollow noopener" target="_blank">https://microformats.org/wiki/metaformats</a> permalink   <a class="" href="https://indieweb.org/permalink" rel="nofollow noopener" target="_blank">https://indieweb.org/permalink</a> principles in the IndieWeb community   <a class="" href="https://indieweb.org/principles" rel="nofollow noopener" target="_blank">https://indieweb.org/principles</a> progressive enhancement   <a class="" href="https://indieweb.org/progressive_enhancement" rel="nofollow noopener" target="_blank">https://indieweb.org/progressive_enhancement</a> reply   <a class="" href="https://indieweb.org/reply" rel="nofollow noopener" target="_blank">https://indieweb.org/reply</a> reply-context   <a class="" href="https://indieweb.org/reply-context" rel="nofollow noopener" target="_blank">https://indieweb.org/reply-context</a> robots.txt   <a class="" href="https://indieweb.org/robots_txt" rel="nofollow noopener" target="_blank">https://indieweb.org/robots_txt</a> social media   <a class="" href="https://indieweb.org/social_media" rel="nofollow noopener" target="_blank">https://indieweb.org/social_media</a> silo   <a class="" href="https://indieweb.org/silo" rel="nofollow noopener" target="_blank">https://indieweb.org/silo</a> View Source   <a class="" href="https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html" rel="nofollow noopener" target="_blank">https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html</a> <a href="https://tantek.com/2024/046/t1/the-ephemeral-web#t5VU1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://chat.indieweb.org/2024-02-13#t1707845454695700" rel="nofollow noopener" target="_blank">https://chat.indieweb.org/2024-02-13#t1707845454695700</a> <a href="https://tantek.com/2024/046/t1/the-ephemeral-web#t5VU1_ref-2" rel="nofollow noopener" target="_blank">²</a> <a class="" href="https://indieweb.org/site-deaths" rel="nofollow noopener" target="_blank">https://indieweb.org/site-deaths</a>

Tantek ÇelikI felt the <a class="" href="https://indieweb.social/tags/earthquake" rel="nofollow noopener" target="_blank">#earthquake</a> here in <a class="" href="https://indieweb.social/tags/SanFrancisco" rel="nofollow noopener" target="_blank">#SanFrancisco</a>. 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 <a class="" href="https://indieweb.social/tags/earthquakes" rel="nofollow noopener" target="_blank">#earthquakes</a> are the last use-case for <a class="" href="https://indieweb.social/tags/Twitter" rel="nofollow noopener" target="_blank">#Twitter</a> because yes I reflexively checked it and did see posts about it from folks, including a few friends. Then I checked <a class="" href="https://indieweb.social/tags/earthquake" rel="nofollow noopener" target="_blank">https://indieweb.social/tags/earthquake</a> and it has plenty of recent <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a> posts about the earthquake, several <a class="" href="https://sfba.social" rel="nofollow noopener" target="_blank">@sfba.social</a>. Feels like something big has shifted. The <a class="" href="https://indieweb.social/tags/federated" rel="nofollow noopener" target="_blank">#federated</a> <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a> has replaced another <a class="" href="https://indieweb.social/tags/socialMedia" rel="nofollow noopener" target="_blank">#socialMedia</a> silo use-case. This is post 7 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable" rel="nofollow noopener" target="_blank">https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable</a> → 🔮 Post glossary: silo   <a class="" href="https://indieweb.org/silo" rel="nofollow noopener" target="_blank">https://indieweb.org/silo</a> social media   <a class="" href="https://indieweb.org/social_media" rel="nofollow noopener" target="_blank">https://indieweb.org/social_media</a> use-case   <a class="" href="https://indieweb.org/use_case" rel="nofollow noopener" target="_blank">https://indieweb.org/use_case</a>

Tantek ÇelikTime to begin again: restarting my <a class="" href="https://indieweb.social/tags/100Days" rel="nofollow noopener" target="_blank">#100Days</a> of <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a> project for 2024, as a <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar! Last year I completed 48 out of a planned 100 posts in my <a class="" href="https://indieweb.social/tags/100DaysOfIndieWeb" rel="nofollow noopener" target="_blank">#100DaysOfIndieWeb</a> project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all. Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes<a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_note-1" rel="nofollow noopener" target="_blank">¹</a>. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a <a class="" href="https://indieweb.social/tags/Twitter" rel="nofollow noopener" target="_blank">#Twitter</a> account to a <a class="" href="https://indieweb.social/tags/Mastodon" rel="nofollow noopener" target="_blank">#Mastodon</a> (or other <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a>) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web. In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic <a class="" href="https://indieweb.social/tags/POSSE" rel="nofollow noopener" target="_blank">#POSSE</a> publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place). I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm<a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_note-2" rel="nofollow noopener" target="_blank">²</a> isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it. On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December. We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023<a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_note-3" rel="nofollow noopener" target="_blank">³</a>, the first time we successfully filled out the whole month since the 2018 IndieWeb Challenge<a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_note-4" rel="nofollow noopener" target="_blank">⁴</a>, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar. By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts<a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_note-5" rel="nofollow noopener" target="_blank">⁵</a> of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here. Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done! Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. <a class="" href="https://indieweb.social/tags/ShowDontTell" rel="nofollow noopener" target="_blank">#ShowDontTell</a> This is post 1 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← ✨ → 🔮 Post glossary: API   <a class="" href="https://indieweb.org/API" rel="nofollow noopener" target="_blank">https://indieweb.org/API</a> POSSE   <a class="" href="https://indieweb.org/POSSE" rel="nofollow noopener" target="_blank">https://indieweb.org/POSSE</a> silo   <a class="" href="https://indieweb.org/silo" rel="nofollow noopener" target="_blank">https://indieweb.org/silo</a> <a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://tantek.com/2023/001/t1/own-your-notes" rel="nofollow noopener" target="_blank">https://tantek.com/2023/001/t1/own-your-notes</a> <a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_ref-2" rel="nofollow noopener" target="_blank">²</a> <a class="" href="https://indieweb.org/algorithmic_feed" rel="nofollow noopener" target="_blank">https://indieweb.org/algorithmic_feed</a> <a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_ref-3" rel="nofollow noopener" target="_blank">³</a> <a class="" href="https://indieweb.org/2023-12-indieweb-gift-calendar" rel="nofollow noopener" target="_blank">https://indieweb.org/2023-12-indieweb-gift-calendar</a> <a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_ref-4" rel="nofollow noopener" target="_blank">⁴</a> <a class="" href="https://indieweb.org/2018-12-indieweb-challenge" rel="nofollow noopener" target="_blank">https://indieweb.org/2018-12-indieweb-challenge</a> <a href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar#t5Ui1_ref-5" rel="nofollow noopener" target="_blank">⁵</a> <a class="" href="https://tantek.com/2023/365/t2/no-large-language-model-llm-used" rel="nofollow noopener" target="_blank">https://tantek.com/2023/365/t2/no-large-language-model-llm-used</a>

Recent searches

Search options

Administered by:

Server stats:

#100PostsOfIndieWeb