IndieAuth: Eliminate registration for OAuth APIs and use URLs for identity & auth: https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web
WeChat ID
aaronpk_tv
-
-
The IndieAuth extension to OAuth2 is perfect. I will adopt this in @home_assistant to make it easier for people to build apps against local instances.
-
Julien Deswaef
https://mastodon.social/@xuv
•
Jul 7
@aaronpk PS: I should mention that I started following you from the other instance. But still could not see your post before searching for it.
Yeah that sounds like Mastodon's limitation where it doesn't actually go fetch posts from people if someone on the server isn't already following them. Thanks for providing an example where that was confusing! -
@aaronpk search function seems to work. Just boosted your post.
-
-
Microsub and the new reader evolution (skippy.net)"The other great thing about Microsub, the technology behind Aperture and Monocle, is the separation of “feed collection” from “feed display”. I don’t have to use only Monocle to read my feeds. On my phone, I use an app called Indigenous. I could also use Monocle from a mobile browser. Or I could use Together. Or I could write my own reader interface, if I so chose."
-
Julien Deswaef
https://mastodon.social/@xuv
•
Jul 7
@aaronpk yes. Exactly tried that. It does not work. Also, I can't seem to see the boost I did from a different instance looking at this account.
I think I fixed it... give it a try again? -
Julien Deswaef
https://mastodon.social/@xuv
•
Jul 7
@aaronpk for some reason, this post does not federate well with all Mastodon instances. I'm trying to boost it from another account elsewhere, but I can't seem to see it. Any clue?
by any chance, are you trying to paste that post's URL into the search box on other Mastodon instances? -
If you’re familiar with OAuth, this introduction to IndieAuth walks through the process of how auth for the open web works. Really happy that Micro.blog supports this now.
→ 2018/07/07 3:41 pm -
Julien Deswaef
https://mastodon.social/@xuv
•
Jul 7
@aaronpk for some reason, this post does not federate well with all Mastodon instances. I'm trying to boost it from another account elsewhere, but I can't seem to see it. Any clue?
hm, I've been incrementally implementing ActivityPub, doing as little as possible each time. I don't think I've tried what you're doing yet, trying to find my post from an instance that is not already following me. I'm not actually sure what I need to implement to make that work though! Any ideas? -
Working on on Indiepaper has been a fun project. It's involved writing Python, Swift, HTML, CSS, and JavaScript, and using @awscloud Lambda, S3, and CloudFront. #polyglot
-
Look for mf2 first, use Mercury as a fallback
If the page has mf2, that is likely to be much better data than what Mercury finds. Indiepaper should first check if it finds an article via mf2, and if it doesn't, then can use Mercury to extract what it can.continue reading... -
Eugen
https://mastodon.social/@Gargron
•
Jul 7
IndieAuth sounds interesting as a more generic way for federated applications to allow app registrations https://indieauth.spec.indieweb.org/
The question is how do we adapt this after our current, extremely similar but somewhat different system has been in production use for around 2 years #mastodev
The existing Mastodon API uses OAuth 2, right? Seems like you'd be able to add this on top and still also support the existing behavior without any changes. You'd get the benefit of auto discovery and global client IDs. Maybe we should chat about this at the next w3c call? -
I added experimental support for IndieAuth in Indiepaper today. Test it out here – https://www.indiepaper.io/indieauth.html. Once authenticated, you get an automatically generated bookmarklet and a button to click for automatically configuring Indiepaper for macOS.
-
Thoughts: The requirement of apps to have a publicly accessible website conforming to the IndieAuth API might be a limiting factor
On the other hand, globally unique identifiable apps is a huge benefit in terms of admins being able to restrict app access. I.e., currently every user can revoke app access to their account, but server admins cannot say "I don't want the cross-poster to work with my server" because there is no such thing as *the* cross-poster
-
IndieAuth sounds interesting as a more generic way for federated applications to allow app registrations https://indieauth.spec.indieweb.org/
The question is how do we adapt this after our current, extremely similar but somewhat different system has been in production use for around 2 years #mastodev
