I'm slowly getting the hang of IndieWeb building blocks. Today I set up IndieAuth on my server using selfauth! Now I can authenticate myself as "moule.world" on any website that supports IndieAuth, including Owncast livestream chats!
How to setup selfauth: https://indieweb.org/selfauth
My next plan: making an "announcements" section of my website, which will use microformats2, support webmentions, hopefully Fediverse reactions and comments, and of course good ol' RSS.
When I wrote that post, my blog was SSG generated by Pollen (which is ultimately running on the #Racket runtime). That was a great system and it served me well for years, but it had its shortcomings and eventually I decided to replace it with something simpler. I went with a dynamic #Lua site.
The new system is good old CGI based scripts written in #Lua using a #SQLite file as source of truth. About 1169 lines for the whole CMS including my #IndieAuth #Micropub and my #MetaWeblog endpoint.
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
→ https://tantek.com/2025/012/t1/eight-years-webmention
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
References
¹ 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
.io domain¹ likely being phased-out² — seven suggested steps
Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands
It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), 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⁴ (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⁵ 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 #GitHubPages⁶), 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 #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), 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 #indieweb 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 #dotIO plans.
Glossary
Domain
https://indieweb.org/domain
IndieAuth
https://indieweb.org/IndieAuth
Internet Archive
https://web.archive.org/
OpenID
https://indieweb.org/OpenID
Redirect
https://indieweb.org/redirect
RelMeAuth
https://indieweb.org/RelMeAuth
Web sign-in
https://indieweb.org/Web_sign-in
References:
¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io
This is post 25 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug
In den letzten Tagen habe ich noch ein wenig hin und her probiert. Ich habe das Activitypub- und das Friends-Plugin aktiviert. Dadurch bin ich jetzt im Fediverse auch unter marc@Marc.hannebrook.info erreichbar.
Durch Friends kann ich dort anderen Accounts folgen und auch mit deren Beiträgen interagieren. Damit habe ich vielleicht das, im vorherigen Beitrag erwähnte, „Friendica-Problem“ indirekt gelöst. Ich würde dann einfach nicht mehr mit dem Friendica-Account interagieren, sondern mit diesem. Die nächsten Tage werden zeigen, wie praktikabel das ist.
Überhaupt stellt sich die Frage, warum ich mit der Installation des ActivityPub-Plugins noch den Friendica- und den Mastodon-Account betreiben sollte, da diese Seite jetzt direkt mit dem Fediverse verbunden ist. Auch hier wird die Praxis in den nächsten Tagen (hoffentlich) Erkenntnisse hervorbringen.
Ich habe diese WordPress-Installation dann noch vom Webspace bei all-inkl auf meinen VPS übertragen, weil ich hoffte, dass das Login auf indieweb.org durch IndieAuth dann funktioniert – bislang Fehlanzeige. Aber dafür kann ich jetzt per Friends auf Beiträge im Fediverse antworten. Das hat auf meinem Webspace vorher nicht funktioniert. Und das Teilen der Beiträge auf Mastodon und Bluesky funktioniert jetzt ohne vorherige Speicherung des jeweiligen Beitrages.
https://marc.hannebrook.info/blog/2024/06/21/weitere-einstellungen/
@farshidhakimy Wie nischig darf es sein?
#IndieAuth ist Login mit der eigenen Website: https://indieweb.org/IndieAuth
Mastodon benutzt auch OAuth. Glaube das könnte man auch benutzen, aber nicht 100% sicher.
Auch interessant #WebAuthn https://webauthn.io/ . Aufgrund der Neuheit vermutlich abschreckend für den Durchschnittsnutzer
Didn't have time to do much non-work coding tonight, so just added myself to an IndieWeb webring and calling it a night.
Virtuoso 08.03.3339 PAGO edition for the Microsoft Azure cloud is now live.
Highlights include:
* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD
Virtuoso 08.03.3339 PAGO edition for the Amazon Web Services (#AWS) cloud is now live.
Highlights include:
* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD
Product Page: https://aws.amazon.com/marketplace/pp/prodview-idujw25jbgpn4?sr=0-2&ref_=beagle&applicationId=AWSMPContessa
How does my Link In Bio oriented profile doc enable this magic?
It includes Plain Old Semantic HTML (#POSH) tags comprising attributes that convey important information required by the #IndieAuth protocol, as depicted in the attached screenshot.
Courtesy of multi-protocol authentication functionality provided natively by our #VirtuosoRDBMS, the designated Identity Provider (a publicly accessible Virtuoso instance) offers up a cocktail of authentication options 
Here's a screencast demonstration of Single Sign-On facilitated by loosely-coupling #Identity and #Authentication, courtesy of the #IndieAuth protocol.
We are working on OIDC support, and exploring IndieAuth!
The Sign-in with Mastodon feature uses Mastodon specific APIs and is a temporary measure until we get OIDC in place and other platforms support it!
@blake I think #IndieAuth style login combined with a central #FriendFeed style #lifestream aggregation of content is what’s needed for the Fediverse.
That way I can have one central canonical identity to rule them all
@dansup @pixelfed Is this using the non-standard #MastodonAPI or a standard like #IndieAuth or #OpenIDConnect? https://www.w3.org/TR/indieauth/
I think it might be better to leave it out, just to avoid the confusion about how the accounts are linked. Instead, and to solve point 3, we could start by reintroducing #OpenID (or some form of it, like #IndieAuth ). Let Pixelfed be a provider, consumer, or both, and get more willing projects like #Calckey to support it too. That could even lend to eventually support domain-based usernames a la Bluesky, especially if Mastodon gets on board with it.
@whalecoiner We need to free the #Fediverse identities from the #Mastodon, #Lemmy, #Pixelfed etc so that I can have a single identity in use across multiple places
I know #IndieAuth has this working for the #IndieWeb, but most API:s that Mastodon support are Mastodon specific not Fediverse generic (except for ActivityPub, WebFinger and a few others)
