Show Navigation
Notices tagged with 100posts
-
š 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
ā š®
-
I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film āTomorrowlandā. Ordered from earliest to most recent:
* Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland
* Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119
* gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/
* Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/
* James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club
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:
* https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news
* https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association
* https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris
* https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland
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: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland
#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub
This is post 12 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland
ā š®
-
Welcome to the May 2025 edition of IndieWeb Movie Club!
As your host for this monthĀ¹, I invite you to (re)watch the film āTomorrowlandā (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment!
āBefore Tomorrowlandā (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so itās fine to read before watching.
#Tomorrowland is available in various physical media formats, and via streaming on DisneyPlusĀ². 130 minutes, rated PG.
This month is the 10th anniversary of Tomorrowlandās release.
The world was quite different in 2015.
I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I wonāt link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015!
Iām curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland.
If you would like to participate in this monthās IndieWeb Movie Club:
* optional: read the prequel book
* watch the film
* blog a readĀ³ (for the book), watchā“, reviewāµ, or even a simple noteā¶ post of your impressions, or some or all the above and link to this post
If you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmentionā· from your post, or drop a link in the IndieWeb chat discussion channelāø and @-mention me.
Since this is an IndieWeb community activity, please both follow the Code of Conductā¹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly.
Happy reading, watching, and dreaming!
#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub
This is post 11 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/077/t1/what-are-words-for-blogging
ā š®
References:
Ā¹ https://indieweb.org/IndieWeb_Movie_Club#2025
Ā² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-addb-4c66-91a6-136325e6ecf7
Ā³ https://indieweb.org/read
ā“ https://indieweb.org/watch
āµ https://indieweb.org/review
ā¶ https://indieweb.org/note
ā· https://indieweb.org/Webmention
āø https://indieweb.org/discuss#indieweb
ā¹ https://indieweb.org/code-of-conduct
-
āTell me, what are words for?ā They are for blogging!
Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like āromantic 80s tuesday morningā, and the 1982 song āWordsāĀ¹ by the band Missing Persons came on.
When we heard this lyric:
š¶ What are words for when no one listens? š¶
I remarked half-jokingly in response:
Words are for blogging, whether anyone is listening, reading, or not.
Another participant noted that blogging sometimes feels like screaming into the void.
I noted it doesnāt matter if anyone is reading (or listening), itās fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future.
When I write a post itās often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of āputting it on the permanent recordā (since nearly everything blogged is promptly indexed and archived.) with a permalink.
The lyrics have some quite prescient bits, like this:
āNo one notices, I think I'll dye my hair blue
Ā Media overload bombarding you with action
Ā Itās getting near impossible to cause distractionā
Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing.
Rewriting the lyrics as a parody could be a fun project, e.g.:
š¶ What are blogs for when no one reads them? š¶
some existing lyrics barely need any edits, like:
āItās like the feeling at the end of the page
Ā When you realize you don't know what you just readā
perhaps an exercise for the reader for now.
Previously: āInbox Zeroā (parody of The Fixx āSaved by ZeroāĀ²)
* https://tantek.com/w/InboxZero (2009-01-29 https://twitter.com/t/status/1160324190)
This is post 10 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity
ā š®
Glossary
blog
Ā https://indieweb.org/blog
blogging
Ā https://indieweb.org/blogging
permalink
Ā https://indieweb.org/permalink
why blog
Ā https://indieweb.org/why_post
References
Ā¹ https://libre.fm/artist/Missing+Persons/track/Words (YouTube link inside)
Ā² https://libre.fm/artist/The+Fixx/track/Saved+by+Zero (YouTube link inside)
-
Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary:
1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers.
2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account.
3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts.
Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity
Next time: entropy is your friend in security.
If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client.
You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page.
You can also read my article blog posts and those from other Mozillians on the Mozilla Planet:
* https://planet.mozilla.org/
If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer.
This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security
ā https://tantek.com/2025/020/t1/seek-2024-year-in-review
ā š®
Glossary
article post
Ā https://indieweb.org/article
Atom
Ā https://indieweb.org/Atom
content delivery network
Ā https://indieweb.org/content_delivery_network
cybersecurity
Ā https://en.wikipedia.org/wiki/cybersecurity
DNS
Ā https://indieweb.org/DNS
domain registrar
Ā https://indieweb.org/domain_registrar
entropy
Ā https://en.wikipedia.org/wiki/Entropy_(information_theory)
feed reader
Ā https://indieweb.org/feed_reader
h-feed
Ā https://indieweb.org/h-feed
MFA / 2FA
Ā https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authentication
mobile number for MFA
Ā https://indieweb.org/SMS#Criticism
note post
Ā https://indieweb.org/note
social reader
Ā https://indieweb.org/social_reader
web host
Ā https://indieweb.org/web_hosting
-
My Seek 2024 Year in Review:
* 141 new species observed, of those, the top three kinds:
Ā * 79 plants
Ā * 20 insects
Ā * 16 fungi
* 56 challenge badges earned
June was the month I observed the most new species in 2024, followed by March, and then July.
Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.
Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know Iāll be able to search and look up in the future.
Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.
Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection).
Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post.
In some ways itās like Pokemon Go, except based on finding and collecting observations of real living things.
I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one Iāve seen elsewhere, perhaps around home, or is it a slightly different species?
I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it.
Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection.
Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.
This is post 8 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp
ā https://tantek.com/2025/012/t1/eight-years-webmention
ā š®
Glossary:
login wall
Ā https://indieweb.org/login_wall
offline first
Ā https://indieweb.org/offline_first
-
š Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/
As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.
The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, has long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).
There are multiple considerations to keep in mind when displaying such external content.
Two examples of external content are images (e.g. peopleās icons or profile images from the author of a comment) and text (e.g. peopleās names or the text of their comments).
For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.
If you accept Webmentions from arbitrary sources, thereās no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.
For external text, one thing we discovered in recent IndieWeb chatĀ¹ is that someoneās comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text adjacent.
Fortunately there is a CSS property, 'unicode-bidi', that can be used to isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:
<span style="unicode-bidi: isolate;">parsed text here</span>
Though even better would be use of a generic HTML class name indicating the semantic:
<span class="external-text">parsed text here</span>
and then a CSS rule in your style sheet to add that property (and any others you want for external text)
.external-text { unicode-bidi: isolate; }
This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb
ā https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web
ā š®
Glossary
HTML class name
Ā https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
IndieWeb chat
Ā https://indieweb.org/discuss
pixelate
Ā https://indieweb.org/pixelated
small pieces, loosely joined
Ā https://www.smallpieces.com/
Unicode directional formatting characters
Ā https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting
unicode-bidi CSS property
Ā https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi Ā
References
Ā¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900
-
The team @micro.blog have done it again.
They soft-launched https://micro.one yesterdayĀ¹.
This may be the most accessible onramp to the open social web ever.
Cost: $1 a month. Yes you read correctly.
This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content onlineĀ².
Stop posting in someone elseās garageĀ³.
Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.
Of course you can bring your own domain name. Additionally:
* blog posts, naturally, both articles and microblogging notes
* photos
* podcasting
* custom themes
* web-clients and native mobile posting clients
* WordPress, Tumblr, Mastodon, Medium import
More details (and alternatives) at https://micro.one/about/pricing
And yes, it interoperates with the open #socialWeb, including:
* #ActivityPub support, #Mastodon and #fediverse compatibility
* #IndieAuth to sign-in to third-party apps
* #microformats support in all built-in themes
* #Webmention for sending and receiving replies across websites
* #Micropub standard posting API, supporting dozens of clients
* #Microsub standard timeline API, supporting social readers
More #indieweb support details at https://micro.one/about/indieweb
Did I mention the the superb micro.blog (and micro.one) Community Guidelines?
* https://help.micro.blog/t/community-guidelines/39
Well done @manton.org and team.
This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb
ā https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24
ā š®
Glossary
IndieAuth
Ā https://indieweb.org/IndieAuth
microformats
Ā https://microformats.org/wiki/microformats
Micropub
Ā https://indieweb.org/Micropub
Microsub
Ā https://indieweb.org/Microsub
Webmention
Ā https://indieweb.org/Webmention
Ā¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html
Ā² https://tantek.com/2025/001/t1/15-years-notes-my-site-first
Ā³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
-
Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 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.Ā¹
Theyāre also available on the web, without requiring a native mobile app to view.
Mine is here: https://www.last.fm/user/tantekc/listening-report/year
You can find yours (if youāre a last.fm user) by going here:
* https://www.last.fm/user/_/listening-report/year
The page title calls it your #YearInMusic, and the URL your #ListeningReport.
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 #indieweb 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 #Spotifyās #Wrapped.
Thatās step 1. Step 2 is figuring out a good way to blog at least some of it.
This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview
ā https://tantek.com/2025/002/t1/indieweb-third-place-community
ā š®
Glossary:
scrobble
Ā https://indieweb.org/scrobble
year in review
Ā https://indieweb.org/year_in_review
Ā¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
-
The #indieweb is more than #independence. Itās also a web, of both personal sites and āthird placeā sites like aggregators, bridges, proxies, directories, indexes, and other community sites.
Broadly speaking, such āthird placeā sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia.
Similarly, the most obvious āthird placeā in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/.
We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like:
* @snarfed.orgās https://brid.gy/ and https://fed.brid.gy/
* @aaronparecki.comās https://webmention.io/ and many others
* @martymcgui.reās https://xn--sr8hvo.ws/ (IndieWeb Webring)
* @gregorlove.comās https://indiebookclub.biz/
* @mat.tlās https://libre.fm/
and Iām sure many more Iām forgetting.
All these services respect your data and your ownership of it. #ownYourData
All these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance.
The web part of the indieweb complements, connects, and strengthens the indie part.
This is post 4 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save
ā š®
-
When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site.
Speaking of year in reviewsĀ¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears after the 6th!Ā²) and save it locally so you can write and publish your own year in sport.
How to find your Strava: Year in Sport 2024
For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone.
From the mobile app home screen, tap the "š You" button in the lower right corner.
At the top you should see:
"Play back your 2024" heading with an orange button:
[ See your Year in Sport ]
Tap that button.
Saving Seven Summary Segments
You should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time.
For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format.
For each item in the carousel (if there is more than one)
* tap the item in the carousel
* tap the "[ā] More" button at the bottom.
* scroll down the list of options up a bit
* tap "Save Video [ā]" or "Save Image [ā]" option to store it locally on your mobile.
The seventh "segment" is your overall summary, and shows all your sports combined.
Save it (as an image as noted above), then
* tap the "āļø Ā Customize" button
* choose an individual sport (e.g. "š Run")
* tap "Save changes"
* save that image (as above)
* tap customize again
* choose the next sport (e.g. "š² Ā Ride")
* save changes again
* save image again
Strava seemingly only reports summaries of (up to?) two or your sports it appears. Those were Run (presumably all running, street and trail) and Ride for me.
Cleanup Your Screenshots
After having saved all the videos/images for each "segment", you can:
* go back to your mobileās top level Photos app/stream
* delete the screenshots
You should see all the videos/images you've saved. If anything is missing, go back to the previous steps and save them again, then remove any duplicates as necessary.
Post Your Year In Sport
Go through your saved videos/images, and either post on your own site as-is, or use your mobileās built-in image OCR to copy the text bits into a plain personal year in sport note summary post on your own site. Or some combination of both if you prefer.
Add other summaries of your activities and sports as you see fit, like:
* info on other sports (beyond running and biking), e.g. yoga, weight-lifting, bouldering etc.
Ā * total days active (of 366)
Ā * total distance (if applicable)
Ā * total elevation (if applicable)
Ā * total time
* number of races you ran, biked etc. (and finished, if not the same)
* number of miles (or km) you raced (per sport and/or total overall)
* number of (or full set of) awards or trophies you earned at races
* any other stats that you think of that seem interesting to you
For each of these annual numbers, you could also compute (optionally display) the percentage change from 2023, if you happen to have those numbers around.
This is also a good reason to at least total up these numbers for 2024, whether you publish them or not, for figuring out the percentage change in 2025 next year.
When you publish your own year in sport post, might as well re-use the existing #YearInSport hashtag too.
I have already saved all the videos/images from my own Strava Year In Sport, and as I assemble the pieces into my own post, Iāll take more notes, and add to the IndieWeb year in review pageĀ³ accordingly.
This post could also be improved with a few screenshots for a few of the steps above. I figured Iād publish my notes first to hopefully help some people sooner (since the Strava Year In Sport will disappear after January 6th as mentioned!). I might upload a few screenshots to the IndieWeb wiki later as well.
#yearInReview #ownYourYearInReview
This is post 3 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/001/t2/first-new-year-review-prior
ā š®
Glossary:
hashtag
Ā https://indieweb.org/hashtag
own your data
Ā https://indieweb.org/own_your_data
Ā¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
Ā² https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM
Ā³ https://indieweb.org/year_in_review
-
The first of a new year seems like a good day to assemble, aggregate, summarize and publish various year in review posts for the prior year.
When various online services create a year in review for you many weeks before the end of the year (whether #Spotify #Unwrapped or #Strava #YearInSport), it seems they are short-changing you.
No one asks for an 11 months in review (except HR departments, which is a different problem).
So why do people accept only an ~11 months summary when services provide such a premature āyearā in review?
When people say things like āMake every day countā do they not also believe you should āCount every dayā?
In this case, 2024 had 366 days. You should count every one of them, and every thing from every one of them.
Rather than āsharingā a premature year in review, request your āyear in reviewā today on the 1st of the year from various services, extract the data you want, fill in any gaps, and post your year in reviews on your own siteĀ¹.
#yearInReview #ownYourYearInReview
This is post 2 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2025/001/t1/15-years-notes-my-site-first
ā š®
Glossary:
year in review
Ā https://indieweb.org/year_in_review
Ā
Ā¹ https://indieweb.org/year_in_review#IndieWeb_Examples
-
Welcome to 2025!
15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-it
You can too.
I am once again encouraging you start the year with:
1. Getting a personal domain name
2. Posting on your own site first, then syndicating elsewhere: #POSSE
In 2025 there are even more neighborhoods with other peopleās garagesĀ¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404Ā².
This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity:
* Own your domain -> own your online identity
* Own your permalinks -> own your posts
Want help? Just ask: https://chat.indieweb.org/
#ownYourContent #ownYourData
Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.
This is post 1.
Previously, previously, previously:
* https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar
* https://tantek.com/2023/001/t1/own-your-notes
* https://tantek.com/2022/001/t1/12-years-notes-my-site
* https://tantek.com/2020/001/t1/10-years-notes-my-site
* https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata
ā āØ
ā https://tantek.com/2025/001/t2/first-new-year-review-prior
Glossary:
IndieWeb
Ā https://indieweb.org/
longevity
Ā https://indieweb.org/longevity
post
Ā https://indieweb.org/post
permalink
Ā https://indieweb.org/permalink
personal domain name
Ā https://indieweb.org/personal-domain
POSSE
Ā https://indieweb.org/POSSE
syndicate
Ā https://indieweb.org/syndicate
Ā¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
Ā² https://indieweb.org/site-deaths
-
I have written several posts with tips for various aspects of blogging. This post curates those posts and bits from the #IndieWeb wiki into a linear progression, from why, to what, and how to post. This post assumes you already have a blog ā if you donāt have one and wonder why you should, thatās a different blog post.
Why Post
There is a whole wiki page on the topic:
* https://indieweb.org/why_post ā which could use some gardening
Here is a summary of reasons why to post:
1. Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone elseās garageĀ¹, then you already have reason enough to post. So post on your own site first, and optionally syndicateĀ² to that silo, only if you have friends who still use it to read posts.
2.
What to Post
* Post positive things promptly: https://tantek.com/2018/357/t3
Ā * ā¦ from that day first: https://tantek.com/2018/364/t1
Ā * ā¦ in time order: https://tantek.com/2018/364/t5
* Make and share lists. People like lists
How to Post
* Use a local text editor
* Capture first, edit & publish later: https://tantek.com/2023/365/t1/
* Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1
* Single topic post
* Short and to the point. Edit and remove anything distracting from the main point.
* Quotable post title
* Summary opening paragraph
* Put tangents aside
* Quotable sentences and multi-sentence paragraphs
* Subheadings help cluster related paragraphs
* Use a footer for updates, terminology, previous writings, additional reading, and citations.
Ā * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow.
Ā * Use footer subsections: Previously, Post Glossary, References, Additional Reading
* Check your references
Each of these points could be its own blog post.
Glossary
silo
Ā https://indieweb.org/silo
social media
Ā https://indieweb.org/social_media
References
Ā¹ https://tantek.com/2023/001/t1/own-your-notes
Ā² https://indieweb.org/POSSE
This is post 29 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2024/306/t1/simple-embeds
ā š®
-
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
ā š®
-
Last week at a #HomebrewWebsiteClub sessionĀ¹ I pointed out that I was working on implementing a āsimpleā way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.
I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:
1. A separate āembedā version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.
2. A way to āFollow Your Noseā discover that separate embed version
3. A way to discover the original post from the embedded version
For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.
For (2) I proposed using ārel=embedā which Iāve subsequently written up brieflyĀ².
For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.
Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service!
https://indieweb.org/embed#IndieWeb_Examples
I have yet to implement it myself, and thatās fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.
Got other ideas for simple embeds? Want to implement them on your own site?
Join us in the #indiewebdev chat: https://chat.indieweb.org/dev
UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages).
A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2
Glossary
embed
Ā https://indieweb.org/embed
Follow Your Nose
Ā https://indieweb.org/follow_your_nose
h-entry
Ā https://microformats.org/wiki/h-entry
oEmbed
Ā https://indieweb.org/oEmbed
rel-canonical
Ā https://indieweb.org/rel-canonical
static site hosting
Ā https://indieweb.org/static_web_hosting
References
Ā
Ā¹ https://indieweb.org/events/2024-10-23-hwc-europe#embedding
Ā² https://indieweb.org/rel-embed
This is post 27 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug
ā š®
-
No I did not block you on the #fediverse / #Mastodon / #Misskey etc.
If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyoneās #ActivityPub servers to unfollow me (bug details below).
No itās absolutely not your fault, you did nothing wrong.
We need a variant of Hanlonās RazorĀ¹ like:
āNever attribute to malice that which is adequately explained by a software bug.ā
Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!
Also no worries if you ever unfollow/refollow for any reason. I mean that.
I always assume people know best how to manage their online reader/reading experiences, everyoneās priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.
Bug details:
This was due to a #BridgyFed bugĀ² that deleted my profile (āActivityPub actorā) from (nearly?) all instances, making everyoneās accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!
The bug was introduced accidentally as part of another fix about a month agoĀ³, and was triggered within the following weekā“.
Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).
Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.
Bugs happen, yes even in production code, so please do not post/send any hate.
Iād rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.
This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an āactorā should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasnāt been already, I need to double-check).
To be clear, Iām still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services.
All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.
References:
Ā¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor
Ā² https://github.com/snarfed/bridgy-fed/issues/1379
Ā³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be
ā“ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700
This is post 26 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2024/285/t1/io-domain-suggested-steps
ā š®
-
I have put a lot of thought into deliberately shiftingĀ¹ metaphorsĀ², often in the context of the #indiewebĀ³. One goal is to replace use of violent or divisive metaphors with actively constructive, cooperative, or joyful alternatives, like:
* gardening/farming e.g. digital gardenā“
* biology/ecology/nature e.g. digital ecosystemāµ
* cooking/baking e.g. eat your own cookingā¶
* toolmaking, clothing making, other useful crafts e.g. sew what you wantā·
* music, dancing, painting, and other expressive crafts e.g. remixingāø
* travel, navigation, maps e.g. information superhighwayā¹
* games, sports, running, e.g. surfing the netĀ¹ā°
Some of these areas are well developed (sports metaphors), others are obvious or emergent from various IndieWeb efforts like our principlesĀ¹Ā¹, and others could use brainstorming and experimentation.
Thoughts and words, whether spoken or written, influence each other in reinforcement feedback loops. Consciously choosing one can impact the other and vice versa.
Especially in messages to others or our even future selves, words and metaphors communicate and reinforce our values and thus merit care in their inventionĀ¹Ā² and usage.
What are metaphors you have found constructive, cooperative, or joyful?
References:
Ā¹ https://tantek.com/2023/132/t1/agenda-gardening-metaphors
Ā² https://tantek.com/2023/023/t3/
Ā³ https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook
ā“ https://indieweb.org/digital_garden
āµ https://en.wikipedia.org/wiki/Digital_ecosystem
ā¶ https://indieweb.org/cook_what_you_want
ā· https://indieweb.org/events/2020-08-19-hwc-west-coast#sewing
āø https://en.wikipedia.org/wiki/Remix_culture#Analog_era
ā¹ https://en.wikipedia.org/wiki/Information_superhighway
Ā¹ā° https://en.wikipedia.org/wiki/Internet_metaphors#Functional_metaphors
Ā¹Ā¹ https://indieweb.org/principles
Ā¹Ā² https://tantek.com/2024/180/b1/responsible-inventing
This is post 24 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2024/277/t2/october-blogtober-indieweb
ā š®
-
Happy October!
For some reason this month has a plethora of daily blogging or other creativity prompts. Hereās a list of the ones I found so far:
* #Blogtober (consider this post my first for this, retroactively day 1)
* Inktober ā https://inktober.com/
* LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024
* Looptober ā https://looptober.com/
* Mathober - https://mathober.com/
* Viztober ā https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/
Having found so many for the month I created an āOctoberā page on the #IndieWeb wiki to document them all (and in case folks find others to add):
* https://indieweb.org/October
October is also a very popular month for seasonal blog styling:
* https://indieweb.org/Halloween
Do you have a custom Halloween theme for your personal site? Add it to the wiki!
This is post 23 of #100PostsOfIndieWeb. #100Posts
ā https://tantek.com/2024/247/t4/w3c-link-checker-before-federating
ā š®
Tantek
All stadeus content and data are available under the