Interesting post from @kagihq on their small web features
https://blog.kagi.com/small-web
#indieweb #technology #openweb #kagi
Hi Austin! Reminder we’re resuming the IndieWeb Meetup. This coming Wednesday, Nov 6th, the day after the election, 7pm, Mozart’s Coffee.
New (little) review! I enjoyed MURDER BY NUMBERS, a bunch of #nonogram puzzles with some narrative tying them all together. The writing was way better than you'd expect from a game of this size though!
@adam_chal @janriemer Bluesky is built around the concept of users hosting their own data, which is more similar to the #IndieWeb than to Mastodon – Mastodon is focused on being a monolithic multi user social web server that federates with likeminded
I think there are lots to learn from how Bluesky and the IndieWeb puts the user at center, not the server
Please publish and share more
Likes Please publish and share more by Jeff Triplett.
Write and publish before you write your own static site generator or perfect blogging platform. We have lost billions of good writers to this side quest because they spend all their time working on the platform instead of writing.
🤖 I posted to my photography weblog.
Old Slides
I wrote this piece on #indieweb before I had that word in my vocabulary but it still stands true today. I noticed it popped to the top of my popular pages this week so sharing here bc the #PersonalSites and #blog audience may enjoy:
https://www.jimwillis.org/2019/11/20/free-internet-vs-internet-of-free-stuff/
I'm very excited for this month's #IndieWebCarnival. @xandra invited us to write about impact and I have so many good ideas buzzing through my brain.
https://library.xandra.cc/indieweb-carnival/
That @dansup has been a busy chap on the @loops front, good to his word, I'm in…
---
Thank you and keep up the great work! 🙏
Longer:
For me, "simple" means a little HTML is all you need. I was inspired to come up with something that anyone could create with (existing) HTML text files. Zero imperative code.
Simple HTML also means easier / better support for static file hosting solutions.
E.g. if your website is on GitHub Pages or other static site hosting, you can’t implement an oEmbed endpoint (certainly not without an external service, which has other problems).
Whereas plain old semantic HTML (POSH¹) works great on GitHub Pages or other static site hosting.
Would be interesting to see if someone can build an oEmbed "shim" service that did discovery on rel=embed and then translated h-entry into oEmbed’s specific JSON vocabulary.
That way publishers would have less work to do (with plain HTML) and existing oEmbed consumers would support embedding more publishers.
¹ https://microformats.org/wiki/posh
time to #livestream working on my #rust based website builder. version 42 continues to look like it's gonna be the one 
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
→ 🔮
monaxle listened to Everlasting Days (VIP) by Nu:Logic Feat. Lifford on Hospitality 2015 #librefm #indieweb #music #shareopenly https://libre.fm/user/monaxle/scrobble/1730500539
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
Glossary
embed
https://indieweb.org/embed
Follow Your Nose
https://indieweb.org/follow_your_nose
h-entry
https://microformats.org/wiki/h-entry
rel-canonical
https://indieweb.org/rel-canonical
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
→ 🔮
I should add #webmention to the Wok. Does anybody know of a simple (the simplest the better) self-hostable webmention server? Bonus if there's also a client that can be fed some #RSS to do its thing.
My new blog The Digital Renaissance is now fully featured, accepting signups, and sending posts as newsletters