Wrote a summary of web linking (AKA link relations; think rel="xxx" in a <a/> or <link/> HTML element).
The piece of the puzzle that's still unclear to me is whether WebFinger has been superseded, or maybe just generally ignored. There doesn't seem to be much adoption (except by Mastodon) or follow-on activity AFAICT.
Since I've gotten exactly one webmention for my blog, I obviously had to put some work in to display this webmention on my blog. 😄 Had to do some reading to figure out how to make Hugo download external resources, but otherwise it was pretty smooth sailing. Much thanks to https://webmention.io/. Still not implemented sending webmentions yet though.
@henrikjernevad Looks like I'd need to add IndieAuth support to my (WriteFreely) web site before I could use webmention.io. Probably not worth the effort.
Nothing dictates that receiving a Webmention means you’re bound to display its source content on your website.
You could…
• forward the Webmention to your email,
• build a private notifications dashboard (with or without a moderation queue),
• add a link to the source page to your website without including its content,
• do something wild like set up an auto responder to the original author thanking them for the like/boost/reply,
• etc. etc. etc.
Add #IndieAuth to your website and allow others to sign in. They’d be able to view a dashboard of the content they’d posted that made its way onto your website. Maybe add some lightweight self-service moderation controls?
Not all things need to be federated. Wikis probably shouldn't be openly federated (although closed federation a la IRC and pushing to mirrors isn't a terrible idea). Forums can get away with not being federated. Both should probably support something like IndieAuth to make it far simpler to participate, though.
I don't completely understand #IndieAuth though. It appears to be a vastly simplified version of OpenID (which is great!), but unfortunately it also seems to be quite limited. I don't know if IndieAuth supports this (yet?), but with the Fediverse being as big as it is, it might not be a terrible idea to support double-@-style Fedi-handles in the login box (and then get Mastodon-and-friends to support it!).
Anche oggi, per l’ennesima volta in cui mi faccio distrarre da #collegamenti colorati durante la mia #navigazione errante nell’oceano del #web, scopro nuove cose #interessanti. 😼
Nel #footer di un sito c’era un collegamento ad un “#IndieWeb#Webring”, il cui nome di dominio è una sequenza di emoji. Lo apro, e anziché una classica lista di membri, mi trovo un insolito modulo che mi chiede di fare login nel sistema inserendo il #link del mio #sito. Scopro che questa cosa posso farla con questo sito #WordPress, dopo aver installato il #plugin#IndieAuth; quindi, ci provo, e mi viene chiesto di aggiungere alla home del sito i link di navigazione del webring, e poi di preparare #dati del #profilo secondo lo standard h-card. 📟
È stata un’occasione per fare una robina che mi sono sempre seccata, cioè inserire le #info del mio profilo autore (inclusive di bio, come escono sul Fediverso) sulla sezione #MicroBlogdel fritto misto. Purtroppo, questo #standard ben predicato sembra razzolare male: non c’è stato verso di far vedere al #validatore del webring la mia descrizione, e mi devo accontentare di URL, nome, e foto profilo… però, un validatore a parte, che viene consigliato dalla stessa pagina, invece valida tutto come vorrei io. Uno #schifo. 😶
Yay, I wanted to log into my linkblog using IndieAuth but for some reason that’s not working anymore since the last update of the IndieAuth WordPress plugin. Guess that’s something to debug in the New Year then.
Interested in #RelMeAuth or #IndieAuth?
You can add this to your @getkirby install quite easily.
You could even add a structure to have all of your sites and accounts listed in your head tag:
Here's a screencast demonstration of Single Sign-On facilitated by loosely-coupling #Identity and #Authentication, courtesy of the #IndieAuth protocol.
For me, still working on making a bunch of feature additions to my site/blog. Adding #indieweb capabilities (#indieauth, webmentions, notes) and cleaning up some weird things in my site code. Once finished, I have a bunch of things I want to write about in the #infosec domain.
Considering writing an #FEP that allows using #IndieAuth logins as display handles. The basic idea is that next to the meta tags/headers for OAuth links, you'd have a public key that can be used to verify a signature placed in a field in an AP Actor object. There would be another field next to the signature that tells remote servers what the preferred handle is. If lookup succeeds and the signature is valid, show the handle (possibly simplified) next to an IndieAuth icon.
I could probably make a little shim between #IndieAuth clients and #Keycloak to handle client lookup and registration. Not completely sure how IndieAuth clients would handle the redirect though (as it would be undoubtedly cross-subdomain)...
I've started reading a bit about #IndieAuth -- for some reason, I started with the spec on W3.org, which makes more sense to me than a lot of stuff I've read but it also doesn't "feel" complete.
I'm wondering if I can configure #Keycloak to function sufficiently as an IndieAuth provider.
While I understand the motive for #Pixelfed 's upcoming/new Mastodon SSO, I don't like it.
It's confusing to talk about (see above). You have to word it very specifically to make it clear you're signing into Pixelfed with a Mastodon account.
The concept is confusing. It isn't the same account, by any means, and you can register on both services. Threads, for example, is more or less an extension on top of Instagram, like Guppe is an "extension" here.
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.
So, in classic IndieWeb fashion, I want my website to be my hub on the internet.
But I’ve been looking into all the different standards (#Webmentions, #Micropub, #ActivityPub, etc.) but I'm not sure which one or which combination of them is best for my needs.
So I thought I might reach out on here with what I'm trying to do and see what people thought were some go ways to go about it.
@elly@elly I have #IndieKit installed on a test site and looks promising. But I don’t use it for my personal posts yet, so can't fully recommend. Contributions to the repo are sporadic but recent.
Added a couple of screenshots so you can get an idea of what the admin side looks like. It is setup to have syndication plugins, too.
I'm increasingly getting the feeling that one of these days I need to reactivate LID -- Light-Weight Digital Identity -- my entry into #identity and #iiw created more or less by accident in 2004. Then folded into the larger #OpenID movement. Some of its more interesting features were adopted by other identity protocols over time, but some others are still unique and would be very useful now that the decentralized, user-owned, social web is waking back up.
What are You Working on Wednesday
Weekly thread to discuss whatever you’re working on, big or small, at work or in your free time.