Anti-tech and alternative media. https://robertkingett.com/posts/6682/ #Blog #Blogs #Blogging #IndieWeb #NoPaywall
Great conversation at today's #FrontEnd Study Hall event. We took collective notes in etherpad today. It can't encompass everything, but it was a terrific first #IndieWeb event of the year. https://indieweb.org/events/2025-01-02-front-end-study-hall
New year, new personal website? (Or update your existing site?) Join us for a virtual IndieWeb meetup, Homebrew Website Club, January 8th at 6PM Pacific!
New year, new personal website? (Or update your existing site?) Join us for a virtual IndieWeb meetup, Homebrew Website Club, January 8th at 6PM Pacific!
New year, new personal website? (Or update your existing site?) Join us for a virtual IndieWeb meetup, Homebrew Website Club, January 8th at 6PM Pacific!
currently implementing webmentions into my site!
#indieweb
I suppose an #introduction is in order!
I'm erin, a front-end web developer (to steal from based out of Portland, OR. I'm not actually new to fedi, but I wanted a professional account separate from my personal one. So this will be the place where I talk about the web! Web standards, CSS, JavaScript, microformats, indieweb stuff, software engineering in general... the list goes on.
Most of my time has been spent in the React and Vue world on the front-end and the Ruby and PHP world on the back-end. I learned HTML in the late 1900s and have been making little web pages ever since.
Some hashtags to make this searchable:
#html #css #javascript #FrontEnd #WebDev #IndieWeb #React #VueJS #microformats #ruby #php #linux #vim #neovim
A couple great #indieweb blogs I found today!
Had a fight with the Content-Security-Policy header today. Turns out, I won, but not without sacrifices.
Apparently I can't just insert <style> tags into my posts anymore, because otherwise I'd have to somehow either put nonces on them, or hash their content (which would be more preferrable, because that way it remains static).
I could probably do the latter by rewriting HTML at publish-time, but I'd need to hook into my Markdown parser and process HTML for that, and, well, that's really complicated, isn't it? (It probably is no harder than searching for Webmention links, and I'm overthinking it.)
Is it just me, or is there a certain irony to the fact that this month's indieweb carnival subject is "the importance of friction" and the link to that from the wiki page returns a 404 not found error?
I used #CloudflareWorkers to add missing features to an existing website without touching the CMS. In this case, CMS doesn't generate an RSS feed and doesn't have any way how to add a link to RSS into the head for auto-discovery. #indieweb https://www.rarous.net/weblog/2025/01/02/rozsirovani-funkcionality-existujicich-webu-pomoci-cloudflare-workers
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
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
→ https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save
Glossary:
year in review
https://indieweb.org/year_in_review
¹ https://indieweb.org/year_in_review#IndieWeb_Examples
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
Front End Study Hall tomorrow 10am Los Angeles/1pm New York/6pm London. We enjoyably explore whatever we participants want to create, whether that’s Christmas lights, how to create a blurred spoiler with no JavaScript, and all manner of CSS and HTML features. Join us! All are welcome at this fine #indieWeb #frontend #webdev event. https://events.indieweb.org/2025/01/front-end-study-hall-018-jSXCx17D9a63